INSIGHT

Execution Continuity During Transformation

Why successful transformation depends on an organization’s ability to change while continuing to operate effectively.

By Mónica González –

Transformation creates an unusual leadership challenge. An organization is trying to become something different while still needing to operate effectively every day.

Customers and patients still need to be served. Launches and commercialization priorities continue. Markets require decisions. Teams need direction. Regulatory and operational responsibilities remain. At the same time, structures, technologies, processes, capabilities, or ways of working may all be changing.

In my experience, this tension is one of the most underestimated dimensions of transformation. Organizations naturally focus on designing and implementing the future state. But transformation also needs to protect the organization’s ability to perform while that future state is being built.

Transformation creates two operating realities

During significant transformation, organizations effectively operate in two environments at once.

The existing organization remains responsible for current performance, while the emerging organization begins introducing new structures, processes, technologies, responsibilities, and expectations. For a period, neither environment is completely stable.

This creates practical questions that transformation roadmaps do not always resolve. Which processes remain in place during the transition? Who owns decisions when responsibilities are moving? How should teams prioritize current commitments against transformation work? When does authority transfer from an existing structure to a new one? What happens when the future-state design encounters operational realities that were not anticipated?

These are not peripheral implementation details. They determine whether the organization can move from one operating model to another without unnecessarily destabilizing performance.

Transformation is not only about reaching the future state. It is about maintaining the organization’s ability to operate while getting there.

The transition itself needs to be designed

Organizations often invest considerable effort defining the destination: the new operating model, organizational structure, technology environment, governance framework, or way of working.

The path between current and future state can receive less attention.

That path needs its own operating logic. Responsibilities may need to transfer progressively rather than on a single date. Temporary decision mechanisms may be required while new governance becomes established. Critical capabilities may need to remain duplicated for a period before legacy structures can safely be removed. Some activities may need protection from transformation demands because disruption would create disproportionate operational risk.

This does not mean creating another layer of transformation bureaucracy. It means deliberately managing the period in which old and new operating realities coexist.

Business-critical execution needs protection

Not every activity carries the same consequence if transformation disrupts it. Organizations therefore need to identify which areas of execution must remain particularly stable throughout the transition.

In life sciences, these may include critical launch milestones, regulatory commitments, market access activities, supply dependencies, patient-facing operations, major customer or stakeholder relationships, and other priorities where interruption could materially affect performance.

Protecting these activities does not mean isolating them from transformation. Some may need to change significantly. It means understanding their dependencies and sequencing change so that the organization does not unintentionally weaken a critical capability before its replacement is ready.

This is where transformation sequencing becomes an execution decision, not merely a program-management decision.

Decision rights become especially important during change

Transformation frequently changes who is responsible for what. Functions are redesigned, roles move, governance evolves, new capabilities appear, and existing structures begin to disappear.

During that transition, formal organizational charts can become less reliable guides to how decisions are actually made.

Clear decision rights are therefore particularly important. Teams need to know which responsibilities remain with the existing organization, which have transferred to the new structure, who can resolve issues spanning both, and where accountability sits when the transition itself creates ambiguity.

Without that clarity, decisions can stall between old and new structures. People may hesitate because authority is uncertain, or several groups may assume responsibility for the same issue while no one clearly owns the outcome.

Good transformation governance should reduce this ambiguity rather than add another reporting mechanism around it.

Transformation capacity is finite

Another common risk is assuming that transformation work can simply be added to existing operational responsibilities.

The same experienced people needed to design and implement change are often also responsible for running critical parts of the current business. Their knowledge makes them indispensable to the transformation, but their operational responsibilities do not disappear because the organization has launched a major change program.

This creates a genuine capacity constraint.

Organizations need to make explicit choices about priorities, resources, sequencing, temporary support, and where additional expertise is required. Otherwise, transformation can gradually consume the leadership attention and organizational capacity needed to maintain current performance.

Execution continuity therefore depends partly on recognizing that change itself consumes capacity and planning accordingly.

AI can support the transition without owning it

AI can make transformation execution considerably more manageable. It can help synthesize information across workstreams, identify dependencies, maintain knowledge as responsibilities change, support scenario analysis, track decisions, improve operational visibility, and reduce administrative coordination.

These capabilities are particularly valuable during transition because information is moving at the same time as organizational responsibilities.

But AI cannot decide which capability is safe to retire, whether a temporary operating compromise is acceptable, which business priority requires protection, or how responsibility should move between leaders and teams. Those decisions require context, judgment, stakeholder understanding, and accountability.

The opportunity is to use AI to make the transition more visible and manageable while experienced leaders remain responsible for navigating it.

Human-Led. AI-Enabled.

Continuity does not mean resisting change

Protecting execution continuity should not become an argument for preserving the existing organization.

Transformation exists because something needs to change. Existing structures may need to disappear, responsibilities may need to move, established processes may need to be replaced, and teams may need to adopt fundamentally different ways of working.

Continuity means managing those changes without unnecessarily losing the capabilities, decisions, knowledge, relationships, and operational momentum the organization still needs.

The strongest transformations therefore manage two outcomes simultaneously: building the organization that is needed next while keeping the organization capable of performing today.

That ability to change without losing the capacity to execute is what makes execution continuity a transformation capability.