Most organisations know they need to change. The harder question is where to start, who to trust, and how to move fast without breaking what matters.

‍

Portfolio companies are under pressure to modernise, adopt AI, and show measurable progress within a fixed ownership window, but the businesses that come through that window well aren't the ones that moved fastest. They're the ones that moved deliberately.

‍

Three tensions sit beneath every transformation programme

‍

The first is the pressure to adopt AI without a clear strategy or measurable outcome attached to it. Boards want to see AI in the plan, and that pressure alone leads a lot of businesses to bolt tools onto existing processes rather than actually changing how the organisation operates. It looks like progress in a board update.

‍

The second is legacy architecture that makes modern delivery slow, fragile and expensive. This one is less visible day to day, but it's usually the reason a transformation programme that looked straightforward on paper takes twice as long as planned. You can't layer new capability onto infrastructure that was never built to support it and expect it to hold.

‍

The third is the gap between technology investment and measurable business value. This is the one that matters most commercially, because it's the one a buyer or a board will eventually ask about directly. Spend on technology doesn't automatically translate into value created. Something has to connect the two, and that something is usually the operating model around the technology, not the technology itself.

‍

Why process-led transformation fails

‍

Transformation fails when it's led by process rather than outcomes. Roadmaps that optimise for governance theatre rather than commercial value get expensive fast, and they get expensive in a way that's hard to see until well after the budget has been committed.

‍

The alternative is starting with the outcome and reverse-engineering the programme from there, rather than starting with a framework and hoping the outcome follows. This sounds obvious stated plainly, but it's genuinely rare in practice. Most transformation work still starts with a technology decision (which platform, which tool, which vendor) before anyone has properly interrogated what the business is actually trying to achieve.

‍

The technology is usually the easy part. The harder part is the operating model, the governance, the review discipline, and the people change that makes any of it stick. A new platform without a changed way of working just becomes an expensive version of the old way of working.

‍

What does discovery before delivery mean?

‍

One practical way this shows up is in how a transformation programme gets scoped in the first place. Understanding the commercial reality of a business before the technical one changes what gets prioritised. What is the business actually trying to achieve? Where is value being lost today? What does the architecture genuinely look like, rather than what the documentation says it looks like?

‍

A timeboxed discovery phase, typically a matter of weeks rather than months, that produces a prioritised roadmap rather than a long report is a very different starting point than a technology vendor walking straight into implementation. It forces the outcome to be defined before the delivery team is assembled, which sounds like a small sequencing difference but changes almost everything downstream, including who ends up on the team and what they're actually being asked to deliver.

‍

Capability transfer has to be designed in

‍

The other thing that separates transformation programmes that hold up from ones that don't is what happens to the capability once the external team leaves. Every engagement should be designed for handover from day one. If capability transfer is an afterthought, tacked onto the final few weeks of a programme, it rarely actually transfers. The business ends up more dependent on external support to keep the new system running than it was before the engagement started, which is the opposite of what digital transformation is supposed to achieve.

‍

This matters specifically for PE-backed businesses because of the exit timeline. A transformation programme that leaves a business dependent on the consultancy that built it is a liability at exit, not an asset. Buyers are increasingly testing exactly this: whether the capability sits with the organisation itself, or with two or three people who happen to understand how it works. The businesses that come through that scrutiny well are the ones where the operating model, not just the platform, changed as part of the programme.

‍

Speed and rigour are not in conflict

‍

There's a common assumption that moving fast and being rigorous pull against each other, that you have to sacrifice one for the other. In practice, done well, they reinforce each other. The right team, with the right framing and a properly scoped discovery phase behind them, ships faster and ships safer than a larger team working without either.

‍

That's really the core distinction in how digital transformation gets approached in PE-backed businesses today. It's not a question of whether to move quickly. Every portfolio company is under pressure to move quickly. It's a question of whether the speed is built on a properly understood commercial reality, or whether it's speed for its own sake, dressed up as progress and unlikely to survive the scrutiny that comes at exit.

‍