Promise Integrity: The Missing Discipline in Global Programme Change

Commitment Is Not Consensus: A Practical Guide for EA and TMO Teams

Eighteen months into a major global programme, the home region is live and performing well. The steering pack is green. The programme director is confident.

Elsewhere, the picture is different. One region is slow to adopt because the implementation did not account for local operating constraints that differ significantly from the original design. Another region has thin engagement. Regional leaders are attending governance calls, asking polite questions, and doing very little. Nobody has said the programme is failing. Nobody is saying it is succeeding either.

This is not a delivery problem. The programme is on track. It is a promise problem. And it is exactly the situation EA and TMO teams exist to resolve.

What is actually happening

The home region succeeded because the programme was designed around its operating reality. The promise was legible to local leadership. The trade-offs were visible. The small agreements held.

The struggling regions are experiencing a different programme. Not because the solution is different, but because the promise was never translated into their context. One region sees a solution that adds cost and process friction without a clear local benefit. Another sees a corporate mandate with no obvious connection to how their business creates value.

The gap between what was promised globally and what the business is actually prepared to change locally has never been named. That gap is now showing up as slow adoption, low engagement, and a finish line that keeps moving.

A global promise that is not translated into regional reality is not a promise. It is an instruction. And instructions without commitment produce compliance at best and quiet resistance at worst.

The EA and TMO task is to make that gap visible before it becomes a crisis.

Three disciplines that close the gap

Name the promise in every region, not just the centre

The global promise was clear enough at programme inception. It was not translated.

One region heard: implement the global template. Another heard: comply with the corporate standard. Neither heard a promise that connected to their operating reality, their constraints, or their leadership priorities.

A programme promise cannot be a single document owned by the centre. It needs a version for each major region that answers the same questions in local terms. What will improve for this business, in this context, because of this programme? What must change here for the global promise to hold?

When EA and TMO do this work, two things typically happen. Either the regional translation is straightforward and the engagement problem turns out to be a communication gap. Or the translation surfaces a genuine design tension. That is not resistance. That is evidence. And it requires a decision, not a communication plan.

For the slow-adopting region, that conversation might reveal a real constraint the original design did not accommodate. For the low-engagement region, it might reveal that leaders have never been shown a credible line between the programme and the outcomes they are being held accountable for. Different problems. Different fixes. Both invisible until the promise is translated.

Force the trade-offs that have been avoided

Behind every struggling region there is usually an unresolved trade-off. Standardisation versus local operating reality. Enterprise coherence versus regional engagement. Speed of delivery versus quality of adoption. These tensions exist in most global programmes. When they go unnamed, they surface as adoption problems. They are not adoption problems. They are commitment problems.

Adoption problems get solved with more training and communication. Commitment problems get solved with decisions. Applying adoption solutions to commitment problems produces activity without progress, which is precisely what low engagement looks like from the outside.

A Trade-Off Register makes the choices visible: what was decided, what was rejected, who is affected, what the cost is, and what evidence would reopen the decision. Its purpose is to stop commitments being quietly unpicked through corridor conversations, and to make the cost of continued avoidance explicit to the people doing the avoiding.

For a programme in this position, EA and TMO need to identify the unresolved trade-offs in each struggling region and put them in front of the right decision-makers with the options and costs named clearly. The corridor conversations have not resolved them. A visible, facilitated decision will.

Keep the small agreements

Slow adoption and thin engagement are both telling the same story: somewhere, small agreements have broken down.

In a region with adoption problems, the failures are usually practical. Testing timelines were compressed. Local teams were not given adequate time to validate the design against their operating reality. Concerns were flagged and not resolved. The agreement to treat operational feedback as evidence rather than resistance was not kept.

In a region with engagement problems, the failures are more likely about visibility and voice. Regional leaders were told the programme was global and non-negotiable. Their concerns were heard in governance calls and did not visibly change anything. The implicit agreement that engagement would be reciprocal was broken early.

Trust in a large programme is not built through communication. It is built through the consistent keeping of small agreements. When those agreements break, no amount of stakeholder engagement activity rebuilds the credibility they represented. Only visible behaviour change by leadership does that.

A Commitment Ledger for a programme in this position focuses on three questions. Which agreements were made to struggling regions at programme inception that have not been kept? What does leadership need to do visibly and soon to rebuild credibility? What new agreements need to be made, with real consequences for breaking them, to re-anchor regional commitment?

Where this programme sits and what needs to happen now

A programme in this position is somewhere between governing trade-offs and protecting adoption. That is recoverable, but only if the right interventions happen in the right sequence.

The promise framing work was incomplete. It produced a global statement that did not translate regionally. That work needs to be done retrospectively for each struggling region, not as a communication exercise, but as a genuine clarification of what the programme is promising locally and what it is asking to change.

The commitment testing was insufficient. Regional leadership agreed to participate. They did not agree to the trade-offs participation requires. That conversation needs to happen now, directly, with regional leaders about what they are and are not prepared to do and what the programme needs to flex in response.

Trade-off governance has been absent. The issues in struggling regions have been visible for months. Neither has been escalated as a trade-off requiring a decision. TMO needs to change that immediately, with structured sessions that produce explicit choices rather than further deferral.

Adoption protection is the current priority. Old ways of working are still running in parallel. Workarounds are becoming established. The longer this continues, the harder the old world is to retire. TMO needs to define what good adoption looks like in each region, with named owners and a clear timeline, and present that to regional leadership as a commitment rather than a plan.

The call to action

If this programme is sitting in your portfolio, three things need to happen in the next thirty days.

Run a regional promise review with each struggling region separately. Not a programme update. A direct conversation about what the programme is promising them, what it is asking them to change, and whether those two things are currently aligned. Bring EA to assess the design implications and TMO to facilitate the commitment conversation. What surfaces will be uncomfortable. It will also be actionable.

Put the unresolved trade-offs on the table at the next global steering meeting. The issues in struggling regions are not adoption problems. They are commitment problems that have been managed as adoption problems. Name them as trade-offs, present the options with costs attached, and force a decision. If the steering group defers again, that deferral is itself a decision worth naming.

Audit what was promised to each region and what has been delivered against those promises. Not the global benefits case. The specific commitments made to regional leadership about how this programme would work for them. Where those commitments have not been kept, say so and agree what happens next. That conversation, handled honestly, will do more for regional engagement than any communication campaign.

This is not a governance intervention. It is a promise intervention. And it is the work EA and TMO teams are best placed to do.

The broader point

A global programme that is succeeding in one region and struggling in others is not an unusual situation. It is the default outcome when a programme makes a global promise without translating it regionally, avoids the trade-offs that regional differences create, and loses the small agreements that regional credibility depends on.

The programme is not failing because delivery is hard. It is losing the business because the promise was never fully made.

EA and TMO exist to close that gap. Not by adding governance, but by making the right things visible to the right people at the right moment.

The question every EA and TMO team should be asking of every programme in their portfolio is this: where is the gap between what was promised and what the business is actually prepared to change, and have we named it yet?

That is the mandate worth claiming.