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
This page follows two journeys at once: how you grow as a PMO professional, and how you grow the office itself — from supporting a single project all the way to a value-stream-oriented capability. It's a map, not a mandate: most organisations settle, quite legitimately, at a well-run hybrid office. For how projects roll up into programs and portfolios, see Scale.
Three terms get used loosely. Here's what each means in SSLM before we go further.
The Project Management Office — supports and governs delivery across projects. Keeps the standard, the reporting rhythm and the records honest. Where most people start.
The Enterprise PMO — sits at the executive table, links every project to strategy, and owns the portfolio. In SSLM terms, the matured, portfolio-scale (Tier 4) form of the PMO.
One office bridging strategic and tactical, fitted to the organisation's culture. For most small-to-medium organisations this is the sensible, stable operating model.
The difference is altitude. The PMO manages how each project is delivered (tactical); the EPMO decides which projects to do (strategic); the Hybrid does both, fitted to the organisation's culture. That altitude is what sets where each one sits.
One sentence captures it: map a direct line from the project objectives being delivered to the organisation's strategic objectives.
The office's own values are, almost word for word, SSLM's principles. That's not a coincidence — a PMO run any other way stops being simple and low-maintenance.
If you're joining a PMO to support projects rather than run one, your job is to make the whole system work across projects. This is where your own journey begins — and it's the part you can act on today.
From a single project up to a value stream, the office's tools change but one capability doesn't — and it only deepens: the ability to communicate, influence a broad range of stakeholders, make sense of complex and disparate information, and steward resources so delivery meets the organisation's strategy. The templates don't deliver value; a person using them this way does.
The skilled PMO is neither a postbox — passing information up unassured — nor spreadsheet-police enforcing templates without judgment. They assure the information and exercise judgment: the standard makes disparate inputs comparable, and this skill makes them coherent.
Read the PTIP, the active projects' latest reports, and the framework pack. Meet the PMs you support.
Help assemble a SteerCo pack, compile a monthly roll-up, and check the templates in use are the current versions.
Spot where reporting is inconsistent or records are messy, tidy them, and feed one improvement back into the standard templates — the custodian habit.
Consistency. When every project looks and reports the same way, the board can trust the whole portfolio at a glance.
The two journeys. As you grow — support, then coordinate, then run, then build — you also grow the office around you. The rest of this page is the second journey: standing an office up and maturing it. Flip on “the full build-and-mature detail” at the top when you're ready for it.
Building an office is a different job from running one — and the two need different skills, so plan an explicit handover point. Design it holistically, or it ends up reactive and patchy.
Start from the organisation's strategy and culture, then align all five factors to reinforce one another — a single message and consistent behaviours.
An organisation's design isn't one lever but five points of a star — Strategy, Structure, Processes, Rewards and People — and they only deliver when aligned. Start from strategy and align the other four to reinforce it. Pull one without the others — add roles without the processes to support them, say — and the design goes patchy.
It's SSLM's own instinct, applied to the office rather than a project. Anchor to purpose becomes “design around strategy”; right-size governance becomes “align the factors, don't bolt roles on.” Both reject the reactive, patchy build — and both are coherence checks: just as the PMO makes every report element tell one story, the Star makes structure, process, reward and people all tell the strategy's story.
Vision, values and direction that align with the organisation's own strategy — the EPMO strategy flows from it.
Distribution of authority — spans and layers, governance escalation levels, and the key stakeholders.
Information and decision processes — the reporting channels that carry governance.
Compensation, recognition and a growth path — capability and skill development that pulls in the same direction.
Roles, responsibilities, skills and mindset aligned to strategy. Get the people right first — start at the top and work down.
The office doesn't invent tools — it owns and compiles the SSLM pack, used a level up. The deck's names map straight onto the standard blocks.
| In the model (deck) | SSLM name | What it is |
|---|---|---|
| Project Pipeline List (PPL) | PTIP | The single prioritised list of every initiative; where a Project Reference is born. |
| Control (RAID) Logs | RAID Log | Risks, Assumptions, Issues, Dependencies — the project's working memory. |
| Tracker Logs (Action / Decision / CR / Closure) | RAID & Tracker Logs | The same workbook's action, decision, change and closure tabs. |
| Business Case | Business Case | The one-page baseline that ties a project to strategy. |
| Change Request | Change Request | The traceable gate for any change to a baseline. |
| Meeting Agendas & Minutes | Meeting Playbook | Agenda populated with Red/Amber RAID and a look-ahead; minutes capture actions & decisions. |
| Weekly “5 Blocker” | Weekly Update | The weekly status and escalation tool — RAG plus trend. |
| Plan on a Page | Project Plan & Schedule (one-page view) | A one-page, high-level project plan for the executive level — the milestone view, without the detail. Good enough for most decision forums early in maturity. |
| Idea on a Page | Idea on a Page | A new idea captured on one page — the front door to change. Put to the executive to stop it, or develop it into a Business Case (and onto the PTIP). |
Roll-up composes; it must not re-author. Program and portfolio reports are composed from the reports below them, never re-written. If a manager is re-authoring status rather than composing it, the roll-up has broken — and the reporting burden SSLM exists to remove has crept back in. Each layer reads the one below at its top level only. The tier mechanics live on Scale; this page owns the office and role.
A PMO's metrics measure whether the system is healthy, not whether one project is on time — and under SSLM they come straight from the instruments the office already compiles, so they double as your position on the maturity journey.
| Signal | What it tells the office | SSLM source |
|---|---|---|
| Reference coverage | Every live artefact carries its Project Reference. Gaps mean documents are drifting out of the story. | Project Reference · PTIP |
| Reporting cadence adherence | Weekly and monthly reports arrive on the beat. Missing updates are the earliest sign a project is slipping quietly. | Weekly Update · Monthly Report |
| RAG honesty (watermelon check) | A run of greens then a sudden red exposes hidden problems. Watch trend, not just colour. | RAG-Trend reporting |
| Health-Check completeness | Average completeness (1–5) shows whether projects are being run properly — resourcing, RAID, closure readiness. | Project Health-Check |
| Assurance maturity | The 0–10 gate scores reveal systemic weak spots — e.g. closure and lessons consistently low across the portfolio. | Assurance Assessment Tool |
| Template-version compliance | Projects on the current standard blocks, not private forks — where consistency leaks away. | Version Control & the custodian habit |
| Lessons fed back | Lessons captured and turned into a template improvement — the rate the standard actually gets better. | Lessons Learned · Continuous Improvement |
Keep the set small and cheap to read. A PMO that builds a heavy metrics machine has broken its own Right-size governance — measure what changes a decision, and nothing more.
Each level below shows both tracks: how the office matures, and how you mature alongside it. It's a map, not a ladder you must climb — add a level only on a real trigger.
Each rung up this ladder is a paradigm shift, not just more of the same — like going from a child's bike to the Tour de France: the mechanics of riding never change, but the skill, discipline and thinking do. The SSLM principles persist and become instinctive; the skill mix shifts from tangible and technical toward relational and strategic — influence over command, judgment over process. The trap is running the new race the old way: standing up an EPMO with a project manager's reflexes. The fuller treatment — and the source, Marshall Goldsmith — is on New to Project Management.
This is a real, honest destination — not a failure. A well-run hybrid office that fits its organisation beats a value-stream transformation it can't resource. Keep the summit as your direction of travel, not a mandate.
The pinnacle of PMO maturity is an office that operates in a value-stream-oriented organisation. SSLM already carries the mechanics — see the value-stream section on Scale and the SSLM & Value Stream Project Management guide.
Don't stand everything up at once. Each activity matures on its own track across the rollout — a phased grid, not a big bang.
| EPMO activity | P1 | P2 | P3 | P4 | P5 | P6 |
|---|---|---|---|---|---|---|
| Strategic alignment to business units | 1 | 2 | 3 | 4 | 4 | 4 |
| Roles & responsibilities | 1 | 1 | 2 | 2 | 3 | 4 |
| Governance & policy | 1 | 1 | 1 | 2 | 3 | 4 |
| Reporting | 1 | 1 | 1 | 1 | 2 | 2 |
| Planning | 1 | 1 | 1 | 2 | 2 | |
| Pipeline management (PTIP) | 1 | 1 | 1 | 2 | ||
| RAID + decisions & action logs | 1 | 1 | 2 | 2 | 3 | 3 |
| Change control | 1 | 1 | 1 | 1 | ||
| Finance & cost management | 1 | 2 | 3 | 3 | 3 | 3 |
| Resource management | 1 | 2 | 2 | 3 | 3 | 3 |
| Procurement | 1 | 2 | 2 | 2 | 3 | 3 |
| Knowledge & document management | 1 | 1 | 2 | 2 | 3 | 3 |
| Quality assurance | 1 | 1 | 2 | 2 | 2 | |
| Capability uplift / training | 1 | 1 | ||||
| Tools & technology | 1 | 1 | ||||
| Change management | 1 | 1 | 2 | 2 | ||
| Communications | 1 | 1 | 2 | 2 | 3 | 3 |
| Benefits management | 1 | 1 | 2 | 2 | ||
| Reference class forecasting | 1 | 1 |
A practical self-check, built from the roadmap above — each item is one of its activities made observable. Tick what's genuinely in place. Roughly, the deepest stage you can tick in full is where the office sits, and the first stage you can't is where to focus next.
0 of 20 in place
Watch the information move. It is entered once, at the source, then composed upward — and the office assures it is coherent before it ever reaches the executive.
Progress against milestones, plus every risk, issue, dependency, action and decision — logged as they arise. The foundational trio.
The week's RAG and trend, drawn straight from the trio — not re-typed. Red and Amber surface.
Do the elements agree? RAG ↔ RAID ↔ milestones ↔ spend ↔ narrative. Anything that doesn't reconcile is challenged before it proceeds.
Agenda built from Red/Amber RAID and a look-ahead; the forum decides; minutes capture it.
Composed from the month's assured weeklies — the portfolio view the board governs from.
Fund, hold, stop, or approve a change — the call only the board can make.
The checkpoint is the point. A conduit passes information up; a PMO assures it first. Reviewing each submission, the office reads the elements against one another and challenges what doesn't add up — because a decision is only as good as the coherence of the data beneath it.
Follow one item. A vendor slip logged Monday as R-07 → flagged Amber in Friday's Weekly → the PMO checks it against the milestone and the spend and confirms the Amber is honest → tabled at the SteerCo → escalated in the Monthly Report → the board approves a two-week extension → recorded as DEC-014, and R-07 updated. One entry, one assured loop, nothing re-typed.
The point of the loop. The office's real deliverable to the executive isn't a report — it's trustworthy information for a decision. That's why Plan, RAID and the Weekly are foundational, and why it takes influence, not authority, to challenge a regional head's Green. For the tier model, continue to Scale; for every template the office assures, see Templates & Guides.