
Organizational Restructures
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 Where Are You on the Transformation Journey?
Twenty-one transformation leaders were asked what a mature transformation office looks like, how far they are from it, and how to fund the journey. They gave 21 slightly different answers, but the common thread was clear: maturity is less about tooling or headcount than about position, scope and trust.
Mature offices sit close to the top of the business, are clear about what they will and will not do, measure performance rather than activity, and build capability across the organization instead of holding it themselves.
What โMatureโ Looks Like
A show of hands put three offices reporting directly to the CEO and four embedded in a function. Members described maturity in practical terms.
A seat at the table. Reporting into the C-suite as a peer, not buried under finance, HR or technology, where each function adds its own bias.
Partner of choice. Business leaders pull the office in because it helps deliver priority outcomes.
A capability, not a crisis response. Repeatable ways of turning strategy into outcomes, not a team called in at the eleventh hour.
Dedicated people and budget. Many offices borrow resources; people are harder to secure than dollars.
Early involvement. Part of strategy and design, not only implementation.
Leaders who come prepared. In mature organizations, leaders arrive with a baseline and a problem statement, not random requests.
A defined scope. Leaders can see what the office does and, just as importantly, does not do.
Change as culture. Readiness spreads across roles until the whole enterprise treats it as normal.
Looks Mature, But Isnโt
The group listed signs that create a false impression of maturity:
Slide decks and consulting spend. Volume of material says little about outcomes, and no template ever changed behavior on its own.
A rebranded PMO. Some leaders still see a transformation office as a more polished project office, focused on delivery rather than business value.
Dashboards that show activity, not performance. Without baselines and action, scorecards give comfort, not progress.
Uneven understanding at the top. Some executives engage fully on change; others ask for a deck and a communications plan.
The โintern groupโ problem. Anything nobody else wants lands on the office.
A practical fix was a published menu of service offerings that says plainly what the team does and does not do.
The PMO Question
The distinction between a project office and a transformation office came up repeatedly.
Inputs versus outcomes. A project office manages delivery; a transformation office is accountable for the value delivered.
Visibility. Project tracking is visible; transformation work is often invisible for months, which makes it harder to credit.
An activity-and-outcome cascade (these activities lead to these outcomes) helps leaders see why each step matters.
Joint structure upfront. Show leaders who owns the technical, people and governance work streams, and how they connect.
The trap of being good at both. One leader reported being valued for flawless project execution while struggling to be recognized for strategic transformation work.
Use rescue moments. When projects falter and leaders turn to the office, use that trust to explain the difference for the next one.
Where Offices Sit Today
Members were candid about what they are missing.
Structure. Some are early in the journey, with many consultants and a control-tower arrangement but no formal office.
Connected priorities. Different parts of the business march to different criteria, creating friction, for example between sales speed and delivery discipline.
Looking forward, not just back. In operator-led cultures, transformation is equated with incremental improvement; the harder work is reinventing the business while still reporting on it.
Standard work. A small team in a large organization is defining a standard approach to running programs, including the people side, so it can build capability elsewhere and eventually work itself out of a job.
Clear success factors. Goals such as standardize, simplify or digitize need a defined benefit and a trajectory.
Raising Maturity Across the Organization
Use a consistent management system. A common way of running the business gives everyone the same base to build change on.
Explain the why, several times, in several ways. At every level.
Segment demand. One leader sorts requests into enthusiastic, agnostic and resistant, starts with the enthusiasts, and shares results; agnostics warm up and resistors soften.
Introduce your role at every kickoff. Being present early builds recognition, even in meetings that produce no output.
Build a network. A standard change framework, a learning journey for managers and a monthly community of change leaders across functions and sites.
Ask leaders why they need a transformation office. Answers split between โan extension of the project officeโ and โsomeone to deliver adoption for us.โ Both need a conversation about shared effort.
Funding the Journey
Most members said the investment case is made piecemeal, and often with little success.
Prove return per resource. One approach was to set a target of three to four times the cost of each resource and show it, which opened the door to more people.
Expect ad hoc, iterative funding. A seven-figure request was approved at a small fraction of its size; it kept the team going until the next ask.
Ride on large initiatives. Raise needs while the project is being designed, when funds are being allocated and attention is high.
Beware the โtransientโ assumption. Some organizations expect the office to disappear after a program, so there is little appetite for lasting maturity.
The pendulum. Organizations swing between one temporary project team and โleaders should do it themselves,โ and the work can fall between the two.
Three Years On
Asked what would be different day to day, members described:
Routine change. Employees as well as leaders carrying change as second nature.
Proactive, data-led operation. AI-supported monitoring and alerts that cut the cycle time for proving value from months to weeks.
A change of mindset. Starting from the behaviors of the desired future, then working out what it takes to have them, instead of starting from tools.
Scaling with technology. Small teams using technology to scale people-side change when headcount will not grow.
Realism. Some expect little to change in cultures that stand up temporary offices every time.
Key Takeaways
Position decides influence. A C-suite peer position with an independent view beats being buried in a function.
Publish what you do and what you do not. A clear scope protects the team from being the default home for every task.
Measure performance, not activity. Baselines and action make dashboards worth having.
Differentiate from the project office. Frame the office around outcomes and value, and show the cascade from activity to result.
Be present at the start. Introduce your role at kickoff and build awareness early.
Start with the willing. Use early wins from enthusiastic areas to pull others along.
Build capability, not dependency. Frameworks, learning journeys and change networks extend a small teamโs reach.
Make the investment case on the back of big initiatives. Prove return per resource and ask when budgets are being decided.



