Why the Last One Did Not Take
Most PMOs are built to report, so they produce reports. The projects carry on as before, each with its own numbers, and the office becomes overhead with a logo. When budgets tighten, it is the first thing cut, and everybody quietly agrees that is fair.
Red means blame, so nothing goes red until it is too late to be useful. Capable project managers fail for structural reasons, get replaced by other capable project managers, and those ones fail for the same reasons.
There is a simple test.
If your PMO disappeared on Monday, would any decision be made differently by Friday?
If the answer is no, what you have is a reporting function. And reporting functions are always the right thing to cut.
A decision engine is the other kind. It changes what gets funded, what gets fixed and what gets stopped, because the information in front of leadership is real and somebody has the authority to act on it.
This page is for you if: you fund projects through a committee that sees slides rather than numbers, your organization runs more projects than it can actually see, or you have capable project managers and no decision engine around them. And if you are the one who has to explain it when a project lands badly.
What Makes It a Decision Engine
Four things separate the two kinds of PMO, and none of them is a better template.
Decision rights, written down.
The charter states what the function decides, what it recommends, and what it escalates, and your sponsor signs it. A PMO with no authority can only describe. Most were never given any, which is why most only describe.
Criteria, not opinions.
Project health is scored against defined criteria, so red is a fact rather than an argument. Status meetings stop being negotiations about what colour something is.
Thresholds agreed in advance.
What has to be true for a project to be escalated, re-baselined or stopped is settled before anything goes wrong, while nobody is defending a position. Afterwards is too late to agree it, because by then everyone has a stake.
A decision log.
Every material decision recorded with its owner, its date and its reasoning. So the next debate starts where the last one ended, instead of relitigating a settled question from memory.
The output is not a better status pack.
It is that funding, fixing and stopping happen earlier, on evidence, with someone's name against them.
Structure You Can Run Without Us
Five phases, each with defined entry criteria, fixed deliverables and exit criteria that have to be met before the next one starts. You always know where the engagement is, and what ends it.
Diagnose
We interview your stakeholders, review the documents and the tooling, take a portfolio snapshot, and score your delivery maturity against defined pillars. You get a scorecard and a prioritized roadmap. Fixed fee, and it stands on its own if you go no further.
Design
We decide what the PMO will be before anyone builds it: operating model, mandate, decision rights, success measures, reporting structure. It ends in a charter your executive sponsor signs. No charter, no build.
Establish
We produce the kit, configure the tooling, stand up the portfolio view, and pilot the whole thing on two or three live projects, because friction only shows up under load.
Embed
We train your people, coach your PMO lead, and hand the cadence over piece by piece until they are running it and we are watching. There is a named internal owner and a formal transition sign-off. This is the gate that ends our hands-on involvement, and it is written down at the start.
Sustain
Optional and ongoing. We re-score the pillars each quarter and give the executive sponsor an independent read on how their own team's PMO is performing, benchmarked against anonymized peers. Accountability, not outsourcing. The office stays yours.
What You Get
1 / The Baseline
A maturity assessment of your delivery function scored against objective criteria, with the gaps ranked by what they are costing you, and a roadmap that says what to fix first.
2 / The Kit
Governance framework, health criteria, charter, playbooks, dashboards and templates. Branded, versioned, and yours to keep and maintain.
3 / The Decision Rhythm
Strategic portfolio reviews on a defined cadence, with decision rights, thresholds and a decision log behind them, so leadership funds, fixes and stops on evidence, before anything is on fire.
4 / The Handover
Your people trained and running it, a named internal owner, and a written definition of done for every phase, so nobody has to guess whether we are finished.
What This Does for Your Position
The point of a delivery function is not tidier reporting. It is that you stop being surprised in front of people whose confidence you need.
When the quarterly scorecard is produced by someone who does not report to you and has no stake in the result, two things follow. Your good news is believed, because it did not come from you. And your bad news arrives while it is still small, in a room where you can still do something about it.
Governance you did not write is worth more than governance you did.
Right-Sized, Not Maximum
There is no single correct PMO, and the most common way to fail is to build more governance than the organization will tolerate.
So we make the choice explicit and put your sponsor's name on it. A supportive office provides standards and services to teams that are already capable. A controlling office sets standards and checks compliance through gates and reviews. A directive office supplies and manages the project managers itself, which is the right answer only where delivery capability is genuinely absent.
For most mid-market organizations the answer is somewhere between supportive and controlling: enough assurance to give leadership confidence, without the bureaucracy that gets PMOs disbanded. Control can increase later as maturity grows, and the roadmap says when.
We target a solidly defined, consistently practised function inside the engagement, with selective depth where it pays back. We do not promise top-of-scale maturity everywhere. Over-engineering is how PMOs talk themselves into failure.
Amir Asadiara and Suchit Ahuja, John Molson
School of Business, Concordia University
Same tools, different builders: Why digital transformation diverges, August 2026
Which is why the operating model is a decision your sponsor signs, not a template we arrive with.
Frequently Asked Questions
Is this just an old-fashioned PMO with a new name?
Fair question, and usually the answer would be yes. What separates the two is decision rights, defined health criteria and thresholds agreed before anything goes wrong. Those are the things that let a function change an outcome rather than describe one. If your PMO already has all three, you do not need us. Most do not, which is precisely why most get cut in the first hard budget cycle.
Will you run the PMO for us?
No. We install and assure PMOs, we do not staff them. If we ran it, you would have rented a PMO, and it would leave when we did.
We built one before and it became overhead.
Most do, because they were built to report rather than to decide. The test of ours is whether decisions change: whether leadership funds, fixes or stops differently because of what the function shows them.
We genuinely do not have the people.
Then we can arrange managed staffing through a partner, under our governance and our operating model, time-bound with a transition plan back to your own people. It is a bridge, not a destination, and we will say so in writing.
Do we need new tools?
No. The framework is tool agnostic and works with what your teams already use. If a gap shows up in the Diagnostic we will name it, but we do not arrive with a product to sell you.
What if one of our projects is already in serious trouble?
That project needs a review of its own, which is Project Salvage. The portfolio needs this. The two are designed to meet in the middle.
How long before it stands on its own?
The Diagnostic answers that for your organization. Every phase has a defined exit, so "done" is written down before we start.
What does it cost?
The Diagnostic is a fixed fee, agreed before we start. The Build is fixed scope, priced from what the Diagnostic finds. No hourly billing, and no open-ended consulting meter.