
Change Activation
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 The Hidden Failure Point in Transformation: Post-Implementation Sustainability
Many programs are declared successful because delivery milestones were met, yet the business case is won or lost in the months after go-live. Participants agreed that the hidden failure point is rarely the quality of execution. It is the gap between project completion and operational ownership: adoption slips, KPIs drift, governance fades and the project team has already moved on.
A transformation is only complete when the business can run, govern, measure and improve it without the program team. Sustainability has to be designed in from day one, with the business involved early, benefits defined up front, and post-go-live work treated as its own funded phase.
When Momentum Starts to Fade
Before the project begins. Programs measured on time and budget can still fail to deliver the benefit. If there is no defined benefit tied to strategy, do not do it. Survival projects (obsolete systems, new regulation) are the exception, and the aim there is to retain position.
Late engagement. If the people most affected are not involved from the start, a shared vision is missing, and urgency becomes panic. Late is better than never, but alignment at the end is too late.
Investment shifts to the next initiative. When investment in the next program exceeds investment in sustaining the current one, people drop the new behaviors. Count coaching, time, support and visibility, not just money.
Change as loss. To some people, change is like the death of the old, and they go through grief non-linearly. Skipping that care breeds resistance.
Signs a Transformation Has Not Been Operationalized
Workarounds and legacy habits return.
KPIs are not measured or reported, and data quality slips.
Heavy dependence on the program office, and structures crack when it winds down.
Governance was designed for the project, not for run state.
Awareness without adoption. People participate but do not embrace.
No link to the big why. Without a clear problem statement, a large project is mistaken for a transformation, and scope sprawls.
Fatigue at the end. Teams are charged up at the beginning and exhausted by go-live.
Ownership Transition and Governance
A handoff is not a calendar event. It is a capability and accountability transfer, ideally a warm one with a post-implementation phase built into the plan until sustainability is proven.
Support, not takeover. The operating unit owns the journey. The transformation office enables with skills and methodology. Where trust was low, rebuilding it took many months.
Operations in from the start. Involve business owners in decisions, narrowing options together, and in blueprints, metrics and training. They should help write the recipe, not be served a meal.
Sponsorship outside the program. The sponsor should sit outside the transformation team, with authority to step in when push comes to shove.
A practical handoff kit. (1) A public escalation tree for anticipated problem types (adoption, technical, customer). (2) Processes and SOPs on a well-kept intranet rather than buried in email. (3) Tracking and reporting the business can check itself, with continued sponsor review. The minute people stop looking at the number, the change becomes optional.
Clear the path, not carry the load. A small team cannot transform a large company, but it can clear the way and get everyone involved in owning it.
Do not stop at two months. Post-go-live rigor often lasts only a month or two, but the hard part is sustaining change for a year or more.
Measuring Sustained Success and Avoiding KPI Drift
Measure transformation, not deployment. Training completion and go-live are milestones, not results.
Qualitative and quantitative together. Both are needed to show behaviors changed, and not everything ties neatly to revenue.
Set business success measures before anything starts. Use a one-to-two-year objective plus quarterly ones. Expect to refine KPIs as the project evolves, and calibrate with the business before go-live.
Ask the 12-to-24-month question. Is the business operating better than before? Look at adoption, compliance, cost and working capital, and whether change is embraced at lower levels as well as the top.
Track ROI over time. Benefits compound after launch and need long-term review by senior executives.
Give sustainability its own timeline. Some leaders frame it as transition, so the sustainability phase has its own measures and milestones.
The Executive Role: Stability Versus Agility
Stage the rollout. Go live with a deliberate tuning window (a short, announced period to listen and adjust), then close it and move to a stable standard to avoid change fatigue.
Communicate early, loud and continuously. Explain why before launch, in every channel, and keep going.
Sponsors as coaches. They motivate, incentivize, decide and pivot, and their presence alone shapes accountability.
Own the benefits. Benefits are not a glide path. They need executives to take out cost, redirect capacity and redefine roles, with an explicit accountability plan.
Protect critical behaviors. Identify the few behaviors that make the change stick, and protect them through performance management, rewards and leadership attention when the next change arrives.
Accountability levers. Use goals, budgets and incentives. One example reduced a sponsorโs budget by the promised savings. Another tied a compliance-quality target to a leaderโs goals and tightened it after it was met.
Process foundations. Role matrices, a process taxonomy, activity-level SOPs and a single controls platform keep standards consistent as speed rises.
Designing for Sustainability From Day One
A believer network. Recruit influential people regardless of title, and make them resources inside the teams you leave behind.
Middle managers as translators. They turn sponsor vision into something tangible, and build a support structure that outlives the project.
Build change capability. Comfort with change makes the next effort smoother.
Design the end state early. Operating model, ownership, governance and measurement should be defined before implementation is complete.
Key Takeaways
Define the business benefit and success measures before delivery starts.
Involve the operating business in decisions, design and planning from the beginning.
Treat handoff as a warm capability and accountability transfer, not a closing meeting.
Fund and staff a post-go-live phase with its own timeline and governance.
Measure adoption and business outcomes at 12 to 24 months, not just go-live.
Keep sponsors active as coaches and tie accountability to real levers.
Protect the critical behaviors and keep the numbers in front of leaders.
Build believer networks and middle-manager support so change capability endures.



