Most organisations don’t find out their PMO isn’t ready for complex delivery until they’re already in the thick of it. The programme that looked manageable starts sprawling. Dependencies nobody mapped begin colliding. Reporting that worked fine for a handful of projects buckles under a portfolio of interlinked ones. And suddenly the question everyone’s asking, usually a bit too late, is: were we ever set up for this?
The honest answer is that you can know the answer in advance. You just have to be willing to look properly. That’s what a capability assessment is for.
Maturity models, minus the jargon
The idea behind a maturity model is simple, even if the frameworks around it can feel needlessly heavy. It’s a way of describing how good your organisation actually is at delivering projects and programmes and crucially, how consistently.
At the lower end, delivery tends to be reactive and personality-driven. Things get done because a few brilliant people pull heroics, not because the organisation has a dependable way of working. Success is hard to repeat because nobody’s quite sure why it happened.
In the middle, you start to see real process. There are standards, they’re mostly followed and delivery becomes more predictable. People aren’t reinventing the wheel on every project.
At the top end, delivery is genuinely managed and improving. The organisation measures how it’s doing, learns from it, and gets better on purpose rather than by accident. Complex, high-stakes programmes feel less like a gamble.
The point of a maturity model isn’t to slap a number on your forehead and call it a day. A level is just shorthand. The real value is in the conversation it forces: where are we actually strong, where are we exposed, and does that match the complexity of what we’re about to take on? Plenty of organisations are perfectly mature for steady, business-as-usual delivery and nowhere near ready for a transformation programme. The gap between the two is exactly what catches people out.
The four things worth measuring
A good capability assessment looks across four dimensions. They’re connected, weakness in one drags down the others, so it’s worth understanding each on its own terms.
- People. This is the one everyone nods along to and then underinvests in. It’s not just whether you’ve got enough project managers. It’s whether you’ve got the right skills for the work in front of you, whether roles and accountabilities are clear and whether people are actually developing rather than just surviving. Complex delivery demands judgement, not just process-following and judgement comes from experienced, well-supported professionals who know how to navigate ambiguity. If your capability all lives in two or three indispensable individuals, that’s not strength. That’s a single point of failure wearing a cape.
- Process. Here the question isn’t “do we have processes?” It’s “do they work, are they actually followed and do they flex when the work gets harder?” A lot of organisations have plenty of process, it’s just that half of it is theatre nobody believes in and the parts that matter for genuinely complex delivery (managing dependencies, integrated planning, proper risk and assurance) are thin. Good process should make delivery easier under pressure, not add friction when you can least afford it.
- Data. This is where the cracks usually show first. Can you trust your delivery data? Is it consistent enough that you can compare projects, spot trouble early and give leadership a portfolio view they actually believe? In a lot of organisations the answer is a polite no, the numbers are assembled by hand, they’re a fortnight out of date by the time anyone sees them and everyone has their own version. You cannot manage complex, interdependent delivery on data you don’t trust. Confidence in your numbers is, quietly, one of the biggest capability differences between organisations that cope with complexity and those that don’t.
- Tools. Tools are the enabler that ties the other three together, or undermines them. The right tooling gives you consistent data, a real-time view and less time lost to manual chasing. The wrong tooling, or a great tool used badly, leaves your people drowning in admin and your processes living in spreadsheets nobody maintains. The test isn’t how sophisticated the platform is. It’s whether it actually makes good delivery easier for the people doing the work.
Look at these four together and a clear picture emerges. It’s rarely “we’re bad at everything.” It’s far more often “we’re strong on people and process, but our data and tools can’t support the complexity we’re heading into.” That kind of specific, honest insight is worth far more than a maturity score on its own.
Why a diagnostic is a value lever, not a box-tick
It’s tempting to treat a capability assessment as a tidy-up exercise, something you do because good practice says you should. That undersells it badly.
A proper diagnostic is one of the highest-leverage things you can do before committing serious money to a complex programme, for a simple reason: it tells you where your risk actually is before it costs you. The price of finding a capability gap in a two-week assessment is trivial next to finding it halfway through a delivery, when the only options left are expensive and disruptive.
It also stops you spending in the wrong places. Without a clear-eyed view, improvement money tends to chase whatever’s loudest, usually new tools, because tools are tangible and easy to buy. But if your real constraint is capability or data quality, a shiny new platform just gives you a faster way to produce information you still can’t trust. A diagnostic points the investment at the constraint that’s genuinely holding you back, which is where it earns its return.
And there’s a quieter benefit. A good assessment builds a shared, evidence-based picture across leadership, replacing the usual mix of gut feel, defensiveness and competing anecdotes with something everyone can actually act on. That alignment, on its own, is often worth the exercise.
The best diagnostics don’t just hand you a report and leave. They give you a prioritised, realistic view of what to fix, in what order and what difference each move will make.
A capability assessment is a starting line, not a finish line
Here’s the thing worth holding onto: a capability assessment is most valuable when it feeds something ongoing, not when it sits in a drawer.
Maturity isn’t a destination you arrive at and then relax. The organisations that handle complex delivery well are the ones that treat capability as something they keep working on, measuring, learning, and deliberately getting better over time. A one-off assessment tells you where you are today. A culture of continuous improvement is what turns that snapshot into momentum, so the next complex programme finds you stronger than the last one did.
That’s the real prize. Not a score, but the habit of getting better on purpose.
Where to start
If you’ve got a complex programme on the horizon, or one that’s already feeling harder than it should, the most useful thing you can do is find out where you genuinely stand before the stakes get any higher.
That’s exactly what we help organisations do. If you’re not sure your PMO is set up for what’s coming, let’s talk. We’ll give you an honest, evidence-based read on where you’re strong, where you’re exposed, and the few moves that will make the biggest difference. theteam@projectone.com