Simple Solution, Low Maintenance
Practical Project Management for PMs & PMOs
Practical Project Management for PMs & PMOs
Start your first project
Guidance, templates & governance in one place
How SSLM grows from a single project to a whole portfolio: roll up, not rebuild. Every project starts at Tier 1, the core pack, and depth is added only when a real trigger calls for it. Most projects never leave Tier 1 or 2. See the template pack for the documents at each tier.
You never switch frameworks to scale. You climb the same ladder, adding depth only when a real trigger calls for it. Here is the whole ladder at a glance.
Most projects live at Tier 1 or 2. Tiers 3 and 4 are the Enterprise Extension, reached only when work outgrows a single project. Value streams are a Tier 3–4 overlay for continuous flow, covered below.
Whatever the altitude, the same four questions apply: what the level is, who works in it and how, where SSLM fits, and how you get the best outcome. Project and Program and Portfolio are rungs on the ladder; a Value Stream is an overlay for continuous flow.
A temporary, coordinated effort that turns intention into a defined outcome within agreed constraints, then closes. This is the home of SSLM.
A Sponsor (accountable, chairs the SteerCo), a Business Owner (owns the benefits), a Project Manager (runs delivery), the delivery team and suppliers, with the PMO keeping the standard. They work the critical-path flow: idea → business case → plan and RAID → weekly and monthly reporting → closure.
The core pack is this level. Tier 1 is the lean core; Tier 2 adds assurance and control blocks, one at a time, on a real trigger.
Start at Tier 1, add only on a trigger, keep one accountable owner, and report the real colour — the least process for the most traceable result.
Priya runs one project, a new customer returns portal. It is funded at Green Light via the Business Case; day to day she works a Project Plan on the critical path, keeps the RAID log, and sends a Weekly Update that rolls into the monthly report. When vendor integration starts to look risky she adds a Tier 2 Risk Assessment (a trigger appeared) and raises the slip early at SteerCo. At go-live she hands over to the Business Owner and captures the lessons.
A set of related projects coordinated to deliver one shared outcome no single project could deliver alone. Temporary: it closes when the outcome lands.
A program owner accountable for the outcome, with project owners beneath. The program plan treats each project as a milestone, and coordinates the cross-project dependencies and shared constraints no single project can resolve alone.
The same instruments, a level up. The RAID Dependencies view becomes shared across projects; project reports compose into a program report, never re-authored. No new method.
Compose, do not re-author; prioritise the scarce resource across projects; keep one accountable owner per layer.
Sam owns ‘Faster Returns’: three related projects (the portal, a warehouse process, contact-centre training) that only deliver the benefit together. Sam runs none of them; each has its own PM. The program plan treats each project as a milestone, tracks the cross-project dependency (the portal cannot go live before the warehouse process is ready) in a shared RAID view, and composes the three weekly reports into one, never rewritten. When two projects need the same specialist, the one on the critical path wins.
The standing set of all programs and projects, governed as a group against strategy: fund, hold or stop. Unlike a program, a portfolio is permanent.
A portfolio owner or board funds, holds or stops each initiative via the PTIP, run by a permanent office. Two flavours: a strategic EPMO decides which work to do; a tactical PMO runs each project well; most organisations run a hybrid of the two. It runs the portfolio, not the projects within it.
The PTIP sequences and funds against strategy; benefits aggregate across the portfolio; board reporting composes the reports below. Standing up and maturing the office is its own discipline.
Right-size the office to real demand (most settle at a hybrid). Grow it the SSLM way, adding each activity only on a trigger. See Running a PMO for the maturity path.
Dana governs the whole set: a dozen projects and two programs, and delivers none of them. Using the PTIP she scores and sequences every initiative against strategy and decides what to fund, hold or stop; the board sees one composed portfolio report a month. When budgets tighten she stops a low-value project to protect a strategic one. Her small office is a hybrid, strategic (which work to do) and tactical (helping PMs deliver well), sized to the organisation.
Not a rung, but an overlay. When work becomes continuous flow — every step from a customer request to delivered value — rather than a temporary project, SSLM governs it from above while the team runs the flow below. Unlike a project, it never closes: think of a production line for delivering value that keeps running and improving.
Below the altitude break, a value-stream manager owns the flow end-to-end. Above it, the SteerCo or board govern, the sponsor funds and clears blockers, and the customer defines value. The manager translates flow signals into five executive elements.
SSLM governs, funds and reports via the Executive Stream One-Pager and Flow-to-Executive translation. The altitude break keeps team telemetry below and board decisions above; nothing crosses raw. The board funds the stream as a whole, not project by project.
Compose the one-pager from real flow signals, never re-author; keep the altitude break intact; adopt only on a real trigger. Complementary, not competing.
Marco does not run a project; he runs the Payments Platform as continuous flow. Work moves from customer request to released capability every week and never finishes. Below the altitude break his team works in flow (backlog, WIP, lead time). Once a cycle Marco derives the Executive Stream One-Pager (Alignment, Confidence, Constraint, Value, Investment) from real flow signals, never re-authored; when a third-party integration becomes the constraint he reports it red with the decision the board needs. The board funds the stream as a whole and calls fund, hold or stop.
Long before programs or portfolios, a single project deepens. Tier 2 adds assurance and control blocks one at a time, each on its own trigger, all still run from the core pack.
| When this is true (the trigger) | The block you add (Tier 2) | Why |
|---|---|---|
| Delivery confidence is in doubt | Project Health-Check · Assurance Assessment | An independent read on whether the project will actually land. |
| Material risk exposure | Risk Assessment Tool | Risks sized and ranked by impact and likelihood, not just listed. |
| Many stakeholders, or unclear roles | RACI · Stakeholder & Comms Plan | Who is accountable for what, and who to keep engaged. |
| A real budget to control | Cost & Resource Plan | Forecast watched against budget, so there is no late surprise. |
| Benefits to prove | Benefit Register | A baseline captured up front, so the value can be measured later. |
| Third parties delivering scope | Vendor Register | Supply risk and key contract dates kept visible. |
| Design decisions to hold | Design Principles Register | Consistent design rules a solution must honour. |
Nothing is added pre-emptively. With no trigger, you stay at Tier 1. Each block is in the template pack.
Between a single project and a continuous value stream sits the everyday way SSLM grows: rolling up, not rebuilding. A program coordinates related projects; a portfolio governs every program and project against strategy. Both use the same instruments — simply pointed a level up.
What a milestone is to a project, a project is to a program, and a program is to a portfolio. Each layer reads the one below it at its top level only — nothing is re-typed.
The principles don't change — they repeat up the stack. One accountable owner at every layer (Principle 1); prioritise the scarce resource (Principle 5); right-size the governance (Principle 8). The custodian still owns the standard blocks beneath them all.
Nothing new is invented at scale. The core-pack tools are simply applied at a higher altitude.
| SSLM instrument | At project level | At program / portfolio level |
|---|---|---|
| RAID (Risks, Assumptions, Issues, Dependencies) & Tracker Logs | Per-project risks, issues and dependencies. | A shared dependency & constraint view across projects. |
| Reporting chain | Weekly status rolls into a monthly project report. | Composed into program, then portfolio reporting — never re-written. |
| PTIP (portfolio prioritisation) | A single Business Case justifies one initiative. | Sequences and funds every program & project against strategy. |
| Benefit Register | Per-project benefit lines, checked at their horizon. | An optional cumulative portfolio benefits view. |
| Project Plan | The milestone baseline for one project. | A project becomes a “milestone” in the program plan; a program a line in the portfolio. |
Only a handful of things change when you move above a single project — everything else is roll-up.
Closely related, but not the same altitude.
Value Stream Project Management (VSPM (Value Stream Project Management)) manages the end-to-end flow that turns a customer request into delivered value, and improves it continuously. SSLM doesn't compete with it — SSLM governs, funds and reports the stream from above, while VSPM runs the flow below. The seam between them is the altitude break.
This integration lives in the SSLM Enterprise Extension (Tier 3–4). It is picked up only on a real trigger under Principle 8 — when work becomes continuous flow governed above team level. Most projects never reach it.
One page per value stream, derived from the weekly flow once per governance cycle and never re-authored. Every status traces to a real flow signal.
A Value Stream Manager owns the flow but not the people — sales, production, quality and dispatch usually report elsewhere. So value stream management is far more about influence and relationships than command and control. Authority gets compliance; relationships get the commitment that makes an improvement actually stick.
In SSLM terms this is Principle 12 (Capable to deliver) meeting the Stakeholder Management & Communication plan: the structure names who to involve and what to report — relationships are how you turn that into commitment. See Relationship management for the full skill.
SSLM's principles and VSPM's nine components come from the same instinct — remove waste, tell the truth, serve the purpose. Each SSLM principle maps to the VSPM component it reinforces.
| SSLM principle | Aligning VSPM component | How they reinforce |
|---|---|---|
| Anchor to purpose (umbrella) | Value · Continuous improvement | Both start from an externally-defined "why" — strategic purpose and customer value — and question anything that serves neither. |
| Clear accountability & authority | People & teams | One named owner accountable end-to-end: SSLM's accountable owner is VSPM's value-stream manager, not a department head. |
| Report the real colour | Metrics (flow efficiency) | Honest status is honest flow data; flow efficiency exposes the hidden waiting a managed narrative would smooth over. |
| Fit for purpose | Waste | Building beyond what the audience needs to act is over-production — a non-value-adding step in VSPM terms. |
| Plan to the critical path | Value stream · Flow · Mapping | Both sequence by real dependencies, not dates, and expose the constraint sequence that sets the earliest finish. |
| Prioritise | Pull · WIP | Throttle work to the constraint and real capacity — pull on real demand, and don't run ahead of the bottleneck. |
| Narrative flow & roll-up | Flow | One connected story that rolls up without re-authoring is the reporting-layer form of smooth, unbroken flow. |
| Willingness to stop | Metrics · fund/hold/stop | Decide continuation on current evidence, not sunk cost — SSLM's assurance re-test is VSPM's "is spend buying flow?" |
| Right-size governance | Waste | Adding a governance block only on a real trigger is direct waste elimination — the same instinct as stripping approvals and hand-offs. |
| Compose from standard blocks | Continuous improvement · Waste | Reusing a standard block removes re-invention rework; the maintained master block is the baseline Kaizen improves against. |
| Access over ownership | Waste · Flow | Rent, contract and automate over hire and build — cutting the waste of idle owned capacity, a pull-style response to real need. |
| Learn and improve | Continuous improvement (Kaizen) | Kaizen by name: small, regular refinement with lessons fed back so the next cycle inherits the fix. |
| Capable to deliver | People & teams | Staff to the skills the work genuinely needs — SSLM's proven-capability mix mirrors VSPM's cross-functional stream team. |
| Design — Simple Solution | Waste · Pull · Value | Buy over build, configure over customise, add on demand — Lean waste reduction and pull applied to the solution itself. |
| Design — Low Maintenance | Waste · Metrics | Minimal operational footprint, automate, whole-life cost over upfront cost — waste removal that continues long after go-live. |
SSLM's documents become the governance skin over the stream — each one points at a VSPM component without disturbing the flow beneath it.
| SSLM instrument | What it does | VSPM component it governs |
|---|---|---|
| Executive Stream One-Pager | One page per stream — Alignment, Confidence, Constraint, Value, Investment — derived from the weekly flow once per cycle, never re-authored. | The stream & its metrics, as a board-ready view |
| The altitude break | A hard line: the team works in flow below it; the board sees only what those signals mean above it. Nothing team-level crosses raw. | Protects Flow & WIP; separates telemetry from governance |
| Flow-to-Executive Translation | Converts flow telemetry into the five elements, one line of evidence each, with an integrity check. | Metrics & Value → decision language; keeps streams comparable |
| RAID — Dependencies & Constraints | A shared cross-stream view of dependencies, and the single limiting constraint. | Waste / bottlenecks; the Constraint element |
| PTIP | Sequences and funds streams against strategic objectives at portfolio scale. | Value & Pull (Investment, Alignment) |
| Business Case + Benefit Register | Baselines benefits and re-checks them at their horizon — cashable vs notional. | Value — confirms released capability lands |
| Monthly / Board roll-up | Composed from the reports below, never re-written (fractal roll-up). | The rolled-up, stream-level view for the board |
| Project Plan → flow view | A milestone becomes a stream commitment / release; the plan spine becomes a flow view rolled up to stream level. | Becomes the Value stream representation itself |
| Learn & improve | The team runs its own flow retrospective on its native cadence; cross-stream lessons flow to the custodian. | Continuous improvement (Kaizen) & People |
| Assurance / Health-Check | Independently re-tests strategic fit and deliverability each cycle; a low score is a real trigger. | The stop/continue discipline a stream lacks on its own |
The Tier 3 and 4 material lives in the Enterprise Extension. Grab the deeper guides in the Templates & Guides pack, or see Running a PMO for standing up a portfolio office.