Most strategy documents describe a destination. Fewer describe the machine that will actually get there — who decides what, how quickly, and with whose sign-off. That machine is the operating model, and in practice it constrains the strategy far more than the strategy constrains it.
A plan that assumes fast, decentralized decisions will stall inside an organization that routes everything through one desk. A plan that depends on tight coordination will fragment inside a company built for local autonomy. The plan is not wrong in either case. The model underneath it simply cannot carry it.
Where the model quietly stops working
Operating models are rarely redesigned; they accrete. A reporting line added for one hire, an approval threshold set for a problem that no longer exists, a committee that meets out of habit. Individually reasonable, together they become the reason good decisions arrive late.
The signal to watch is not conflict — it is delay. When capable people agree on what should happen and it still does not happen, the model, not the people, is usually the constraint.
The discipline
Redesigning an operating model is not reorganizing the chart. It is deciding, deliberately, where each class of decision should live, how much it should cost to make, and who is accountable for the outcome rather than the process. Get that right and the strategy tends to execute itself. Get it wrong and no plan survives contact with the calendar. If your plan and your organization seem to be pulling against each other, that tension is usually worth a conversation.
