Ask the executive sponsor of a struggling transformation what has gone missing and the answer is rarely budget. It is visibility. A multinational logistics organization reached exactly that point with a critical enterprise program, and program recovery governance became the means of restoring a view its leaders could act on.
Plenty of Activity, Very Little Sight
The program had many workstreams, capable teams, and visible sponsorship from the top, and on paper it looked healthy. Yet the executives who owned the outcome could not say what was on track, what was blocked, or which decisions were waiting for them.
My part was program recovery lead and senior transformation advisor. Nobody asked me to bring a new methodology. The leaders wanted control of something that mattered, and they wanted someone to describe the situation to them plainly.
Anyone who has held that seat knows how disorienting it is: accountable for an outcome, surrounded by motion, and unable to answer a simple question about where to step in. I treated that question as the real brief.
Why Another Layer of Reporting Would Not Have Helped
Too many workstreams were moving at once. Priorities conflicted across functions. Problems traveled sideways through informal channels instead of reaching people who could settle them, and executive meetings carried a great deal of status and very few decisions.
Those were surface features. Underneath, the program lacked a dependable path from information to decision. Reports described activity rather than exposure, and dependencies between workstreams lived in people’s heads. No one could say with confidence who was entitled to resolve a clash between two legitimate priorities, so clashes stayed open and each team quietly tuned its own piece.
Information was never scarce here. What was missing was information shaped for a decision and delivered to someone with the authority to act on it.
That redefined the assignment. The program needed governance built for recovery: structures that made reality visible and made decisions possible.
Program Recovery Governance in Five Moves
I kept the intervention small and deliberately ordered. Every move asked something of the client’s leaders, and I named the cost aloud rather than absorbing it silently.
Bringing the dependencies onto one page
I ran working sessions with the people nearest the work and mapped how the workstreams leaned on one another. The target was a shared picture of where one team’s delay turned into another team’s blocker, not a flawless plan. Candor was the price, since dependency maps expose gaps, so I introduced the exercise as protection against surprises and not as an audit.
Settling who decides
For each recurring type of conflict we named a single accountable decision-maker, listed who had to be consulted, and defined when a decision counted as final. Some early conversations slowed because certain people had to relinquish informal influence. After that, things moved faster.
Reserving forum time for decisions
Executive forums had been doing two jobs poorly. Status went into a short, consistent format that could be read without a meeting. The time that freed up went to a brief agenda of real choices, each framed with options, consequences, and a recommendation. An item that was not a decision did not take airtime.
Ranking priorities and defining escalation
We spelled out what qualified for escalation, who received it, and what response to expect. Alongside that, I pressed executives to rank competing initiatives against the outcome the transformation existed to deliver. Those conversations are seldom comfortable, yet they replace silent compromise with explicit choice.
Leaving a cadence that runs without me
We closed by setting a rhythm of working-level coordination, decision forums, and executive review, each with a clear purpose. I resisted anything elaborate. A process that works only while an outside advisor sits in the room is dependence, not governance.
Looking back, the order of the moves mattered as much as the moves themselves. Visibility had to come before decision rights, because nobody can agree who decides about something they cannot yet describe. Decision rights had to come before the forum redesign, because a forum with no authority to settle anything simply relocates the delay. Each step prepared the ground for the next, which is why I resisted the temptation to start with the most visible change.
How the Executives’ Position Shifted
Executives could now see where the program was exposed and which decisions were waiting on them. Decisions that had lingered got made, and by the right people. Escalations arrived earlier and better framed. With priorities ranked and communicated, teams had less reason to optimize locally, and conversations between functions became more direct.
Problems remained, as they do in any recovery. The gain that mattered was the organization’s capacity to spot trouble early and decide on it, which is what executive control amounts to.
Executive forums changed in tone as well, moving from performance review toward resolution. That is a healthier use of senior attention and a sign the governance was reducing noise instead of adding to it.
Takeaways for Other Recovery Efforts
- Sight comes first. Leaders cannot govern what they cannot see, and nobody sees what no one is willing to name.
- Decision rights are designed, not inherited. Where authority is ambiguous, delay becomes the default.
- Status and decisions need separate homes. Reports inform and forums decide, and blending the two weakens both.
- Governance has to outlast the advisor. If the cadence cannot run without me, the job is unfinished.
None of this depends on logistics or on a particular technology. Complex change outruns its guiding structures in every sector, and AI adoption makes that more likely as it spreads into daily operations. That territory is the focus of my enterprise AI consulting and leadership practice, and my approach to leading enterprise transformation sets out the principles I bring to executive teams.
Finding the Way Back
A critical program that is harder to read and slower to decide than it should be tends to need clarity ahead of extra effort. Start a conversation about your own transformation