
Localized Enablement
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 Scaling a Transformation Practice in a Decentralized Organization
Transformation leaders in federated, multi-country organizations described the same bind: business units run like standalone companies, nobody agrees on what "transformation" means, and the central team is a handful of people serving tens of thousands of employees. Teams of two to five were common, supporting 3,000 to 20,000+ staff. Headcount alone was not the fix, because the organizations were already saturated with change.
The practices that scaled were the ones that moved ownership out of the central team: a shared definition of transformation, disciplined intake and prioritization, trained practitioners embedded in the business, and data that showed leaders what change overload was costing them.
Why Decentralization Makes Transformation Harder
Agreement in the room, reversal outside it. Leaders in federated models often nod along to central priorities, then tell their teams they do not have to comply. Open refusal is easier to manage than pretend alignment.
Hidden agendas. Business-unit leaders are accountable for their own revenue, so psychological safety is thin and priorities collide.
No shared definition. Every function, and sometimes the CEO, holds a different view of what transformation or change management means. One leader believed every manager already knew how to do it, which is how a "transformation enablement" title came to exist.
Reorganization churn. New teams and new leaders arrive mid-program, so nobody is sure who owns what.
The Resourcing Reality
Ratios are misleading. A team of three serving 3,000 people struggled as much as a team of two serving 10,000, because the real constraint is how much change the organization is already absorbing.
Both obvious fixes fell short. Upskilling project managers as extensions of the team failed because they had no spare time. Borrowing process engineers and architects failed for the same reason.
Tenure is a hidden limit. Long-tenured staff with fixed views are being asked to think differently and lead change. Several leaders want fresh talent but cannot get the approval.
What Worked: Getting Resources and Ownership
Position as revenue-enabling. Align priorities to revenue so the function is read as a growth lever, not an overhead cost. This matters most under a finance-minded CEO.
Intake and prioritization. Review incoming projects and decline or defer some. Leaders who lose resources escalate, which builds awareness of what change management takes.
Maturity baseline. Assess enterprise change maturity against a recognised model, then agree a gap roadmap with a sponsor. It adds work on top of delivery, and nobody may have asked for it.
Beg, borrow, steal, via the sponsor. Ask the sponsor to request people from leadership teams for specific critical projects. Resources will never be adequate, so borrowing is the realistic model.
Scale teams to the program. Hire or assign dedicated people for a defined program such as a 12-month integration, then redeploy or absorb them afterwards.
Building Practitioners and Communities
Invest in people who want it. Identify HR partners and project managers who want change leadership in their development plans, and certify them as practitioners.
Run communities and practices. Communities are people affected by change; practices are people who lead it. A shared repository holds tools and lessons learned, and post-mortems are shared with stakeholders.
Rotations. Let people from other areas work with the transformation team for a period, then return to their teams as local leaders.
Make people managers own it. Treat transformation as behavior change on an adoption ladder (recognize, try, repeat, sustain), with managers owning it rather than a central team pushing down.
Embed in the learning system. Convert training and cascade materials into the enterprise learning platform so they outlast the project team.
Winning Over Skeptical Business Leaders
Start with their pain. Show a leader that seven separate changes are landing on the same employees, or that hundreds of initiatives hit people at an average of five each. Then ask how they want to address it, instead of asking to take over.
Meet them where they are. Define what success looks like and the yardstick up front, say you do not have all the answers, and keep a nimble approach with some structure.
Three levels of disagreement. "I don't get it" is solved by explaining. "I don't like it" needs the objection surfaced. "I don't like you" needs a higher authority.
Prove it with a pilot. Split an initiative into a group using the methods and a control group without, and pick low-stakes groups. Choose the pilot where success is most likely, because being handed the hardest group is a common trap.
Use diagonal stakeholder mapping. Map supporters, neutrals and detractors from the grassroots up and the top down, and grow champions on both sides.
Tailor to the audience. Different demographics and roles perceive the same change differently, so the story has to be told differently for each.
Knowing When Leaders Can Go It Alone
Risk-tier the portfolio. One organization ran a short survey at annual planning (complexity, customer impact, revenue and cost, development effort). The highest-risk projects went to a dedicated change office. Lower-risk ones got a local change agent.
Keep a change backlog. Keep asking leaders for their problems, so the backlog shows how much change the organization needs against what is funded.
Expect to stay needed. Few leaders expect to work themselves out of a job, but all agreed the aim is to build capability in others.
If We Could Start Again
Reduce the number of simultaneous changes, because individual priorities multiply them.
Run simulations so people feel the future state, not only understand it.
Slow down to go fast: build capability bottom-up and top-down instead of absorbing every fire alone.
Write a jargon-free one-liner for what the program is and why it matters, and revisit it as the program ages.
Key Takeaways
Agree a working definition of transformation before agreeing a plan.
Treat resourcing as a prioritization problem: intake, defer, and align to revenue.
Do not count on central headcount; train and certify practitioners in the business.
Make people managers the owners of change, with the central team as coach.
Open with data on change overload, not with a request to take over.
Use a low-stakes pilot with a control group to prove value quickly.
Risk-tier projects so the central team focuses on the ones that must go right.
Put training and lessons into permanent systems so they outlast the team.



