How to redesign your operating model without a big-bang restructure

Most operating model redesigns start too big. New structures, new role titles, new governance forums, new reporting lines. The logic is often sound, but the change lands as disruption before it creates value.

A better route is to redesign the operating model in the flow of work. Keep the organisation stable enough to perform, while changing the parts that make performance harder than it needs to be.

Start with the work, not the org chart

An operating model is how work gets done. It includes decision rights, funding, governance, roles, routines, measures, technology, and behaviours. Structure matters, but it is only one part of the system.

Before changing reporting lines, ask:

• What work matters most to our strategy?
• Where does that work slow down?
• Which decisions take too long or get escalated too often?
• Where do teams depend on too many other teams to deliver?
• What are leaders spending time on that adds little value?

This shifts the conversation from “who reports to whom?” to “what stops value moving?” That is where useful redesign begins.

Map the current operating friction

You do not need a six month diagnostic. You need a clear view of the main constraints.

Look for patterns such as:

• Priorities change faster than teams can respond
• Teams are funded by function, but outcomes cut across functions
• Governance checks activity, not progress or risk
• Product, technology, operations, and commercial teams plan separately
• Leaders make decisions that should sit closer to the work
• People are busy, but accountability for outcomes is unclear

Use interviews, delivery data, customer feedback, and a few working sessions. The goal is not a perfect map. It is a shared view of the operating problems that most affect performance.

Pick a thin slice to redesign

Avoid redesigning the whole organisation at once. Choose one important value stream, customer journey, product area, or internal service. It should be meaningful enough to matter, but contained enough to change safely.

For that slice, redesign the minimum set of elements needed to improve flow:

• Clear outcome ownership
• A smaller number of decision forums
• Defined decision rights for teams and leaders
• Cross-functional planning routines
• Measures linked to customer, colleague, and business outcomes
• Simpler handoffs between teams
• Capacity set aside for improvement, not just delivery

This creates a practical test of the future model. It also avoids the abstract debates that often slow operating model work.

Change leadership routines first

Many operating model issues are reinforced by leadership habits. If leaders keep asking for the same reports, approving the same decisions, and rewarding the same behaviours, the model will not change.

Start by redesigning leadership routines around the thin slice:

• Replace status meetings with decision meetings
• Review outcomes and risks, not task lists
• Set fewer priorities and protect them for longer
• Push decisions to the lowest sensible level
• Make trade-offs visible when capacity is constrained
• Ask what the system is making hard, not who is at fault

These changes are low cost, but they send a strong signal. They show people how the new model is meant to work.

Treat structure as a later decision

Sometimes structure does need to change. But it should come after you understand what the work needs.

By testing new routines, decision rights, roles, and measures first, you learn which structural changes are actually necessary. You may find that the issue is not reporting lines. It may be unclear ownership, duplicated governance, too many priorities, or incentives that pull teams in different directions.

If structure does need to shift, you can make a targeted change with better evidence and less disruption.

Scale what works

Once the thin slice shows better performance, capture what has changed. Be specific:

• Which decisions moved closer to the work?
• Which meetings stopped or changed?
• Which roles became clearer?
• Which measures helped leaders steer better?
• Which dependencies were removed or managed differently?

Then extend the patterns to the next slice. Do not copy everything blindly. Keep the principles consistent, but adapt the design to the local work.

The practical path

A non-big-bang redesign needs discipline. It is not a soft option. It means making real choices about priorities, power, decision making, and accountability, but doing it in a way the organisation can absorb.

The sequence is simple:

• Understand where work gets stuck
• Choose a meaningful slice
• Redesign the operating elements around that work
• Change leadership routines
• Test, learn, and adjust
• Scale proven patterns
• Make structural changes only where evidence supports them

The aim is not to avoid change. It is to avoid unnecessary disruption. The best operating models are not designed in a slide deck and launched in one moment. They are built through focused changes that make it easier for people to deliver the outcomes the organisation needs.