
Change Communication
About this brief
What is the ECLC? The Executive Council for Leading Change (ECLC) is a global, peer-led community of more than 1,200 enterprise transformation leaders. Members meet in regular virtual roundtables of around 45 executives, held under Chatham House rules, to share what is working, what is not, and how they are handling change.
How Tigerhall fits. ECLC is convened by Tigerhall, the transformation delivery platform for a world of always-on change. Tigerhall turns a company’s strategy into personalized change journeys for each employee, delivered in the flow of work (Teams, Slack, Outlook, mobile) in 33 languages, with real-time data on where the change is landing and where it is stalling. Leaders own the strategy and the plan; Tigerhall runs the delivery, so a team of two or three can deliver what used to take fifteen to twenty.
What is an executive brief? An ECLC executive brief is a short, anonymised write-up of a single roundtable. It captures what the room discussed, where leaders agreed and differed, and what to do next. Each opens with a summary, then themed sections, then eight key takeaways.
Executive Summary for It’s Never Too Late: Turning Around a Transformation
Transformations rarely run to plan. Using a simple three-phase model (prepare, manage, sustain) as the frame, participants marked up where programs typically derail and what has actually pulled them back. The pattern was consistent: the early mistakes are about context and coalitions, the middle mistakes are about communication and capacity, and the late mistakes are about reinforcement and ownership. Almost all of them are recoverable with honest acknowledgment, quantified goals and the right people brought in.
Turnarounds are not magic. They come from naming the friction, using data to reset the conversation, and building reinforcement in so change survives the leader’s next priority.
Phase Zero: When the Change Started Without You
Rumors run ahead of the plan. Announcements, policies or tool bans can land before the change team has a seat at the table. A curt “stop doing X until we announce a policy” leaves people guessing.
Use an existing moment. One fix was having the CEO send a short note pointing to an already-scheduled all-hands where the executive team would explain the strategy. It reinforced the original message rather than undercutting it, and it bought time without a new event.
Make the CFO a friend early. Finance is often the first to ask what the change will return, and the first to help fund the reinforcement later.
Baseline before ambition. A common derailer is no baseline, so nobody knows where the starting point is. Readiness assessments across people, process and technology fix this fast.
Prepare: Defining Success and Building Coalitions
Silos and polite nodding. Functions work in isolation and meetings end in agreement that evaporates in the hallway.
The inclusion gap. One analyst study found about three-quarters of leaders believe they have talked to employees about the change, while well under half of employees feel included in the planning.
“Why do we need change management at all?” The best counter is quantification. Ask leaders what they want to see when the switch is flipped (more invoices processed per day, a target accuracy rate) and the work stops looking soft.
Re-educate when the decision predates you. When a system was chosen before the change lead arrived, talk to leaders and end users early about why, and keep asking who else should be in the conversation. Late-comers keep appearing well into the project.
Slow down to speed up. The desire for speed is constant. Skipping prioritization and use-case clarity costs more later.
Duplicate efforts in matrix organizations. Regional teams can solve the same problem in parallel without knowing it. Early cross-functional coordination prevents the waste.
Bring communications in at the start. Communications is distinct from change management, and inviting it only for the board update or the year-end celebration is too late.
Manage: Communication, Capacity and Listening
Too little and too much. Silence lets people write their own story. A long-lead announcement with months of internal quiet is a classic case. Over-communication from an excited sponsor creates fatigue. The fix is a few crisp reasons, a clear cadence (“here is where we will be in 90 days, and in six months”) and translation into what it means for each role.
Managers are the carriers. How the change actually lands in someone’s day depends on their manager, so equip them first.
Different personas, different depth. Cascading one blanket update to everyone misses who needs more detail and who needs to hear about a changed login or workflow.
Feedback loops with honest answers. Pulse surveys and listening tours help, but only if you say what will be addressed now, what comes in a later phase and what is out of scope, and why.
Language gaps. Business and technology teams can speak the same language and still hear different things. A clear stakeholder engagement plan early helps.
Unmanaged change creates chaos. When nobody is looking after the next phase, teams go and push their own projects forward.
Multiple changes at once. The old linear model, with a big go-live and a stabilization period, is gone. Change is constant and exhausting, so structure still helps, but a more human-centered, empathetic approach matters more now, especially with AI. The work is moving from science toward art.
Sustain: Reinforcement and Ownership
Leaders move on to the next shiny thing. And frontline turnover can reach 20 to 50 percent during a long rollout, so many people were not there at the start and do not experience it as a change at all.
A sobering stat. More than half of transformations lose their financial value, partly because the post-implementation phase is under-invested. Recognition programs and success stories are not nice-to-haves.
Make business leaders report on benefits. One global transformation office handed designs to business leaders, who then reported monthly to an executive council on rollout and benefits realization. It became part of their performance, and follow-ups continued two years on.
Train the trainers on behaviors first. Product owners were asked to define the behavior they wanted to see before assigning any metric to learning. “They attended” was not an answer. Several later applied the same approach with external clients.
Build reinforcement into the technology. Validation rules that stop poor-quality data being passed downstream make the right behavior the default and take pressure off willpower.
Skills, permissions and incentives. Performance depends on what people know how to do, are allowed to do and are rewarded for. Training and communications cover only the first.
Tie it to evaluation and bonuses. Unsurprisingly, commitment rises when outcomes are linked to review and pay.
Credibility compounds. If past changes did not stick, people will not invest in the next one. Revisit projects from one, five and ten years ago and show what endured.
Leaders cannot delegate it. Change management is a leadership skill, not something handed to a change team. The sustain phase is the hardest and most important, and productivity dips need to be planned for.
Three Closing Thoughts
Expect friction and acknowledge it. Hiding obstacles invites overcorrections that cause bigger problems later.
Solve for the longer-term outcome. Avoid the short-term patch.
You are not alone. Peers and internal cross-functional partners have seen it before. Hold outcomes tightly and tactics lightly.
Key Takeaways
Reset with a quantified vision. Define what success looks like in numbers leaders care about, and baseline where you are today.
Use the moments you already have. An existing all-hands or leadership forum can correct a rumor faster than a new campaign.
Build the coalition early. Include communications, HR business partners, people managers and finance from the start, not at the celebration.
Calibrate communication. Aim for a few clear reasons, a visible cadence and role-specific detail, delivered through managers.
Close the loop on feedback. Say what you will fix, what comes later and what is out of scope.
Plan for capacity and fatigue. Treat multiple concurrent changes as a portfolio, and lead with empathy.
Engineer reinforcement. Combine system controls, policies, incentives and executive reporting so the change does not depend on goodwill.
Keep leaders accountable to the end. Tie benefits realization to performance, and keep checking in long after go-live.



