TRANSFORMATION AT SCALE AND SPEED - PART 5

Part 5

Sustain speed through structural empathy

The same team can appear on six transformation plans, with each programme assuming it has capacity for one.

At executive level, the plans look reasonable. Each has a sponsor, a business case and a delivery schedule. Each has been approved through the appropriate process.

For the people doing the work, those plans arrive together.

A new system. A revised structure. Different performance expectations. Additional learning. Requests to attend design workshops, test processes and support colleagues.

Customer commitments continue throughout.

This is where the ambition to transform can exceed the organisation’s ability to absorb the work. It is also where senior leaders must take responsibility for the combined consequences of decisions that looked manageable in isolation.

Throughout this series, I have argued that transformation should become a permanent leadership capability. We have examined ownership, workflow design and the skills needed to operate a new model.

The final question is how to sustain that capability.

An organisation cannot keep adapting successfully if every change leaves people with more work, less clarity and fewer resources for the next transition.

I use structural empathy to describe the discipline of designing workload, sequencing, decision-making and support around a realistic understanding of what people must absorb.

It becomes visible in the decisions leaders make about what starts, what stops and what the organisation can reasonably deliver.

Look at the portfolio from the employee’s perspective

A transformation portfolio is usually organised around initiatives. Employees experience it through changes to their working day.

That difference matters.

One programme may require a team to learn new technology. Another may change its reporting relationships. A third may introduce different targets. Each programme can have a credible change plan while their combined demands remain unexamined.

The executive team needs a view across those demands.

Which teams are affected? What must they do differently? How much time will implementation, learning and temporary workarounds require? Which specialists are needed by several initiatives? What else is happening in the operation during that period?

A useful assessment should include the effort of transition. Attending training is only one element. People may also need to practise, seek advice, correct early mistakes and help colleagues who are encountering the same problems.

Managers face their own additional demands. They must interpret changing expectations, answer questions, monitor performance and resolve uncertainty while continuing to run the operation.

A portfolio that overlooks this work is underestimating the resources it needs.

Treat capacity as a constraint that can be managed

Leaders routinely assess whether an investment has sufficient funding. We should apply comparable discipline to the capacity required to implement it.

Capacity includes available time, access to expertise and the attention needed to make sound decisions. It also depends on how predictable the surrounding work remains.

Consider the customer-onboarding team used throughout this series.

The organisation is introducing AI-supported document review. Employees need to learn how to investigate exceptions and challenge unreliable outputs. At the same time, the team is moving to a new reporting structure and preparing for a seasonal increase in applications.

The investment may still be worthwhile. But its delivery plan must reflect those conditions.

Leaders could begin with a smaller group, defer an unrelated change, provide temporary operational support or move the rollout outside the peak period. Where deadlines cannot move, scope and resourcing may need to change.

These choices have costs. So does proceeding with assumptions that the organisation cannot meet.

The important requirement is to make the trade-off explicit and assign authority to resolve it. A programme team cannot manage enterprise capacity if it has no influence over competing commitments.

AI changes the workload as well as the output

AI can remove repetitive effort and help people find information more quickly. It can also create additional material to assess and more systems to supervise.

An employee may spend less time preparing an answer while spending more time checking its basis, resolving inconsistencies and deciding whether it can be trusted.

The effect on workload therefore depends on the design of the complete process.

BCG reports that, in a study of 1,488 full-time US workers, 14% of AI users described a form of mental fatigue associated with excessive AI use or oversight. This is a self-reported finding from a particular sample, rather than a measure of all workers or proof that AI causes burnout. It does provide a reason to examine the review burden created by deployment.

For leaders, the practical question is whether the new model reduces the demands on people or changes their form.

How many outputs must an employee review? How difficult are the exceptions? How often must they switch between systems? Can they obtain specialist help when needed?

These questions belong in the business case and the implementation review.

Estimated time savings should be tested against the actual work required after deployment. The organisation should also decide how any released capacity will be used. Some may support growth or better service. Some may be needed for learning and stabilisation before further gains are realistic.

Sequence change around dependencies and stability

People need enough stability to understand whether a new way of working is effective.

If the process, technology, team structure and performance measures all change simultaneously, it becomes harder to diagnose why results have improved or deteriorated. Employees may also be unsure which expectations remain valid.

Where possible, sequence changes so that teams can establish competence in one significant area while other arrangements remain dependable.

This is a design principle rather than a universal rule. Some changes must happen together. A new service may require a new system and new responsibilities from its first day.

In those circumstances, leaders should strengthen the transition arrangements. Provide clear escalation routes, accessible support and realistic expectations for early performance. Reduce competing demands where possible.

Explain what will remain consistent: the customer commitments, the standards that apply and the authority people have to act.

Perpetual transformation requires regular review. It does not require every team to be reorganised at every review.

Remove work as deliberately as you introduce it

One of the most practical contributions an executive can make is to authorise the removal of work.

A report that no longer informs a decision. A duplicate approval. A meeting whose purpose has disappeared. A legacy process retained after its replacement has proved reliable.

These activities often persist because stopping them requires a decision that nobody owns.

During transformation, their cost becomes more visible. Employees may be expected to maintain the old process while operating the new one, with no clear agreement about when the duplication will end.

Temporary parallel running can be necessary. It should have a defined purpose, an owner and conditions for closure.

For each major change, I would ask the leadership team to identify what will be retired, simplified or reduced. Include that work in the plan and review whether it happens.

Otherwise, the organisation can accumulate changes without gaining the capacity those changes were intended to release.

Make governance proportionate to the decision

Governance should help people act with confidence and obtain timely decisions when they reach the limits of their authority.

Its design should reflect the consequences of the decision.

A reversible change within an agreed boundary may be delegated to the team. A material change to customer outcomes or risk exposure may need independent review. An incident may require immediate attention rather than waiting for the next scheduled meeting.

The objective is to make those distinctions clear.

A fortnightly coordination discussion may be useful during implementation. A quarterly portfolio review may provide an opportunity to reassess investment and capacity. Neither should prevent an urgent decision when conditions change.

Leaders should also examine the reporting burden they create.

Can several programmes use the same evidence? Are teams repeatedly presenting information that decision-makers already have? Does each meeting resolve something that could not be resolved more simply?

The time spent satisfying governance requirements is part of the cost of transformation. It should earn its place through better decisions, clearer accountability or meaningful assurance.

Listen in a way that can change the plan

Employee feedback becomes useful when leaders are prepared to act on it.

A pulse survey may reveal uncertainty about responsibilities, difficulty finding support or a workload that feels unmanageable. Conversations with teams can explain what sits behind those responses.

The next step is to examine the operating conditions.

Are priorities conflicting? Has training been squeezed out by delivery targets? Are employees absorbing unresolved design problems through manual workarounds? Is a small group of experienced people carrying most of the transition?

Microsoft’s 2026 Work Trend Index found that organisational factors—including culture, manager support and talent practices—were more strongly associated with self-reported AI impact than individual factors alone. Its analysis does not establish causation, but it reinforces the value of examining the environment in which employees are expected to perform.

Feedback should lead to visible decisions. Leaders may narrow a rollout, provide additional support, clarify authority or stop a competing initiative.

Protect confidentiality and avoid using team feedback to label individuals as resistant or insufficiently resilient. Explain what has changed in response and what cannot change, with the reasons.

Asking people how they are coping while leaving every demand untouched weakens confidence in the process.

Measure performance and the capacity to sustain it

A delivery dashboard can show that milestones are on track while concealing the effort required to keep them there.

An initiative may depend on repeated overtime, cancelled learning or a few specialists resolving every difficult case. Those arrangements may support a short period of exceptional effort. They provide a weak basis for a permanent operating model.

I would review business outcomes alongside evidence about sustainability.

That could include customer service, quality, rework, unresolved exceptions, time to proficiency and the amount of support teams require. Workload feedback and the concentration of critical knowledge can help explain the operational results.

Use the indicators together.

Rising escalations may show that employees are identifying problems more effectively. Lower handling time may conceal correction work elsewhere. A team reporting confidence may still depend heavily on one expert.

Agree in advance what evidence would prompt intervention. If quality deteriorates and workload rises, who can narrow the rollout? If benefits depend on continuing exceptional support, what must change before expansion?

Measurement should inform the pace of delivery.

Make Amplify a decision about sustainable performance

The Amplify stage of transformation requires leaders to decide what deserves to grow and under what conditions.

A successful pilot is evidence to examine. It may have benefited from enthusiastic volunteers, experienced specialists or unusually close support.

Before expanding it, ask whether the outcome can be reproduced by other teams, at realistic volumes and with resources the organisation can sustain.

Capture what made the improvement work. Update guidance, learning materials and decision rules. Retire obsolete arrangements. Assign ownership for monitoring and continued development.

This is how one transformation strengthens the next.

The organisation retains more than a new system or process. It gains knowledge about how to implement change, recognise problems and adapt its approach.

It also needs room to absorb that learning. Completion should include a review of what has stabilised, what remains fragile and what support is still required.

The leadership responsibility across the whole series

The five parts of this series describe connected responsibilities.

Making transformation permanent requires leaders to understand which business assumptions are changing. Clear ownership gives the organisation a way to resolve the resulting trade-offs. Workflow design translates intent into a practical operating model. Capability development prepares people to perform the changed work.

Structural empathy keeps those commitments grounded in what the organisation can deliver and sustain.

Together, they give substance to the Anchor–Architect–Activate–Amplify loop. Leaders establish direction, design the conditions for delivery, support implementation and use evidence to decide what happens next.

That loop depends on the willingness to stop as well as start, to revise a plan when conditions change and to recognise that employee time and attention are finite resources.

At your next executive review, take one priority transformation and examine its full demands on the teams involved. Look beyond the programme plan to the operational work, learning and other changes those people must manage.

Then make one concrete decision that improves their ability to deliver.

The enduring test of transformation is whether it leaves the organisation better able to respond again. That includes the skills, judgement and confidence of the people who will carry the next change.

What will you stop, simplify or defer to create capacity for the transformation that matters most—and who will own that decision?

This concludes the five-part series Transformation at scale and speed.

Research informing this article includes BCG’s 2026 analysis of AI oversight and cognitive workload, and Microsoft’s 2026 Work Trend Index. Structural empathy, the proposed portfolio practices and the suggested measures are the author’s synthesis. The customer-onboarding example is illustrative.