Working context
Most organizations can describe their strategy in a sentence. Fewer can show where, week to week, that sentence turns into decisions, handoffs and routines. An operating model review looks at that translation layer: who decides what, which processes carry the work, what information moves between teams, and where effort quietly leaks. It is less about drawing a new chart than about seeing the system that already exists.
Using the Context, Choice and Consequence lens from the Businessphere home page, this brief walks through a review a leadership team could run in a few working sessions. Businessphere Consulting is an independent publication and does not advise any organization, so the examples are hypothetical. Adapt them to your own setting, and involve qualified professionals where legal, financial or regulatory questions arise.
SECTION 01Map how the work actually flows
Begin with one outcome the strategy depends on, such as getting new customer orders fulfilled reliably, and trace it from trigger to result. Write each step, the person or team who performs it, the tool they use and the decision they make. Include the informal steps, like the quick question posted in a chat channel because the official form is slow. Those workarounds show where the designed model and the lived one differ. Hypothetical example: a regional team approves discounts in a shared spreadsheet that finance reviews at month end. The map reveals that the real approval point sits with one coordinator, not with the manager named in the policy. Keep the map to a single page so people can argue about it productively.
SECTION 02Test ownership, cadence and evidence
Once the flow is visible, examine three things at each step. Ownership: is one named role accountable, or does everyone assume someone else is? Cadence: how often does this step meet, report or decide, and does that rhythm match how fast the business changes? Evidence: what information would show that the step is working, and who sees it? Many reviews stop at the first question, yet a clear owner with a quarterly review cycle can be too slow for a weekly problem. Hypothetical example: a product team owns the roadmap, but customer complaints reach them only through a monthly summary. The owner exists, the cadence is off, and the evidence arrives after the choices are already made. Mark each step green, amber or red against those three tests.
SECTION 03Decide what to change, and what to leave alone
A review that produces thirty findings often produces no change. Sort what you find into three groups: friction that costs time every week, gaps that put the strategy at risk, and untidiness that is merely irritating. Address the second group first, then the first, and tolerate the third unless it grows. Before changing a step, ask what it quietly protects. A slow approval might exist because of a past error, a compliance duty or a customer promise, and removing it could trade a visible delay for an invisible exposure. Pilot changes in one unit, define the signal that would show improvement, and set a date to look again. If a change touches employment terms, contracts or regulated activity, involve qualified advisers before acting.
Checks to carry into the decision
- Pick one outcome the strategy depends on and trace it from trigger to result on a single page.
- Record informal workarounds alongside official steps, since they show where the designed model and the lived one differ.
- Name one accountable role for each step, and note where two roles believe the other owns it.
- Compare each step's review rhythm with how quickly the underlying situation changes.
- Ask what evidence would show a step is failing, and who would see it first.
- Pilot one change in a single unit and set a date to review the result.
How to get the most from it
Read the three briefs in the order the home page lists them: review the operating model, structure your priorities, then test the conditions behind growth. Each brief uses hypothetical examples and ends with questions a leadership team can discuss before a planning session.
Common questions
Questions readers ask
How long should an operating model review take?
It depends on scope, so it is better to size the review to one outcome than to a deadline. A single process trace can often be done in a few working sessions, while a whole-organization review takes longer and needs more stakeholders. Start narrow, learn what the first trace reveals, and extend only where the findings justify more effort.
Who should be in the room?
Include the people who do the work as well as those who own it. Managers describe the designed process, while practitioners know the workarounds. A neutral facilitator can help if the review touches sensitive questions about roles. Be clear from the start that the purpose is to understand the system, not to evaluate individuals.
Is an operating model the same as an org chart?
No. An org chart shows reporting lines. An operating model also covers processes, decision rights, information flows, tools and the rhythm of review. Two organizations with identical charts can run very differently. That is why the review traces work rather than titles, and why the chart alone rarely explains a recurring delay or dispute.
Bringing it together
An operating model review earns its keep when it changes one real thing and shows why. Resist the urge to redesign everything at once. Trace one outcome, test it for ownership, cadence and evidence, and let the results guide the next step. These notes are general and cannot assess any particular organization, so consult qualified professionals on legal, financial or regulatory matters.
These briefs are general business education from an independent publication and are not consulting, financial, legal or investment advice, so review important decisions with qualified professionals who can examine your actual circumstances.