Operating Model Redesign: Make Critical Decisions Faster

Operating model redesign should start with the decisions that determine performance, not the boxes that describe reporting lines. Before moving teams, establish where value is being lost, who has authority to act, and what happens when a decision stalls.

What is the gap between our value agenda and our delivered performance?

The gap is the measurable difference between your strategic commitments and the outcomes your organization consistently delivers. Define it through a small set of business measures, then trace missed outcomes to specific decisions, handoffs, and constraints. Do not assume every performance shortfall requires a structural solution.

Start with the value agenda: profitable growth, stronger cash conversion, reliable delivery, or better returns on invested capital. For each commitment, record the intended outcome, actual performance, accountable executive, and relevant timeframe. Separate external pressures from internal execution failures. A construction business facing lower margins may have a pricing problem, a project-selection problem, or slow approval of scope changes. Those require different interventions, even when they appear in the same financial result.

Follow the work behind the numbers. Examine recent bids, investment requests, procurement exceptions, or product releases. Identify where work waited, decisions were reopened, or accountability changed hands without a clear acceptance point. Establish a baseline for decision time, rework, and commercial impact. The output should be a short list of value-critical decisions—not a catalogue of every organizational frustration. That list becomes the design brief.

Who decides, who gets consulted, and who is only informed?

Assign one accountable decision owner wherever authority can legitimately sit with one role, and distinguish required consultation from notification. A decision rights matrix should specify the decision, authority limits, required inputs, consultation obligations, and communication responsibilities. Where collective approval is mandatory, define voting rules and accountability explicitly.

Build the matrix around actual decisions rather than broad activities. “Manage pricing” is too vague; “approve a bid below the agreed margin threshold” is testable. Name the role authorized to decide, the evidence it needs, and the boundaries of its discretion. Finance may validate economics, operations may assess delivery capacity, and legal may identify contractual exposure. Consultation provides input; it does not create an informal veto. Any veto must have a defined basis, such as a compliance requirement.

Those who are informed receive the outcome and rationale without becoming another approval stage. For recurring cross-functional decisions, specify how conflicting advice is resolved and who owns implementation after approval. In medical technology or aerospace, preserve required quality, safety, and regulatory controls rather than treating them as removable friction. Test the matrix against several recent cases: if participants still disagree about who could authorize the next step, the design is not yet usable.

How long should a decision be allowed to take before it escalates?

Allow only as much time as the decision’s risk, reversibility, and cost of delay justify. Set a decision deadline, a consultation window, and a named escalation route before work begins. Escalation should resolve a defined blockage, not automatically transfer every overdue item to the chief executive.

There is no universal service level for decisions. A reversible customer exception may warrant a same-day response; an irreversible capital commitment needs deeper review. Set deadlines by decision category and distinguish preparation time from approval time. Define the minimum evidence needed to start the approval clock, while tracking total elapsed time so incomplete submissions cannot conceal recurring delays. For mandatory safety or regulatory approvals, a deadline triggers intervention—not permission to proceed without authorization.

Escalation rules should state the trigger, recipient, required evidence, and expected resolution time. Escalate earlier when delay threatens a contractual milestone or exceeds an agreed exposure limit. The escalation note should present the choice, options, recommendation, and consequences of waiting. Review overdue decisions for patterns: repeated escalation may indicate inadequate delegated authority, missing expertise, or conflicting incentives. Adding another committee usually makes those problems harder to see rather than easier to solve.

Should we refine the current model or move to a new design?

Refine the current model when performance gaps come mainly from unclear authority, inconsistent processes, or weak management discipline. Move to a new design when strategy demands capabilities, economics, or coordination that the existing model cannot support. Test that distinction through bounded pilots before committing to enterprise-wide structural change.

The practical answer to how to redesign operating model arrangements is to compare two credible options: repairing the current system and replacing its underlying logic. Refinement might mean delegated pricing authority, common performance measures, or fewer approval layers. A new design may be justified when a product business adds lifecycle services, regional operations need shared capabilities, or an acquisition changes the scale of integration required. Evaluate both options against the same value agenda, including transition cost, execution risk, and management capacity.

A target operating model must connect decision rights with processes, capabilities, technology, governance, and incentives. Pilot those elements in a bounded business area or decision category, with success criteria and a review date agreed upfront. Check whether faster decisions preserve quality and improve business outcomes rather than merely shifting work elsewhere. Redraw reporting lines only where the evidence shows a structural barrier. Then sequence the transition with explicit ownership of customer continuity, controls, and benefits delivery.

Bottom line

Operating model redesign earns its value when critical decisions become clearer, timely, and accountable. Structure should reinforce that system, not substitute for it.

1. Within two weeks, identify five value-critical decisions and baseline their elapsed time, rework, and impact on business outcomes.
2. Assign decision owners, consultation requirements, authority thresholds, and escalation deadlines; validate them against recent real cases.
3. Run a bounded pilot with agreed outcome and control measures, then use the results to choose targeted refinement or a new design.

FAQ

What is the gap between our value agenda and our delivered performance?

The gap is the measurable difference between your strategic commitments and the outcomes your organization consistently delivers. Define it through a small set of business measures, then trace missed outcomes to specific decisions, handoffs, and constraints. Do not assume every performance shortfall requires a structural solution.

Who decides, who gets consulted, and who is only informed?

Assign one accountable decision owner wherever authority can legitimately sit with one role, and distinguish required consultation from notification. A decision rights matrix should specify the decision, authority limits, required inputs, consultation obligations, and communication responsibilities. Where collective approval is mandatory, define voting rules and accountability explicitly.

How long should a decision be allowed to take before it escalates?

Allow only as much time as the decision’s risk, reversibility, and cost of delay justify. Set a decision deadline, a consultation window, and a named escalation route before work begins. Escalation should resolve a defined blockage, not automatically transfer every overdue item to the chief executive.

Should we refine the current model or move to a new design?

Refine the current model when performance gaps come mainly from unclear authority, inconsistent processes, or weak management discipline. Move to a new design when strategy demands capabilities, economics, or coordination that the existing model cannot support. Test that distinction through bounded pilots before committing to enterprise-wide structural change.