Operating Model Design

Organizations rarely design their operating models from a blank page. They grow through acquisitions, new products, reorganizations and quick fixes, and over time the way they run becomes a patchwork of decisions made for different reasons. Eventually the patchwork starts to slow things down. Decisions bounce between committees, teams duplicate work, data does not match across systems and new strategies struggle to gain traction. Operating model design is the deliberate work of deciding how the organization should run instead, based on what the strategy requires.

Good operating model design looks at all the elements of the operating model together. Changing the structure without changing processes and decision rights tends to move problems around rather than solve them. Introducing new technology without redesigning work rarely delivers the expected gains. Designers therefore use principles, frameworks and options analysis to make consistent choices across structure, processes, people, technology, data, locations, suppliers and governance. For executives, strategy and transformation leaders, HR, finance and enterprise architects, operating model design is one of the most consequential decisions they make.

Definition of Operating Model Design

Operating model design is a structured process for defining how an organization will deliver its strategy, in which leaders set design principles, assess the current state, develop and evaluate options for each element of the operating model, choose a target design and plan the transition to it.

Its output is usually a target operating model. It overlaps with organizational design, which focuses on structure and roles, and with defining decision rights.

Key Design Choices

Centralization. Which activities are run centrally, which are run in business units and which are shared, often through a federated operating model.

Organizing axis. Whether the primary structure follows functions, products, customers, regions or a matrix of these. The choice signals what the organization values most, such as functional expertise, product speed or customer intimacy.

Sourcing. Which work is done in-house, in shared services, through partners or by outsourced providers. These choices depend on whether the work is a source of competitive advantage or a commodity that others can perform more cheaply.

Decision rights. Who has authority over strategy, budgets, priorities, hiring and technology choices.

Management system. How planning, funding, performance reviews and governance forums work.

Design Principles

Design principles translate strategy into guidance for choices, such as putting customer-facing decisions close to the customer or standardizing back-office processes.

They help leaders evaluate options consistently and resist designs that serve individual interests rather than the strategy.

Good principles are few, specific and occasionally in tension, forcing explicit trade-offs.

They should be agreed by the senior team before options are developed, not after. Principles agreed after the fact tend to be written to justify a preferred option rather than to guide the choice.

Importance of Operating Model Design in Enterprise Operations

Design links strategy to execution. A deliberate design ensures the organization has the capabilities and decision paths the strategy depends on.

It reduces friction. Consistent choices across structure, processes and systems remove duplicated work and unclear handoffs. Teams spend less time coordinating and more time delivering.

It also makes change manageable. A clear target design gives transformation programs a defined destination and a basis for planning. It also gives employees a clear picture of where the organization is heading.

Operating Model Design and Financial Management

Design choices such as centralization, sourcing and location have large effects on cost, so options should be evaluated with clear cost estimates.

One-time costs of transition, including systems changes, severance, relocation and temporary double running, must be weighed against expected savings and benefits.

Designs that change funding processes, such as moving from project to product funding, affect how budgets are set and tracked.

Benefits should be tracked after implementation to confirm that the design delivers what was promised. Without this tracking, organizations often cannot tell whether a redesign succeeded or simply added cost.

Common Challenges

Design is reduced to drawing a new org chart, while processes, systems and decision rights stay unchanged. People then carry on working the old way under new titles, and the expected benefits never appear.

Leaders choose options to protect their own scope rather than following agreed principles.

The design is too detailed too early, consuming months before people see any change. Long design phases also create uncertainty that can drive talented people to leave.

Implementation is underestimated, and the organization struggles with the new design because it was not supported with training, systems and change management.