Operating Models: Where Strategy Becomes Organisational Reality

By Stephen Allan

Founder, Elevate Transformation

Strategy defines where an organisation wants to go. The operating model determines whether the organisation is actually designed to get there.

Most organisations understand the importance of strategy.

They invest considerable time defining ambition.

Where will we compete?

How will we create value?

Which customers will we serve?

What capabilities will differentiate us?

What outcomes do we want to achieve?

These choices establish direction.

But direction alone does not change an organisation.

At some point, strategic ambition must become organisational reality.

People need to work differently.

Capabilities need to be built.

Technology needs to enable new ways of operating.

Processes need to change.

Accountabilities may need to move.

Performance measures need to reinforce different outcomes.

And the organisation may need to interact with customers in fundamentally different ways.

This is where the operating model becomes critical.

Because strategy describes the organisation's intent.

The operating model determines whether the enterprise is designed to deliver it.

Strategy Has Organisational Consequences

Every meaningful strategic choice creates implications for the organisation.

A strategy built around customer intimacy may require different data, decision rights, capabilities and ways of working.

A productivity strategy may require process redesign, automation and structural simplification.

A digital strategy may change channels, roles, technology architecture and customer interactions.

A growth strategy may require new capabilities, operating capacity or organisational structures.

An AI-enabled strategy may fundamentally reshape work, decision-making and the capabilities the organisation requires.

The strategic choice is only the beginning.

The leadership question becomes:

What must become materially different about the enterprise for this strategy to work?

Without that translation, strategy can remain compelling at the executive level while the organisation continues operating much as it did before.

The Operating Model Is More Than Structure

Operating-model conversations are sometimes reduced to organisational charts.

Who reports to whom?

Where should functions sit?

How many layers should exist?

Which activities should be centralised?

These questions matter.

But structure is only one part of the system.

At Elevate, we define an enterprise operating model as:

An enterprise operating model is the integrated system through which an organisation organises and enables its capabilities to deliver strategy and create enterprise value.

That distinction matters.

An operating model is not simply a picture of the organisation.

It describes how the interconnected elements of the enterprise work together to enable the capabilities the strategy requires.

At Elevate, we consider that system across six interconnected dimensions:

Structure

How accountability, authority and organisational units are configured.

Leadership & Talent

The leadership, skills, behaviours and workforce capabilities required.

Technology & Data

The platforms, information and digital capabilities that enable the enterprise.

Ways of Working & Processes

How work flows across organisational boundaries and how decisions are made.

Performance & Value

How outcomes, performance and enterprise value are measured and managed.

Customer Model

How the organisation creates, delivers and sustains value for customers and stakeholders.

The important point is not the individual dimensions.

It is the connections between them.

The Enterprise Must Be Designed as a System

A change in one operating-model dimension often creates consequences elsewhere.

Introducing new technology without redesigning processes may simply digitise existing inefficiency.

Changing structure without clarifying decision rights can relocate ambiguity rather than remove it.

Redesigning customer journeys without changing internal accountabilities may create an experience the organisation cannot consistently deliver.

Building new capabilities without changing performance measures can leave old behaviours reinforced.

Automating work without reconsidering roles may create capacity without determining how that capacity should create value.

Each intervention may appear logical in isolation.

But transformation occurs at the level of the enterprise system.

That is why operating-model design should not become a series of independent functional exercises.

The question is not simply whether each component is improved.

It is whether the components work together to support the strategy.

The Future State Cannot Be Designed by Projects Independently

When an operating model is not sufficiently defined before mobilisation, projects inevitably begin making design decisions.

A technology initiative defines new processes.

A workforce programme creates new roles.

A customer initiative changes service models.

A data programme establishes new capabilities.

A restructuring exercise moves accountabilities.

Each decision may solve an immediate problem.

But collectively, the initiatives may be designing different versions of the future organisation.

This is a common source of transformation fragmentation.

Projects should contribute to building the future state.

They should not have to independently determine what that future state is.

The enterprise needs sufficient design clarity to provide a common direction for execution.

Not every detail must be resolved before execution begins.

But the major operating-model choices need to be sufficiently clear to guide subsequent design.

Otherwise:

The future organisation emerges from the accumulation of project decisions rather than deliberate enterprise design.

Capabilities Define What the Operating Model Must Enable

One of the most useful ways to translate strategy into operating-model design is through capability.

Strategy describes what the organisation intends to achieve.

Capabilities describe what the organisation must be able to do to achieve it.

The operating model determines how those capabilities will be organised and enabled.

This creates a powerful sequence:

Strategic Ambition
↓
Enterprise Outcomes
↓
Required Capabilities
↓
Operating Model
↓
Transformation Initiatives

Rather than moving directly from strategy to projects, leaders first ask:

What capabilities does this strategy require?

Which already exist?

Which need strengthening?

Which are missing?

Which are becoming less important?

Which could become sources of competitive advantage?

Once those questions are answered, operating-model design becomes more purposeful.

The organisation is no longer redesigning itself simply because change feels necessary.

It is designing the enterprise system required to enable specific strategic capabilities.

The Target Operating Model Defines the Desired Future Configuration

The operating model describes how the enterprise works.

A Target Operating Model takes the next step.

At Elevate, we define it as:

A Target Operating Model defines the desired future configuration of the enterprise operating model—how capabilities will be organised and enabled to deliver strategic outcomes and enterprise value.

It translates required enterprise capabilities into deliberate future-state choices across the interconnected dimensions of the organisation.

That does not mean specifying every detail of the future.

Nor does it mean designing a static blueprint that cannot change.

Its purpose is to establish enough coherence to guide enterprise design, investment and execution.

The Target Operating Model therefore provides a common reference point for the transformation:

What needs to become different?

What needs to remain consistent?

Which capabilities require strengthening?

How should the dimensions of the enterprise work together?

And what design choices must guide individual initiatives?

Design Is About Choices, Not Perfection

Future-state design can create another risk.

The pursuit of a perfect operating model.

Detailed organisational structures.

Complete process maps.

Technology architectures.

Role descriptions.

Governance models.

Measures.

Policies.

The objective should not be to design every element of the future before transformation begins.

Complex organisations will continue learning during execution.

Conditions will change.

Assumptions will evolve.

Some designs will need to adapt.

The purpose of future-state design is therefore not perfect prediction.

It is to make the critical enterprise choices required to create coherence.

Which capabilities matter most?

What design principles will guide the organisation?

Where should accountability sit?

What should be standardised?

Where is flexibility important?

Which processes need fundamental redesign?

What role should technology play?

What must remain consistent across initiatives?

Good operating-model design creates enough clarity to guide execution without pretending the future can be completely specified in advance.

 

The Current State Still Matters

Future-state design should not begin with an organisational chart.

Nor should it begin with an idealised vision disconnected from the organisation that exists today.

Transformation requires understanding the gap between the two.

What currently works well?

Where does performance break down?

Which capabilities are strong?

Where are structural constraints?

Which processes create friction?

Where is technology limiting performance?

What cultural or leadership conditions matter?

Which existing strengths should be protected?

This matters because transformation is not about replacing everything.

It is about determining what needs to change—and what does not.

A strong future-state design is grounded in strategic ambition while remaining anchored in organisational reality.

Operating-Model Choices Make Strategy Tangible

Operating-model design forces leaders to confront choices that can remain abstract at the strategy level.

Centralise or decentralise?

Standardise or differentiate?

Build or buy?

Automate or augment?

Global consistency or local responsiveness?

Functional efficiency or end-to-end customer ownership?

Control or autonomy?

Short-term productivity or long-term capability?

There is rarely one universally correct answer.

The appropriate choice depends on the strategy.

That is precisely what makes operating-model design so consequential.

It converts broad strategic intent into decisions about how the enterprise will actually work.

This is why operating-model design is a core discipline of enterprise transformation.

It makes the consequences of strategy tangible.

A strategy that cannot guide these choices has not yet been sufficiently translated into organisational reality.

From Strategy to Organisational Reality

The operating model is not an organisational-design exercise sitting beside transformation.

It is one of the principal mechanisms through which transformation occurs.

Strategy establishes intent.

Capabilities translate that intent into what the enterprise must be able to do.

The operating model determines how those capabilities will be organised and enabled.

The Target Operating Model defines the desired future configuration.

Transformation initiatives then build the required changes.

That sequence matters.

Without it, organisations can move too quickly from strategic ambition into projects.

And when that happens, projects inherit questions that should have been resolved at enterprise level.

The leadership question is therefore not simply:

What initiatives do we need to deliver our strategy?

It is:

What organisation do we need to become for our strategy to be executable?

That is a fundamentally different question.

It moves the conversation from activity to enterprise design.

From individual solutions to connected capabilities.

And from changing parts of the organisation to deliberately shaping the system as a whole.

Strategy becomes organisational reality when the enterprise is designed with the capabilities, accountabilities, technology, processes and ways of working required to deliver it.

That is the role of the operating model.

It is where strategic intent becomes organisational design—and organisational design makes execution possible.

The operating model is where strategy becomes organisational reality.

Explore the Elevate Perspective

Elevate Transformation provides leaders with a repeatable enterprise transformation system that connects strategic intent to required capabilities, future-state operating model design, execution and sustained enterprise value.

Explore the Elevate Enterprise Transformation Framework →

Take the free Transform or Improve? Executive Diagnostic →

Explore Elevate Advisory →