Why A Case For Change Is Not Enough If Managers Cannot Translate It
- Andrew Pigott
- Jul 3
- 5 min read
Updated: 5 days ago
A large NHS trust is redesigning its outpatient access model. The strategic rationale is clear: demand is rising, waiting times are too long, services are fragmented and the existing model is financially difficult to sustain. The programme director presents the case well. The logic holds. The chief executive's backing is visible.
Managers leave with a slide deck, an FAQ and a communications timeline. They are asked to brief their teams confidently, keep the message consistent and answer questions as they arise.
Then the team meetings happen.
Staff are rarely asking only why the organisation is changing. They are asking what it means for Monday morning. Which activity migrates first? Which vacancies get filled under the current model and which under the new one? If a patient safety concern arises during the transition, who holds the decision? What can this team adapt locally, and what has already been decided centrally?
The manager can explain the strategic logic. They cannot yet explain the operational consequences.
Managers can find themselves pulled toward three familiar responses. They repeat the strategic story and hope the detail follows. They reassure their teams more confidently than the evidence allows, which creates a credibility problem once the uncertainty becomes visible. Or they signal, subtly, that this is a corporate decision rather than one they personally own, which creates distance rather than momentum.
None of these makes the change locally credible. Staff leave the meeting understanding why the organisation is changing. They do not yet know what to do differently.
The tempting diagnosis
When this pattern appears, the instinct is usually to look at communication. Managers need better preparation. A clearer FAQ. Another briefing webinar. More consistent key messages.
These responses are not wrong, exactly. Better preparation does help. But they tend to address the symptom rather than the source.
The problem is often not primarily one of communication skill. It is that managers have been asked to translate a strategic story before the local implications of that story have been worked out. They have received information. They have not yet been equipped to make meaning.
Managers are often asked to carry certainty downward while still carrying uncertainty themselves. Managers often become the point at which unresolved organisational ambiguity is expected to be made workable. When that gap is not acknowledged, the ask becomes difficult to fulfil honestly.
Managers as translators, not channels
Research on organisational change consistently treats managers as active interpreters rather than neutral communication channels. They connect strategic direction to local work, test it against operational reality and influence what teams understand the change to mean.
National Audit Office reviews of integrated care systems and NHS financial sustainability show why this matters in practice. The strategic purpose of reform may be clearly articulated while local organisations are still working through workforce pressures, financial constraints, existing service commitments and the practical consequences of new operating models. The direction can be coherent at the centre while the local translation task remains unfinished.
A manager working inside that gap may be dealing with more than a communication problem. A manager who cannot answer the practical questions may not simply be under-briefed. They may also be under-authorised.
A briefing can transfer information. It cannot create local meaning.
Four practical moves
These are not communication fixes. They are design moves for organisations that want managers to translate change rather than merely repeat it.
Give managers a sensemaking session, not just a briefing
Before asking managers to brief their teams, run a working session in which they can test the case against their own area. What will your team ask first? What does this change mean in practice for the work you manage? Where does the strategic rationale create a local contradiction? What can you answer now, and what needs to go back to the programme?
Do not give managers only the polished narrative. Give them an honest account of what has not yet been worked out.
This session is not another broadcast. Its purpose is to surface what managers need before they can speak honestly, and to return unresolved questions to the people who can answer them. For that to work, there must be a named channel back into programme decisions, a clear owner, and a visible response. Without that, a sensemaking session risks becoming a place where ambiguity is discussed but nothing is resolved.
Separate the enterprise story from the local translation task
Managers benefit from organising the change material clearly before speaking to their teams. A simple working structure helps:
Decided: what has been confirmed and will not change
Open: what remains genuinely unresolved at programme level
Local: what managers and teams can adapt or work out themselves
Escalate: what requires a programme or executive decision before managers can answer
This prevents organisations from confusing a coherent strategic rationale with a complete local operating model, and it gives managers an honest framework rather than a script that becomes brittle the first time someone asks a real question.
Clarify authority before asking for ownership
Managers cannot credibly own a change if they have no authority to respond when local reality creates a problem. Before team conversations begin, be specific: what can managers decide independently, what can they adapt, what must stay standard, and what must be escalated and to whom?
Vague language about empowerment is not sufficient. Authority should be specific. Ownership without authority quickly becomes performative.
Treat recurring questions as design data
When the same questions keep appearing across teams and managers, the first instinct is often to add more communication. But recurring questions are not always a sign that people have not heard the message. They may be a sign that the change is not yet sufficiently worked through.
It is worth distinguishing between questions that need a clearer explanation, questions that reveal missing information, questions that expose an unresolved design decision, and questions that identify a genuine conflict between strategic intent and operational reality. Answering every recurring question by adding another FAQ may close the symptom while leaving the cause untouched.
The equipping gap
The gap that most often weakens the case for change at the local level is not between the strategic vision and the team. It is between the briefing and the equipping.
Briefing managers tells them what the organisation intends. Equipping them means helping them work through what has been decided, what remains open, what it means locally and what authority they hold when reality does not match the plan.
When that work is not done, the change that reaches teams is shaped by whatever meaning each manager has been able to construct from an incomplete brief.
Managers do not need every answer before they can lead a change conversation. They do need enough meaning, authority and honesty to make the conversation credible.
At Common Path Connection, we help organisations move beyond briefing managers and equip them to make change meaningful in real work.
Our Change & Adoption support helps leaders clarify what has been decided, what remains open and what managers need to lead honest local conversations.
Our Change Adoption Sprint is designed for organisations that need to close the gap between strategic intent and local understanding.
Related reading
A strong case for change still has to be translated into local work. These insights look at what happens when adoption, drift and decision-making are not designed carefully enough:
Change Adoption: Why the New Way Feels Harder — why the new way must work under real operating pressure.
When Change Looks Like It Has Landed: How to Spot Adoption Drift Early — how adoption can weaken after launch.
Why Decisions Escalate When Uncertainty Has Nowhere to Go — why unresolved local uncertainty often moves upward.
Comments