Is your change plan built on fact or fiction?

Written by Ollie Butcher, Practice Director - Change & Transformation, Robert Walters Consultancy

Many change plans look solid on paper. The scope is agreed, the budget is signed off and the dates are set. But look closer and parts of the plan rest on assumptions nobody has tested.

In my first article I looked at why change succeeds or fails before it starts and how the strongest leaders read the context first. They ask how ready their people are, who really holds the decisions and what else the organisation is already absorbing.

Those questions matter. But on their own they change nothing. An assessment isn't valuable because it identifies risks. It is valuable because it impacts the decisions leaders make before delivery begins.

This article covers what comes next, between assessment and delivery. It shows how to build a plan around the reality of your own organisation.
 

Where the fiction creeps in

In my experience the problem is rarely that context is ignored. It is that it is under-considered. The assessment gets done, then the pressure to start takes over.

That pressure has familiar sources. A sponsor wants a date. A business case needs to land in this budget cycle. Optimism fills the gaps in scope. Senior leaders may not have agreed exactly what the change will and won't include. Each one assumes the plan matches what they have in mind.

None of this feels like a mistake at the time. But anything missed early comes back during delivery as change requests, plans that have to be redrawn and benefits that are compromised or never realised. By then it is expensive to fix.

The risk grows with scale. It is highest in large programs, especially those paired with a significant global operating model redesign. Add several vendors with their own ways of running change and teams spread across global locations. The organisation ends up holding it all together. That is where programs lose the most time and see the biggest impact on budget.

Build the four levers around the assessment

Every program needs a business case before it can mobilise. At its core that business case sets four levers: scope, resource, budget and timeline. Without all four you can't mobilise effectively.

Scope is the starting point because it shapes everything else. Get scope wrong and the budget won't align.  That leads to an unrealistic resourcing profile and timeline. Leave something important out and you spend money on a solution that isn't whole. Include something that shouldn't be there and you may never be able to deliver it. In practice the levers pull on each other. A fixed deadline or budget will push back on scope. But scope is where the conversation must start.

This is where the assessment does its real work. Each lever needs a decision. That decision should always point back to something the assessment found. 

• Scope: decide exactly what you will and won't deliver. Base it on the true scale of change the assessment uncovered, not the scale everyone hoped for.
• Resource: decide who must be involved and what they will stop doing to ensure right-sized capacity. That goes beyond subject matter experts to everyone the change depends on.
• Budget: set a budget that covers the real cost of the change, including the disruption it creates. That is more than the cost of delivering the solution.
• Timeline: set dates that reflect what people are already absorbing. Build in time to recover after go-live.
   

Put it into practice

Say the assessment shows that the experts the program needs are already committed to another change, or at capacity through BAU commitments. A plan built on fiction assumes they will find the time. A plan built on the assessment makes a decision. It might change the sequence so the work lands when they are free. It might fund extra resource to cover their day job. Or it might reduce the initial scope to what they can genuinely support.

Sometimes the assessment shows that readiness is low. That leaves two choices. You can delay the start or start knowingly at risk. There will always be unknowns, so starting at risk is often the right call. What matters is that the risk is named and owned in the plan from the start, then tracked through to resolution. 

I’ve seen what happens when a risk isn’t named. Too often, large global programs mobilise around an ill-defined scope. The budget is signed off and teams are brought on board. But when they start on requirements, design and solution, progress stalls. Nobody has properly worked through how things run today and how they need to run in future.

So the scope gets defined after the program has started. Resetting the baseline eats into the time planned for requirements, design and the technical solution. Output drops, delays build and the timeline stretches.

I’ve also seen this done well. One program was ready to ask for funding, but before sign-off the sponsor arranged a short, time-boxed readiness assessment. It brought the delivery and risk teams together to test the business case.

The assessment found the same gap. The current processes hadn’t been mapped in enough detail, so the size of the change was guesswork. The future design rested on untested assumptions about what the new platform could do. In short, the scope wasn’t defined.

So leadership didn’t approve the full budget. They funded a discovery phase to close the gaps and run a proof of concept with the supplier. The rest of the budget was released at a second gate. Teams were then brought on board with a scope built on evidence, not guesswork. It wasn’t a delay or a gamble. It was a decision based on what the assessment found.

Get ready to deliver the plan

A good business case is necessary but not enough on its own. The organisation must be ready to carry it, and three things make the difference.

Create capacity before you add load. People can't absorb new change on top of everything they already do. Decide what stops, pauses or slows down to make room. Then decide who controls where freed capacity is allocated. 

Put the change operating model in place. A change framework sets out how the change will be governed and run. Each outcome needs one accountable owner. Decision rights need to be clear so everyone knows who settles trade-offs when priorities collide. A simple test is whether you can write down on one page: what's the process and who owns the key decisions. If you can't, you aren't ready.

Make the outcomes clear enough to sequence. Vague outcomes produce vague plans. Clear ones let you decide what comes first, protect recovery windows and keep momentum once delivery starts. 

Then comes mobilisation itself. My one piece of advice to any leader at this stage is to bring every key stakeholder together to start the change formally. Mobilisation is above all a communication moment. But that meeting confirms alignment rather than creating it. The decisions and accountability need to be settled before everyone is in the room.

From that day governance has one job: to control the four levers. Decision owners keep scope stable. Reporting shows early when resource, budget or timeline start to slip. Clear escalation routes mean trade-offs are made quickly by the right people. If governance starts late the levers are already drifting. 

Ready for delivery

So how do you know you're ready? You should have three things in place:

• A business case covering scope, resource, budget and timeline that is shaped by the assessment.
• Governance running from day one with clear decision owners.
• Teams mobilised and ready to start, with everyone clear on their role.
  

That is the line between mobilisation and delivery. From here teams move into requirements, solution design, build and test. The context doesn't stand still while they do. People tire, leaders shift and priorities move. 

In the next article I'll look at delivery itself. That includes how leaders keep control of the four levers as the context changes. 

Test your plan with us

I’ve seen plans that looked solid on paper come apart in delivery, and I’ve seen leaders who took the time to get them right. If you’re building a business case or getting ready to mobilise, I’d be glad to talk it through.

A discovery call is a chance to test your plan against the reality of your organisation, check whether your scope, resource, budget and timeline hold up, or discuss anything else about your change portfolio or program. Complete the form to get in touch.