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 portfolio: start light and add depth only on a real trigger. Every project begins at Tier 1 — the core pack — and most never leave Tier 1–2. See the template pack for the documents at each tier.
The default. One project, one pack — the full critical-path flow above.
Same single project, with deeper assurance blocks added only when a trigger requires — still run from the core 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 & 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 | 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.
The practical detail of running SSLM at program and portfolio scale.
A project owner, a program owner, and a portfolio owner or board — each accountable for their own layer's outcome (Principle 1, repeating up the stack). The PMO / EPMO custodian maintains the standard blocks beneath them all.
SSLM governs cross-project dependencies, shared constraints, portfolio prioritisation and funding, and aggregated benefits. Each project still runs itself — the layers above read it at its top level only.
Program and portfolio reports are composed from the reports below, not rewritten. If a manager is re-authoring status rather than composing it, the roll-up has broken and the reporting burden has crept back in.
A program when related projects share dependencies and one outcome; a portfolio / EPMO when a standing office is needed to run many at once. Picked up under Principle 8 — never pre-emptively.
Program at Tier 3, Portfolio & EPMO at Tier 4. The instruments are the core pack's, pointed a level up — no new method, no rebuild.
So scarce resources are prioritised across projects, dependencies are seen before they bite, benefits add up to a portfolio picture, and the board funds, holds or stops against strategy — all on the tools teams already know.
Value Stream Project Management (VSPM) 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.
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 practical detail of running a value stream under SSLM governance.
Below the line, the value-stream manager owns the flow end-to-end. Above it, the SteerCo / Board govern, the sponsor funds and clears blockers, and the customer defines value. The PMO / EPMO custodian keeps the standard mapping consistent.
SSLM governs funding, stop/continue decisions, cross-stream dependencies, board reporting and benefits. The stream owns everything below the line — its own flow, WIP, mapping, metrics and Kaizen loop.
The manager derives the Executive Stream One-Pager from the weekly flow once per cycle. Every element traces to a real flow signal; an amber that's really red is reported red. Nothing team-level crosses the altitude break raw.
Picked up under Principle 8 (Right-size governance) only when work becomes continuous flow governed above team level — the Tier 3–4 threshold. Never pre-emptively; "it felt like time" is not a trigger.
It lives in the Tier 3–4 Enterprise Extension, above the altitude break. The stream itself runs wherever the delivery teams are, in whatever method they already use — SSLM layers over it, additive not rip-and-replace.
So the board decides in decision language, streams stay comparable across a portfolio, and the flow below is never disturbed — while supplying the funding discipline and honest stop/continue call a stream on its own lacks.