Blog | How to elevate your Transformation Office to deliver at scale against your strategic objectives

Blog by Darryl Petticrew, Director, Transformation Delivery

I've spent the best part of two decades working with senior leaders to deliver on their Transformation strategy and unlock real value to their business. Teams tend to get bogged down in doing the work, setting up the governance arrangements, mobilising SMEs and tracking progress. And yet, many organisations struggle to connect transformation delivery with strategic outcomes.  

The honest answer is that most transformation programmes are set up for output, focused on delivering the scope of work, rather than on delivering value to the organisation that will enable transformation. Those are two very different things. And until we're clear on that distinction, we'll keep hitting our milestones and missing our ambitions.

Below, I've tried to unpack the most common questions I get asked when I raise this with leaders. I hope it's useful whether you're in the middle of a programme right now or starting to think about what comes next.

Q: Isn't transformation just about delivering outputs well?

Outputs are tangible. Milestones can be tracked. Ownership is usually clear. Measuring whether something has been delivered is a straightforward way to demonstrate progress.

But here’s the problem: delivering outputs doesn’t automatically mean you’re delivering transformation.

An organisation can complete every milestone, launch every workstream, and deliver every agreed-upon output on time, yet still fall short of the strategic ambition that transformation was meant to achieve.

Why? Because outputs are not outcomes.

When teams focus on delivering their own outputs in isolation, it becomes easy to optimise for activity rather than impact. Effort gets duplicated, resources are stretched, and delivery can quietly drift away from the bigger strategic objective.

Transformation is not about completing a collection of deliverables. It’s about creating measurable organisational change and business value.

That’s what makes transformation different from project delivery.

Transformation should be treated as a connected system, not a series of independent outputs. And while marking a milestone complete is relatively easy, measuring whether the transformation is delivering outcomes is much harder, and far more important.

Q: Why do so many transformation programmes end up pulling in different directions?

Because they're not designed to pull together. Most of the governance focuses on individual initiative health, RAG statuses, milestone tracking, and risk registers. That's all necessary and I love that discipline. But it doesn't answer the harder question: “Is this, collectively, moving us towards our strategic ambition?”

Without that view, teams face misaligned priorities, uncoordinated activity, and inconsistent benefit expectations. Delivery teams end up absorbing the cost of decisions that were made in isolation upstream.

The fix isn't more governance. It's a different kind of orchestration, one that connects initiatives, clarifies dependencies, and keeps the whole transformation oriented around what the organisation is actually trying to become. Keeping transformation connected to strategy is key here, so delivery and business teams see how what they are delivering on the ground impacts the overarching strategy. I’ve seen this done in lots of ways depending on the context, some use OKRs, Value Creation Frameworks (typically in a PE context), Value Trees, Value Streams – this list goes on. The important point is choosing the most relevant way to connect strategy to transformation for your business and building anchor metrics around the key value drivers that will enable it.

Q: Why is change readiness still such an afterthought?

Partly habit, partly incentive structure. Project teams are measured on delivery, scope, time, and cost. Change readiness is seen as someone else's problem, usually a communications or HR function, and it tends to surface as a tick-box exercise in the final weeks before go-live.

But that's far too late, and far too narrow. Real change readiness isn't a pre-launch checklist. It's about whether the organisation has the capacity, structures, and behaviours in place to absorb and sustain what the transformation is asking of it.

When that's missing, you see consistent challenges with adoption, workarounds that undermine the intended design, and a gradual drift back to old ways of working. The work is delivered. The change didn't stick. My advice, embed change and business readiness into your planning at the start and bring the right people into the room to help land the change you’re delivering.

Q: Business cases get approved, but the value never seems to materialise. Why?

Because the business case is often the finish line, when it should be the starting pistol.

Once investment is approved, accountability for value realisation tends to fragment. The project team moves on to delivery. The finance team tracks budgets. The business owns the outcomes in theory, but in practice, there's rarely a clear mechanism to measure whether the expected value is actually being generated.

Realising value requires active tracking, clear ownership, and the willingness to course-correct when the numbers aren't moving in the right direction. That's not a one-off exercise. It's a discipline that needs to be built into the portfolio's operations from day one. Most people write benefits down but rarely focus on them during delivery; it tends to become something that’s done at the end. But what most are missing is that the project or programme is meaningless unless it drives value or benefit to the business. During the business case process and in delivery, focus on delivering value and ask yourself often, ‘what does this mean for our value drivers / benefits’.

So, what does genuinely successful transformation delivery look like?

In my experience, it has four characteristics. The portfolio is coordinated around clear strategic priorities, not just a list of approved projects. Initiatives are orchestrated as a connected system, with shared dependencies and aligned sequencing. Value realisation is actively managed, not just hoped for. And the changes made are embedded into organisational capability, so they last beyond the programme.

That's not a complicated idea. But it requires a deliberate shift in how transformation is planned, governed, and delivered. And it requires someone to hold the end-to-end view, which most organisations don't have a clear owner for.

These aren't new problems. But they're the ones who tend to get pushed aside under the pressure to deliver, until the programme ends and the honest conversation begins about what actually changed.

The questions above underpin how we deliver transformation at Lancia Consult. They’re also embedded in how we work day-to-day through CORE Transformation Delivery.

Introducing CORE: Transformation Delivery  

Turning Transformation into Organisational Capability

CORE is our transformation delivery framework, built around the belief that effective transformation requires an end-to-end organisational view in which change, delivery, and value are managed as one for the portfolio as a whole, not initiative by initiative.

It works across four connected dimensions:

Coordinate

Align your portfolio around clear strategic priorities and outcomes

Orchestrate

Connect initiatives, teams, and dependencies so transformation works as one system

Realise

Build the tracking and accountability mechanisms that drive measurable value

Embed

Build the structures and behaviours that make change stick

If any of the questions in this piece resonate with what you're seeing in your organisation, we'd love to talk.

Learn more about CORE here.

Book a conversation with the team here.

Darryl Petticrew

Director, Transformation Delivery

Darryl leads Lancia Consult's transformation delivery practice, working with organisations to build the portfolio capability needed to turn strategic ambition into lasting organisational change.

‍

‍

‍