MAKE TRANSFORMATION A PERMANENT LEADERSHIP CAPABILITY - PART 1

Part 1 of Transformation at scale and speed

A transformation programme can reach its final milestone while the organisation remains poorly equipped for the next disruption. The system is live. The new structure is in place. The programme has delivered against its agreed scope.

Yet when the next shock arrives, the organisation has to mobilise again. Leaders negotiate ownership. Teams assemble information that should already be available. Funding follows a lengthy approval process. People wait for decisions while customers and competitors move on.

We should ask what the transformation actually left behind. It may have delivered a valuable improvement. But did it also strengthen the organisation’s ability to recognise a change in its environment, decide what matters and respond effectively?

For senior leaders, that second question deserves much more attention. Our responsibility extends beyond delivering the changes already on the agenda. We must build an organisation capable of responding to changes we cannot yet describe.

That is what I mean by making transformation a permanent leadership capability.

The leadership challenge begins with our assumptions

Every organisation operates on assumptions. We make assumptions about what customers value, how demand will behave, where expertise will come from and how long it will take to deliver a product or service. Our structures, budgets and career paths give those assumptions a practical form.

A seismic event can invalidate several of them at once. A supply disruption can expose dependence on a single supplier. A shift in customer expectations can make an established service model uncompetitive. AI can change the cost and speed of work that previously justified entire processes. A shortage of critical skills can make an otherwise sound strategy difficult to execute.

The initial event may be outside our control. How quickly we recognise its implications, and how effectively we organise our response, are leadership responsibilities. This requires us to examine something uncomfortable: the operating model we are protecting may embody assumptions that no longer hold.

A process that once provided essential oversight may now add delay without improving the decision. A departmental boundary that once supported specialist expertise may now make it difficult to serve a customer across channels. An annual funding cycle may keep resources committed to a priority whose value has diminished.

These arrangements usually had a rationale. Leaders need to understand that rationale and recognise when it has expired. Perpetual transformation means developing the sustained ability to make those judgements and act on them.

It also requires restraint. If every development produces a new priority and every priority produces a reorganisation, the organisation loses the continuity it needs to perform. Leaders must distinguish between a signal worth monitoring, an opportunity worth testing and a change that requires a fundamental response.

Build the capacity to adapt into the management system

The research provides a useful foundation for this broader view.

The World Economic Forum and Accenture’s 2026 paper describes organisations moving towards AI embedded in core workflows and decision-making. Its emphasis includes operating-model redesign, human accountability, talent systems and disciplined experimentation. [1]

Marlina and colleagues’ review of 30 articles similarly connects organisational adaptation with leadership, culture, digital capabilities and governance. It also recognises that greater autonomy can weaken coordination when common standards and responsibilities are unclear. [2]

For executive teams, the implication is that these elements need to be considered together. An investment in technology creates demands on skills. A change in skills affects how work should be allocated. A new workflow changes the decisions people need to make. Those decisions require authority, information and accountability.

If each element moves through a separate planning process, the organisation can become internally inconsistent. We train people for responsibilities they have not been given. We delegate decisions without providing access to the necessary data. We introduce technology while retaining approvals designed for the previous process.

A permanent transformation capability should help the executive team identify and resolve these inconsistencies. It should influence how strategy is reviewed, how capital is allocated, how leaders are assessed and how people develop. It cannot depend entirely on the personal energy of a programme director or the temporary attention generated by a launch.

Start with the business consequence

When a significant disruption occurs, the first executive question should concern its effect on the business.

• What has changed about the value we provide, the economics of providing it or the capabilities required to deliver it?

That question gives the organisation a basis for prioritisation.

“Become AI-enabled” is too broad to guide difficult choices. Improving the speed and reliability of customer onboarding is more specific. It allows leaders to examine the customer experience, the cost of delivery, the quality of decisions and the work required across functions.

Consider an illustrative organisation whose customers are abandoning an application process because it takes too long. Sales wants a faster response. Operations wants complete information. Risk wants confidence that the necessary checks have been performed. Technology has been asked to introduce an AI tool that can read documents.

Each perspective is reasonable. But the tool addresses only part of the problem. Suppose document extraction becomes much faster, while applications still wait in a queue for someone authorised to resolve an exception. The customer experiences little improvement. The organisation may have accelerated one task while increasing the volume arriving at an existing bottleneck.

The executive team therefore needs to examine the whole journey. Where does work wait? Which information is requested repeatedly? Which decisions require specialist judgement? Who can resolve a case that crosses departmental boundaries? What would happen to quality if volumes increased?

These questions reveal the capabilities the business actually needs: reliable interpretation of information, timely risk assessment, effective exception handling and clear customer communication. A capability spans the people, processes, technology and authority needed to achieve an outcome. Looking at the business this way helps leaders see dependencies that an organisation chart does not show.

It also improves investment decisions. The next constraint may require better data, a different approval threshold or more experienced reviewers. Purchasing additional technology will not resolve every constraint.

Give continuous transformation a practical rhythm

I propose four connected disciplines: Anchor, Architect, Activate and Amplify.

Together, they provide a way to manage adaptation without turning every response into a separate enterprise-wide mobilisation.

1.  Anchor the change in an outcome that matters.

The executive team must be clear about what improvement it is seeking and why that improvement matters now.

For the onboarding example, faster completion might be the objective. But speed must be considered alongside accuracy, customer understanding and the consequences of poor decisions.

Establish the starting position. Identify the assumptions behind the proposed investment. Agree which capabilities need to improve and what evidence would justify a different course.

Anchoring also means setting limits. A team cannot make sound trade-offs if every desirable outcome has been declared equally urgent. Leaders need to decide where the organisation will concentrate its attention and what it will defer.

2.  Architect the conditions for delivery.

Once the outcome is clear, design how the work will happen.

This includes the workflow, access to information, decision rights, controls and the responsibilities of people and systems. Reporting lines may need to change, but they should follow an understanding of the work.

In the onboarding example, someone must own the end-to-end result. Teams need to know which cases can proceed within agreed rules and which require review. Employees need a workable route for challenging an AI output. The organisation needs a response when the technology is unavailable.

Architecture should make execution coherent. It should also make accountability understandable to the people expected to exercise it.

3.  Activate through supported changes in everyday work.

A new process only becomes an organisational capability when people can perform it reliably.

That requires more than communication and training attendance. Employees need opportunities to practise, managers need time to coach and the organisation needs to assess whether people can handle the situations they will encounter.

If AI changes a role from preparing information to reviewing it, the person may need deeper judgement about evidence, uncertainty and exceptions. Leaders must account for that shift in expectations.

Activation should begin at a scale that allows learning. Observe where employees need help, where customers encounter difficulties and where the design creates additional work elsewhere.

Then act on what those observations reveal.

4.  Amplify through evidence and resource decisions.

A successful trial creates an investment decision.

Can the improvement hold at greater volume? Does it depend on exceptional individuals or temporary support? What happens when it reaches a different customer group or a team with less experience? Have the benefits survived the cost of review, maintenance and error correction?

Scale should follow credible answers.

Amplifying also includes withdrawing resources. When a new process is established, the old process should be retired where appropriate. When an initiative fails to justify further investment, leaders need to stop it.

Otherwise, transformation accumulates as additional work. The organisation carries new systems, old systems and the effort of reconciling them.

These four disciplines should inform one another. Early implementation may reveal a weakness in the design. A test may challenge the original business assumption. Leaders need a process that allows evidence to change the plan.

BE EXPLICIT ABOUT WHAT REMAINS DEPENDABLE

Permanent transformation asks a great deal of an organisation. People need to know what they can rely on while their work evolves.

Customers need continuing service. Employees need clarity about present responsibilities and fair treatment when those responsibilities change. Teams need confidence that raising a problem will lead to examination rather than blame.

These commitments need practical expression.

If learning matters, provide time for it. If customer continuity matters, fund the transition arrangements. If employees are expected to exercise judgement, give them the information and authority to do so. If a new priority is urgent, decide which existing demand will be reduced.

Structural empathy begins with these choices. Leaders have to understand the demands their decisions create for the people carrying them out.

The credibility of perpetual transformation depends partly on whether employees experience it as purposeful improvement or as an expanding list of obligations.

MEASURE THE CAPABILITY YOU ARE TRYING TO BUILD

Programme milestones remain useful. They tell us whether agreed work is being delivered. To understand whether the organisation is becoming more adaptable, I would add a different set of questions.

How long does it take us to recognise a material change in a business assumption? How quickly can we resolve a decision that crosses functions? Can we move resources when evidence changes? How long does it take people to become proficient in a redesigned workflow? Do improvements persist after the programme team leaves?

There is no need to compress these into a single transformation score. Their value is in exposing where the organisation struggles to respond.

The answers may also challenge executive behaviour.

If every decision returns to the same small group, leadership attention becomes a constraint. If funding cannot move until the next annual cycle, the organisation’s response is limited by its planning process. If managers are rewarded for protecting existing activity, we should not be surprised when resources remain there.

Building a permanent capability requires leaders to change the conditions that produce these outcomes.

BEGIN WITH ONE CONSEQUENTIAL TEST

At your next executive review, choose one disruption that could materially affect the business.

Trace its implications to a customer or business outcome. Identify the capabilities required to respond. Examine where the current operating model would help and where it would slow the response.

Then make the decisions concrete. Name the outcome owner. Fund a bounded test. Protect the capacity needed to learn. Establish what would justify expansion, revision or a stop.

Ask what the organisation should retain from that work: better information, stronger judgement, clearer decision rights or a capability it can reuse elsewhere.

That is how adaptation becomes part of how the enterprise operates. A transformation programme should leave behind more than the change it was commissioned to deliver. It should leave the organisation better able to make its next consequential change.

For senior leaders, that is the enduring responsibility.

If your core business assumptions changed tomorrow, which capability would you need most—and how quickly could your organisation bring it into action?

Next in the series: Give transformation clear ownership.

Research underpinning this article:

[1] World Economic Forum and Accenture (2026), Organizational Transformation in the Age of AI: How Organizations Maximize AI’s Potential.

[2] Marlina, D., Setiawan, Y., and Sojanah, J. (2026), Transformation of Organizational Models and Structures in the Digital Era: A Systematic Literature Review.

The onboarding example is illustrative. Anchor–Architect–Activate–Amplify and the proposed leadership practices are a synthesis informed by the research.