operating model redesign · Insights
Operating Model Redesign: Stop Critical Decisions Stalling
November 17, 2026
Operating model redesign should begin with the decisions that determine performance, not the boxes that describe reporting relationships. When authority, accountability, and execution pull in different directions, a new org chart can preserve the same delays under different names.
What is the gap between our value agenda and our delivered performance?
The gap is the measurable difference between strategic commitments and actual outcomes, traced to the decisions and execution failures behind it. Start with the value agenda: growth, margin, cash, service, or risk reduction. Establish the performance shortfall, then distinguish operating model constraints from market conditions, capability gaps, and unrealistic assumptions.
Use a small set of commitments with clear baselines, accountable executives, and delivery dates. A construction business might examine project margin erosion; a logistics operator might examine service failures and working capital. For each shortfall, reconstruct the sequence from commercial commitment to delivery. Where did a decision wait, get reversed, or arrive without the resources needed to execute it? Interview the people doing the work, then validate their accounts against transaction records and approval histories.
The objective is not to label every problem a governance failure. Weak demand will not disappear when approval rights change. However, recurring exceptions can reveal a structural constraint: sales promises delivery dates that operations cannot authorize, or project leaders carry margin accountability without control over procurement choices. Quantify the affected value where evidence allows. That creates a redesign mandate tied to business outcomes rather than executive preferences about spans and layers.
Who decides, who gets consulted, and who is only informed?
Give each recurring decision one accountable decision owner, define mandatory consultation, and separate both from notification. A decision rights matrix should specify the decision, authority limits, required inputs, consultation deadline, and escalation route. Informed parties receive the outcome; they do not gain an implicit veto by appearing on a distribution list.
Build the matrix around decisions, not functions. “Approve a customer-specific engineering change” is usable; “engineering owns technical matters” is not. Specify who prepares the recommendation, who authorizes the trade-off, and who implements it. Consultation should bring relevant expertise into the decision without requiring universal agreement. Where law, safety, or regulation requires an independent approval, document that requirement explicitly rather than disguising it as consultation.
Authority must also come with boundaries. A regional leader might approve pricing within agreed margin and credit limits, while exceptions go to a named enterprise owner. Finance provides the economics; operations confirms deliverability; legal addresses contractual exposure. None automatically becomes a joint commercial decision maker. Test these assignments against recent disputes. If two executives still believe they have the final say, the matrix has recorded the ambiguity rather than resolved it.
How long should a decision be allowed to take before it escalates?
Set a decision deadline according to business urgency, reversibility, and risk, with escalation triggered by a missed deadline or breached authority limit. There is no universal clock. Define when timing starts, what constitutes a complete submission, who receives escalation, and what happens while the decision remains unresolved.
A routine supplier substitution within an approved specification should not follow the same timetable as a safety-critical design change. Set separate deadlines for input, decision, and escalation response. For example, a business could require a standard commercial exception to be decided within two working days of receiving complete information. That is a design choice to test against customer needs and risk, not an external benchmark. Missing information should prompt a specific request, not an indefinite pause.
Escalation must transfer authority to someone who can resolve the issue. Sending an overdue request to another coordination meeting merely relocates the queue. Define whether work continues within existing limits or pauses pending approval; silence must never substitute for required safety or regulatory clearance. Track elapsed decision time, overdue items, reversals, and escalation frequency. Repeated escalations of the same type usually warrant revised thresholds, better inputs, or stronger capability at the original decision level.
Should we refine the current model or move to a new design?
Refine the current model when its basic logic supports the strategy and failures are concentrated in specific interfaces or decisions. Move to a new design when the strategy requires fundamentally different capabilities, economics, or accountability. Choose the smallest change that can close the performance gap without preserving the constraint causing it.
Refinement can include revised authority limits, fewer approval layers, shared performance measures, and stronger process ownership. A more substantial redesign may be necessary when a product business moves into lifecycle services, acquisitions require integrated delivery, or local autonomy prevents enterprise-wide resource allocation. Assess the alternatives against customer value, economic accountability, execution capability, control requirements, and transition risk. Moving boxes is justified only when reporting relationships need to reinforce a different way of creating and delivering value.
For leaders asking how to redesign operating model arrangements, the practical sequence is outcomes, decisions, workflows, capabilities, then structure and enabling systems. Describe the target operating model in those terms and test it in one bounded business area. Confirm that decision owners can access data, deploy resources, and influence the measures on which they are judged. Scale only after the test shows better performance without unacceptable control failures or hidden workload shifts.
Bottom line
Operating model redesign succeeds when authority follows the value agenda and decisions translate into accountable execution. Redraw the organization only when the reporting structure must change to support that logic.
- Select three material performance gaps and trace each through recent decisions, handoffs, and execution failures.
- Build a decision rights matrix for the recurring decisions behind those gaps, including authority limits, consultation deadlines, and named escalation owners.
- Test revised rights and decision clocks in one business area; review performance and control outcomes before approving wider structural changes.
FAQ
What is the gap between our value agenda and our delivered performance?
The gap is the measurable difference between strategic commitments and actual outcomes, traced to the decisions and execution failures behind it. Start with the value agenda: growth, margin, cash, service, or risk reduction. Establish the performance shortfall, then distinguish operating model constraints from market conditions, capability gaps, and unrealistic assumptions.
Who decides, who gets consulted, and who is only informed?
Give each recurring decision one accountable decision owner, define mandatory consultation, and separate both from notification. A decision rights matrix should specify the decision, authority limits, required inputs, consultation deadline, and escalation route. Informed parties receive the outcome; they do not gain an implicit veto by appearing on a distribution list.
How long should a decision be allowed to take before it escalates?
Set a decision deadline according to business urgency, reversibility, and risk, with escalation triggered by a missed deadline or breached authority limit. There is no universal clock. Define when timing starts, what constitutes a complete submission, who receives escalation, and what happens while the decision remains unresolved.
Should we refine the current model or move to a new design?
Refine the current model when its basic logic supports the strategy and failures are concentrated in specific interfaces or decisions. Move to a new design when the strategy requires fundamentally different capabilities, economics, or accountability. Choose the smallest change that can close the performance gap without preserving the constraint causing it.