
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 Beneath the Known Problems: Reading the Signals โ and When Youโre the One Stuck
Two member-hosts asked a harder question than โwhere is the organization stuck?โ: what if the transformation leader is part of the system that is stuck? Drawing on leader interviews and a membership benchmarking survey, they invited the group to share signals, pivots and personal stories.
The strongest signal that you may be the one stuck is when the work feels too hard, and the best way out is to get close to stakeholders and understand why people do what they do before proposing anything new.
Signals the Hosts Brought
Interviews with business leaders, mostly in energy and chemicals, surfaced recurring tensions that look different from a business leaderโs chair.
Accountability versus fear. Leaders know the techniques but worry they create a culture of blame.
Fear of loss, not of change. People resist losing control, autonomy, relevance, identity or a job; a change seen as positive spreads quickly.
Trust and consistency. An aspirational data-driven narrative collapses when the organization reverts to across-the-board cost cuts.
Changes that go viral usually start with the person doing the work who wants to improve it.
Capability, not program. Several leaders invested in transformation as a lasting skill.
Treasuring the old. One leadership team deliberately looked for new value in legacy assets instead of framing them as the problem.
What the Benchmark Showed
A survey of a section of the membership earlier in the year, small but suggestive, found:
Higher-performing offices reported through the C-suite, held a permanent seat and had budgets matching their roadmaps.
They were small and nimble, partnering with the business rather than producing playbooks and training.
Having tools and a function was not enough. Presence alone did not correlate with performance.
Most initiatives only partly met expectations, and, with value described as murky, more than 80 percent fell into those two groups combined.
Two Stories of Being the Stuck One
The hosts each shared a moment when they realized they were part of the problem.
From observer to coach. A transformation leader four months into a program brought a long list of gaps against a framework to a senior executive. The response reframed the role: ask why colleagues do things the way they do. Peers were building habits within their own mental models, so the job became joining them there and using the framework as a reference, not enforcing it. The shift moved the office from being a police force to being a capability.
Anchored on an assumption. A small team set up to tackle long-standing business problems kept hitting walls while connecting data and systems. After weeks, the lead realized they had anchored on an early assumption of where the problem sat, creating a blind spot. Reframing the same data from a different anchor exposed other issues in the ecosystem.
The common image was a kaleidoscope: the same pieces, a different view after a small turn.
Signals Members Recognized
Too many problems at once. A leader who keeps surfacing issues, including customer-impacting ones, is told the priority is the strategic push; the lesson was to decide which big rocks go in first.
Boiling the ocean. Pulling one thread leads to a tangle. A simple decision tree on business and financial impact helps filter demand; quick wins are worth a detour when they support the larger mission.
Drift from stakeholders. The further you move from stakeholders, the more misaligned you become. Spend daily time where the work happens; the signals are in those conversations.
Falling in love with the plan. The hard part is taking those signals back and persuading the team to pivot. The plan is a starting point, and the middle will be messy.
Moving targets. Mid-course shifts from adjacent executives, and leaders living in the future while everyone else lives in the present, erode trust unless someone manages the narrative and tells people early.
How to Pivot
Treat โtoo hardโ as a signal. Pause and ask why, and where internal dynamics are getting in the way.
Notice your own reactions. One member caught a defensive reaction to a colleagueโs tool and asked whether pride in the original plan was the real issue.
Re-align leaders. When alignment at the start fades, bring misaligned stakeholders together and help them see each otherโs views.
Understand the why. Assume people are trying to do the right thing with the information they have, and learn their beliefs before suggesting a better way.
Translate and validate. A shared definition of high potential, blessed at the top, fell flat in a safety-critical plant, where agility could be read as risk. The fix was to unpack the concept by level instead of abandoning it.
Let the front line name it. A rollout stalled until the team dropped the programโs branding and simply adopted the practices under their own name.
The Experiment
The hosts proposed a short learning experiment for interested members: when the work feels too hard, ask how you might be stuck and how well you understand the why behind othersโ actions, then report back. Volunteers signed up during the session, and results will be shared at a future roundtable.
Key Takeaways
Ask whether you are part of the stuck system. Shift from observer to participant.
Read โtoo hardโ as a signal. It is a prompt to pause and examine internal dynamics.
Seek the why before the fix. Assume good intent and learn what people are trying to achieve.
Stay close to stakeholders. Daily conversations show the signals a plan cannot.
Hold the plan lightly. It is a starting point; pivot and communicate early when it changes.
Prioritize ruthlessly. Filter demand by business impact, and take quick wins that serve the larger goal.
Translate before you roll out. Validate definitions with stakeholders and adapt language to context.
Fear is about loss. Address what people stand to lose before pushing the change.



