ADLC: SPM != PMO
Part of the ADLC series. The other piece argued the portfolio is the front door to the lifecycle. This article is about the office standing at that door, and how most traditional PMOs are designed to keep the door shut.
Strategic Portfolio Management Is Not a Better PMO
Part of the ADLC series. The last piece argued the portfolio is the front door to the lifecycle. This one is about the office standing at that door, and why most of them are built to keep it shut.
A traditional PMO is built to make the work conform to the plan. Strategic Portfolio Management is built to do close to the opposite, and no amount of buzzwords turns one into the other.
BLUF: Most enterprises that tell me they’re “moving to SPM” are running a traditional PMO with new terminology, which is a category error and an expensive one. A traditional PMO is an instrument of control: it standardizes method, enforces phase gates, and scores delivery as conformance to a plan and a budget set in advance. Strategic portfolio management is an instrument of allocation: it decides what’s worth doing against strategic intent and moves money toward evidence as the year unfolds. The two differ in form (where they sit, who they answer to, what they produce) and in function (the question each one is built to ask). Lean Portfolio Management, a body of knowledge I’m proud to have contributed to, was the bridge between them and pointed the right way as early as 2019, though it carries a ceiling that SPM done well is the thing to finally clear. Install SPM tooling on top of PMO instincts and all you’ve bought is a faster way to produce the same green status deck. The platform isn’t the function, and this piece is about the function.
I was in a portfolio review a while back, the kind that happens every quarter in every large enterprise, watching a wall of initiatives glow green. The status was green, the spend was on plan, the milestones were tracking. Everyone in the room understood, but nobody had the courage to say anything about it, that at least a third of what we were looking at had lost relevance sometime in the prior two quarters, and that the green measured how well teams were executing against the plan rather than whether the plan was still worth executing. The office running that review was doing its job perfectly, which was the problem. We knew the work needed to stop, to ignore sunk costs, and pivot to what was now right, but the system wasn’t designed for that conversation.
The PMO isn’t a failure of competence, but a discipline pointed at the wrong objective.
The failed rebrand.
Watch what most organizations do when they decide to modernize the portfolio. They buy a strategic portfolio management platform, point the existing PMO at it, and keep the same governance body, the same intake form, the same gate reviews, and the same definition of a healthy project. In fact, they may even customize the new tool to support the old patterns. Then they wait for the strategy-to-execution gap to close, and it of course doesn’t, because they changed the tooling and left the function untouched.
The reason it fails is that the PMO and SPM aren’t the same office at different points on a maturity curve. Gartner draws the line cleanly: project portfolio management is about doing things right, and strategic portfolio management is about doing the right things. That sounds like a slogan until you sit with what it implies. Doing things right is a conformance question, and it assumes the right things have already been chosen and the job is to deliver them on schedule and on budget. Doing the right things is an allocation question, and it never closes, because the right things keep changing underneath you.
You can’t get from the first to the second by tightening the first. A PMO that runs flawlessly produces flawless conformance to a plan that may already be wrong, and more rigor only sharpens the fit to something that was no longer worth fitting.
What SPM is.
Strategic portfolio management is the coordinated management of investments, initiatives, and capacity in service of strategic outcomes, operated continuously rather than at an annual gate. The emphasis falls on value and adaptability across the whole portfolio instead of on tracking and reporting against a fixed scope. Gartner named it a distinct discipline precisely because traditional portfolio practices, PMOs and EPMOs included, don’t move fast enough or bend enough to compete at the current pace of business.
Stated plainly, SPM is the bridge between strategy and execution. It decides what’s worth building and funds it against intent, then re-decides as evidence arrives, sitting above the lifecycle as the strategy layer that feeds it.
Definitions are the easy part. The contrast is where this gets useful, because most leaders are running on an unexamined model of how these two offices differ.
Two structures built for different jobs
Start with how each one is built.
A PMO is, in form, a delivery-assurance function. It usually reports into a CIO or a delivery executive. Its artifacts are the project charter, the work breakdown, the RAG status report, the change request, and the stage-gate review. Its unit of account is the project, a thing with a defined scope, a start, and a terminal end. Its calendar is the gate, where work advances once it clears Discovery, Planning, Develop, Execute, and Close, and the governance body grants go, no-go, hold, or modify at each one. Its currency is the plan, and its core skill is variance management, the discipline of noticing when reality has drifted from the plan and pulling reality back.
SPM, in form, is an allocation function. It reports up rather than in, to the office that owns strategy and the P&L, often with the CFO at the table instead of observing from a distance. Its artifacts are the strategic theme, the value stream, the funding guardrail, the portfolio Kanban, and the scenario model. Its unit of account isn’t the project but the bet, a body of work tied to a hypothesis about value, funded continuously, with no assumption of a terminal end. Its calendar is, ideally, the arrival of evidence rather than the turn of a fiscal quarter. Its currency is the capital envelope and the intent that governs it, and its core skill is reallocation, the discipline of moving money toward what’s working and off what isn’t.
Read those two descriptions back to back and the substitution problem becomes obvious. You can’t run an allocation function with a delivery-assurance org chart, a project-shaped unit of account, and a variance-management skill set, because at every point the form fights the function it’s been handed.
Function: the back office and the front office
The cleanest way I’ve found to explain the difference is to borrow from how an investment firm is built, because that’s the business SPM is in.
A PMO is the back office, and the back office is essential. It handles settlement, compliance, reconciliation, and reporting. It makes sure every trade is recorded correctly, that the books tie out, that the firm isn’t exposed to an error nobody caught. A back office that runs well is invisible, and one that runs badly can sink the firm. What it doesn’t do, and isn’t supposed to do, is decide where to put the money. Confuse the two and you get a firm that’s beautifully reconciled and pointed at the wrong positions.
SPM is the front office. The front office holds a thesis, places capital against it, watches the market, and repositions when the evidence moves. It doesn’t measure itself by whether it held January’s positions; it measures itself by return, and the failure it fears most is staying in a position long after the thesis behind it broke. Repositioning isn’t a deviation from the work. It is the work.
A PMO asks whether we’re on schedule, whether we’re on budget, and whether we hit the acceptance criteria, which are the right questions for the wrong problem, the same line I drew in the ADLC piece, now moved up a level. SPM asks what we’re learning, what that learning is telling us to fund more of, and what we should stop funding now rather than next January. Both offices belong in a large enterprise. The mistake is handing the back office the front office’s job and then wondering why nobody’s steering.
Where LPM fits.
If you’ve done any work with the Scaled Agile Framework, you already know there was a halfway house between these two offices, and it was a good one. Lean Portfolio Management took the PMO’s instincts and bent them toward allocation. I’m proud to have had a hand in shaping it, so consider me biased.
LPM got the hard part right. It funded value streams to guardrails instead of funding projects to detailed business cases. It replaced the steering-committee change request with cadence-based portfolio syncs. It gave teams Weighted Shortest Job First so sequencing followed economic value as it was learned, not the order things landed in the intake queue. It put epics on a portfolio Kanban with progression tied to hypothesis validation rather than phase completion. Every one of those moves is a step from conformance toward allocation, and they work, which is why organizations already running SAFe should recognize this as muscle they’ve built rather than theory they have to learn.
This is why LPM feeds SPM so directly. Its funding instinct, money to the capability and the value stream rather than to the named project, is the core of how SPM allocates, and the guardrail-over-business-case posture carries straight across. Run LPM well and you’ve already retired the worst habits of the PMO and learned to think like a portfolio rather than a project office.
Where the two diverge matters just as much. LPM is an operating model that lives inside a delivery framework, built bottom-up from the value streams, prescriptive about ceremonies and roles, and scoped largely to the technology and product organization. SPM is the enterprise strategy layer above all of that, framework-agnostic, executive- and finance-facing, and concerned with the whole portfolio of investment rather than the Agile delivery slice of it. The deeper difference is cadence. Even strong LPM adoptions re-plan the portfolio two to four times a year, and while that was a generational improvement on annual planning, in 2026 it’s still a batch process. The next generation of SPM tooling, the ServiceNows and Planiswares and Claritys I walked through in the last piece, exists to drop the batch and make reallocation event-driven, triggered by evidence instead of by the cadence calendar. LPM moved the portfolio off the annual clock and onto the quarterly one; SPM is the attempt to take it off the clock entirely.
The honest framing, then, isn’t LPM versus SPM. LPM is how a lot of organizations will first learn to think in value streams and guardrails at all, and SPM is where that thinking goes once it outgrows the quarterly sync and reaches the rest of the enterprise.
The strategy layer
Step back and the symmetry is hard to miss. The SDLC was the delivery model of a world where software shipped on a schedule, and the PMO is its portfolio twin, an office built to govern scheduled, scoped, terminal work. The ADLC is what delivery becomes when the work has no finish line and production is a feedback source, and SPM is what the portfolio becomes to keep time with it.
I’ve written that the portfolio is the front door to the lifecycle, the place where strategy enters and becomes work. If the lifecycle downstream now runs every day, and a generation of decisions has already been pushed down to the teams and the agents working inside the guardrails, then a front door governed by a back office that opens once a year on a phase gate is the constraint on the whole system. The ADLC dissolved “build and done” at the team level, and SPM is the same dissolution one floor up, moving the portfolio from monitor-and-control to sense-and-respond and from treating variance as failure to treating deviation as signal. A PMO is built to prevent movement and an SPM function is built to keep movement inside the envelope, which is how two offices can share the same wall of dashboards and be doing opposite jobs.
What this asks of you
None of this is a platform purchase, and I want to be blunt about that, because the vendors will tell you otherwise and the platforms are genuinely good. Buying the tool and pointing your existing PMO at it gives you a more expensive PMO. The function doesn’t change because the software did, any more than buying a Bloomberg terminal turns the back office into a trading desk.
The work is structural and unglamorous. It means moving the reporting line so the portfolio answers to strategy and the P&L instead of to delivery assurance, changing the unit of account from the project to the funded bet, replacing the gate review with an evidence trigger, retiring variance management as the core skill and standing up reallocation in its place, and putting the CFO in the room as a participant rather than an auditor. Every one of those is a conversation with someone whose role was built around the office you’re changing, which is exactly why most organizations announce the platform and skip the work.
There’s a cost to skipping it that never lands on a portfolio dashboard, because dashboards only measure conformance. It shows up as the product leader who learned in Q2 that the bet was wrong and then spent two more quarters delivering it flawlessly anyway, because the office she answers to rewards hitting the plan and has no mechanism to absorb the fact that the plan stopped being true. She did her job and the office did its job, and the strategy still lost while everyone’s status stayed green the whole way down.
The PMO was the right office for work that shipped on a schedule, and that work hasn’t disappeared, so neither should the discipline that governs it. But the portfolio stopped being a delivery problem some time ago. It’s an allocation problem now, and you can’t solve an allocation problem with an office built to keep score. Stop asking the back office to steer.