Every programme I’ve worked on has had someone who knew the plan inside out.

Far fewer have had someone equally clear about what happens to people the morning after go-live.

That second person is meant to be the Business Change Manager. Too often they’re treated as the support act. Brought in late. Given the role on top of a day job. Asked to report on readiness in a meeting that has already moved on to the next milestone.

My starting point is simple. A programme only succeeds if both the capability and its adoption succeed. A brilliant system nobody uses has failed. So has a willing workforce with nothing fit for purpose to work with. There is no main act here. Both are the programme.

Programme management guidance, with MSP the most familiar, splits leadership into two responsibilities. Both report to the Senior Responsible Owner, the business sponsor.

The Programme Manager delivers the capability. They run the projects, manage the dependencies, and make sure the new systems, processes and structures arrive on time and fit for purpose.

The Business Change Manager makes that capability deliver the benefits the business case promised. They prepare the business, lead the transition, embed the new ways of working, and stay until the benefits are real rather than forecast.

One builds it. The other makes sure it’s used, and that it works.

The two are peers by design, and that matters. When business change reports into delivery, adoption becomes a workstream. It competes for the same budget, time and attention as the build. When delivery comes under pressure, and it always does, adoption is what gets squeezed.

Keeping them as peers creates a deliberate tension. Is it built? Is it working for the people who have to use it? Both questions need someone standing behind them.

This is the part I think we underestimate.

If the two roles are peers, the sponsor is the only person above both. They can’t just follow the delivery dashboard. They have to understand progress on the capability and progress on the business transition, and weigh one against the other. That is a far more involved job than most sponsors expect, or are given time for.

So, quite understandably, many sponsors look for one person to cover both. They appoint a programme director and expect them to own the whole outcome. It feels like good delegation. One point of leadership. One report to read.

But a programme director following the method sees the Business Change Manager as a peer. Business change is someone else’s responsibility. Their attention goes where the role description points it: scope, schedule, cost, dependencies, delivery risk. Not negligence. Just the job as written.

Then the sponsor delegates leadership of the business side to them anyway, and the tension becomes personal. The Business Change Manager believes they’re a peer but is being led by someone measured on dates. They know the value of readiness, confidence and behaviour. Their boss knows the value of a green milestone. They either defer or push back. Neither does the programme much good.

The structure was designed to put the tension in the sponsor’s hands. Hand it back down and it doesn’t disappear. It lands on the person with the least authority to resolve it.

Beyond the sponsor, a few familiar patterns keep the Business Change Manager in the shadows.

Programmes are funded, staffed and reported around delivery. Milestones are visible. Readiness and confidence are harder to put on a RAG status, so they get less airtime.

The role is an add-on. It goes to a senior operational manager on top of their day job, or to a change specialist with the skills but no authority in the operation.

The role arrives late. The Business Change Manager turns up near handover and inherits something they didn’t shape, with benefits they never signed up to.

And the programme closes when the last deliverable lands, while the benefits profile runs on for another eighteen months. The delivery team moves on. The sponsor’s attention shifts. The benefits fall into the vacuum between project and business as usual.

I once programme managed the offshoring of a set of business processes. There was some technology, but most of the work was people: setting up processes, transferring knowledge, and establishing how two sets of teams would work together.

Delivery was training and systems, followed by an explicit three-month transition phase. We tracked volume and quality, and signed nothing off until every stakeholder had the confidence to say the operation was fit for purpose across people, process and performance.

Nobody questioned the extra time. Those three months were going to happen with or without oversight. The oversight simply meant we could see what was really going on. Offshoring was seen as high risk, so the evidence mattered. Performance didn’t dip. It came in better than target.

But the real signal wasn’t on the dashboard.

It was when the conversations changed. The onshore and offshore teams started talking directly to each other. Detailed queries. Support flowing both ways. Between the people doing the work, not the people managing the process.

That’s when the momentum took hold. And it lasted well beyond the three months.

This is the heart of it for me.

The Programme Manager holds the plan. The Business Change Manager holds the lived experience. Every programme has both running in parallel, and the distance between them is the Human Gap. The plan says done. The people living with the change say not yet.

The plan is well served by method. The lived experience needs its own toolkit, and there’s no shortage. Most programmes stop at Prosci and ADKAR, and they’re useful. ADKAR shows you where individuals are stuck. The Prosci triangle reminds you that sponsorship, project management and change management have to work together.

But the role has to go further. You only have to look at the leading change models.

Lewin reminds us that change needs time to settle, and the refreeze doesn’t happen at go-live. It happens in the months after, exactly when most programmes stop watching.

Kotter asks whether short-term wins are being noticed and whether the change is being built into how the organisation runs.

The McKinsey Influence Model asks whether people see leaders behaving differently, understand why it matters, have the skills, and are backed by the targets and processes around them.

Nudge thinking asks whether we’ve removed the small barriers that make the old way easier.

BCG’s Change Delta pairs executional certainty with enabled leaders and an engaged organisation. Executional certainty on its own is the plan. The other two are the lived experience.

Different lenses. Same question. Is this change actually landing with people?

Numbers matter. Volumes, quality, adoption rates, performance against target. But numbers tell you what happened. They don’t tell you how it feels, or what’s coming next.

The qualitative signals are often the early warnings. What kind of questions are people asking? Are they the questions of people trying to make it work, or of people looking for a way round it? Who is asking whom for help? Are the workarounds growing or shrinking? What’s being said in the team chat, and in the corridor after the town hall?

In my offshoring programme, the shift in the conversations told me more than any dashboard did.

A Business Change Manager who only reports the dashboard is reporting the plan. The job is to report the lived experience too. And to have the standing to be heard when the two don’t match.

None of this is new. The role exists because someone recognised long ago that delivering capability and realising benefits are different jobs. What’s missing is the respect we give that second job. In budget. In time. In voice.

It would mean the Business Change Manager in the room from day one, co-owning the business case and defining what “ready” means. Readiness carrying the same weight as progress, with an equal voice at go/no-go. Transition treated as a phase with evidence-based exit criteria, not a fortnight of hypercare. Someone named to own the benefits tail long after the delivery team has gone.

And it would mean sponsors accepting that sitting above two peers is an active role. You can’t delegate the tension away.

So here’s the question I’d put to any sponsor.

Are you listening to the plan, or to the lived experience?

A programme only succeeds when you’re listening to both.

Whatever next?