Transformation diagnostics for programmes that have stalled.
Diagnostic work on why transformation has not delivered, and what needs to change for it to recover.
What this means
Most transformation programmes fail quietly. The RAG status stays amber, the workstreams stay active, and the board updates develop a vocabulary of managed expectation. The stall is not visible in the programme data because the failure is usually in the design, not the delivery: the programme was built on a theory of change that was never genuinely tested, or it has the right theory and the wrong governance, or the people dimension was treated as a communications problem rather than a structural one. Transformation diagnostics is the work of making that failure visible, naming it precisely, and determining what it will take to recover.
When this work shows up
A transformation programme is hitting its milestones but the business outcome is not materialising. The RAG status stays amber, the workstreams are active, and nothing is visibly failing, yet the change the programme was commissioned to deliver is not happening.
A sponsor or board has lost confidence in the programme leadership team and needs an independent read of what the actual state of the programme is, separate from the programme's own reporting.
A PE firm or investor has a portfolio company running a transformation that is consuming significant management time and capital and needs an assessment of whether the programme is recoverable or whether the investment should be redirected.
The programme has a change management or people workstream that is lagging significantly behind the technical or operational workstreams, and the sponsor needs to understand whether the lag is a pacing problem or a design problem.
A new CEO or incoming leadership team has inherited a programme that was commissioned by the previous leadership and needs a fast, independent assessment of what the programme is actually trying to do and whether it should continue in its current form.
How we approach it
Change theory assessment
Most stalled programmes have a problem in the theory of change before they have a problem in execution. The logic model underneath the programme, the sequence of assumptions connecting the intervention to the intended outcome, was typically never made explicit. It was embedded in the objectives and the workplan, assembled in pre-programme workshops where the people in the room had already agreed the answer. The change theory assessment takes that implicit logic and tests it against the delivery evidence, asking not whether the programme has been well run but whether it was designed to solve the right problem, with the right assumptions about what the organisation would need to do differently and whether it could.
Governance and sponsorship review
Governance and sponsorship is the most consistent failure mode in stalled programmes, and the one most likely to be invisible in standard programme reporting. The programme sponsor on the governance chart is rarely the programme sponsor in practice. Authority to make the structural decisions the programme requires often sits with people outside the programme governance structure, or with people whose bandwidth is consumed by operational priorities. The review tests specifically whether the formal sponsor has the organisational capital and the time to make the decisions the programme needs, whether there is a clear escalation path to genuine decision-making power, and whether the programme has been scoped to the level of change the business outcome requires rather than the level the organisation is currently willing to absorb.
Delivery architecture and programme design
Stalled programmes are rarely under-resourced in headcount terms. The delivery team is typically large, the governance calendar is full, and the workstream leads are experienced programme managers. The gap is usually in the specific domain expertise required to deliver the two or three hardest workstreams, present nowhere in the team but invisible inside a structure that looks adequately staffed from the outside. The delivery architecture review examines the workstream design and interdependencies, the quality and experience of the programme leadership, and whether the programme has the right capability in the right places, not just adequate coverage across the workstreams.
People and organisational change capability
The people dimension is the most consistently underweighted component of transformation programme design. Every programme has a communications plan and a training schedule. Almost none has a serious assessment of the behaviour change the programme requires at each level of the organisation, a structured plan for the people decisions the transformation demands, or an honest read on whether the leadership population the programme is delivering into has the capacity to sustain the new model once the delivery team leaves. Sustaining a change is a different capability from implementing one, and the conditions required for each are different. The review examines whether both sets of conditions are present, not just the implementation ones.
From the casebook
Fourteen months in and the programme had stopped delivering
A business services organisation came to us fourteen months into a transformation programme that had good structural bones but had largely stopped moving. The steering committee was receiving regular progress reports filled with activity updates and workstream summaries, yet the business outcomes the programme existed to deliver were not materialising. The CEO had begun to suspect the issue lay somewhere in how the programme was being run rather than in what it was trying to do.
The diagnostic found a governance problem at the workstream level. Leads had been given accountability for delivery but not the decision rights to accompany it. Every material call that touched more than one function was escalating to the steering committee, which met fortnightly and had neither the time nor the appetite to work through operational detail at that volume. The programme was running on consensus-seeking rather than on clear authority, and the gap between the two was generating the delays.
The engagement rebuilt the governance framework around explicit decision rights: documenting what each workstream lead could resolve independently, what required steering committee sign-off, and what could be safely delegated further. The steering committee agenda was restructured to separate strategic direction from operational blockages, so the programme could maintain pace between meetings without waiting a fortnight every time a cross-functional call needed to be made.
Delivery pace recovered within two months. The steering committee meetings shortened considerably as the volume of operational escalation fell away, and the programme completed the following quarter within its original budget parameters.
Related advisory work
Advisory
Advisory overview
The full scope of the advisory practice and how engagements are structured.
Advisory
Operating model design
Diagnostic and design work for organisations where the operating architecture has stopped fitting the business.
Advisory
Post-acquisition integration
Integration planning and delivery for bolt-ons, carve-outs, and merger situations.
Who we work with
Private equity
Operating model and people advisory for PE firms and portfolio companies across the hold period.
The practice is led by Sam Bramhall.
Sam Bramhall is the Principal Consultant at Esbee, with two decades of board-level strategic HR and organisational advisory across telecoms, fintech, professional services, technology, and PE-backed businesses. Engagements are principal-led: you work directly with Sam throughout, not with a junior team managing upward.
About Sam and the firm →Frequently asked questions
- What does a transformation diagnostic actually produce?
- The diagnostic produces a written framing of why the programme has not delivered what it was designed to deliver. Rather than a lessons-learned document or a post-mortem, it is a structured analysis of the specific gaps between programme design and execution reality: where the programme theory of change was wrong, where the delivery architecture was wrong, where the sponsorship and decision-making structure failed, and where the people and capability dimension was underestimated or absent from the design. The output is structured to be actionable, telling the sponsor what needs to change for the programme to recover, not just what went wrong.
- How is this different from a programme assurance review?
- Programme assurance reviews are designed to assess whether a programme is being run to the right standards of project management: governance, reporting, risk management, stakeholder engagement. They operate within the logic of the programme as designed. The transformation diagnostic is a different exercise: it interrogates whether the programme theory of change was correct in the first place, whether the structural and capability conditions required for delivery are present, and what the actual blockers are regardless of whether they appear in the programme risk register. The approach is adversarial rather than assurance-led.
- What does 'programme that has stalled' mean in practice?
- A programme has stalled when the delivery metrics suggest forward motion but the business outcome is not materialising. This is more common than outright programme failure. The reporting looks reasonable: milestones are hit, workstreams are active, the RAG status is amber not red. Yet the behaviour the programme was designed to change is not changing, the capabilities it was designed to build are not being built, or the structural changes it was designed to deliver are being absorbed and reversed by the organisation. The stall is usually evident to the sponsor before it is visible in the programme data.
- How does the diagnostic handle programme governance and sponsorship?
- Most stalled programmes have a governance and sponsorship problem at their core. The diagnostic specifically examines the decision-making architecture of the programme: where authority actually sits, whether the sponsor is genuinely empowered to make the programme decisions required, whether there is a single accountable owner at the right level, and whether the programme has access to the business capabilities it needs to deliver. In practice, this often means examining where the programme sits relative to operational priorities, whether the right people are spending the right amount of time on it, and whether the escalation path from the delivery team to decision-making authority is clear and functional.
- Can the diagnostic be run while the programme is still live?
- Yes, and this is the most common situation. The diagnostic is designed to be run without stopping the programme. The engagement is structured so that the diagnostic work runs in parallel with programme delivery, and the output is presented as a forward-looking intervention plan rather than a retrospective. The programme team is typically aware that the diagnostic is happening, though the framing with them is that it is support for the programme rather than an evaluation, which matters for access and candour during the interview phase.
- Do you provide support through programme recovery, not just the diagnostic?
- Yes. Many diagnostic engagements lead to a programme recovery phase, where the advisory practice provides hands-on support to the sponsor and programme leadership during the intervention. This might involve redesigning the delivery architecture, replacing or supplementing the programme leadership, or providing the people and organisational change expertise the programme was missing. The recovery support is scoped separately from the diagnostic once the diagnostic output has been agreed, so the sponsor has a clear view of what the diagnostic has identified before committing to the recovery engagement.
Last reviewed: May 2026