Introducing The SANDWICH Framework

Your team can’t “run faster” if every important choice still needs a meeting to get unblocked-so ask yourself this: when something changes mid-week, who gets to decide, and what do they use to decide in under an hour? If the answer is “we convene and hope,” you don’t have a decision problem-you have an operating model problem.

That’s exactly what decision-centric operations fixes. It shifts your day-to-day work from managing tasks to managing decisions: you make the decision earlier, assign it clearly, and attach execution to the decision outcome. Nadia, an Operations Director at a mid-sized services company, felt this pain when a key supplier started delivering partial loads. Her team spent days coordinating updates, while the field teams waited on guidance. Once she changed the system so frontline leads could decide within set rules, the schedule stopped wobbling every time the supplier changed.

What You Need to Know

Decision-centric operations means your organization plans and runs around decisions-who decides, what they decide, when they decide, and what evidence they use. The goal isn’t more meetings; it’s fewer delays between a signal and a choice.

The SANDWICH Framework is a practical way to build that decision system. It gives you a set of connected capabilities so you can detect early signals, align intent, coordinate execution, accelerate decisions, manage risk, use AI where it helps, and learn fast-then measure whether you actually improved value.

The Decision-Centric Compass is the chapter’s anchor for how you think. It forces you to orient every workflow around three things: decision ownership (who can decide), decision inputs (what information they must use), and decision speed (how fast they must decide). When those three stay clear, execution becomes easier because teams stop waiting for approvals that don’t add quality.

Ask yourself as you read: where do your delays come from-unclear ownership, missing inputs, or slow decision cycles?

Breaking It Down

Start with the difference between traditional management and decision-centric operations. Traditional management often centers on plans, approvals, and “progress updates.” Decision-centric operations centers on decision rights, decision criteria, and real-time learning from outcomes.

1. Map your current “approval path” for one real decision. Pick a decision your team makes weekly-like whether to reschedule a job, approve an exception, or switch a materials source. Write down every handoff from the first signal to the final call. You’re not trying to blame anyone; you’re exposing the friction points.

2. Name the decision, not the task. Teams often track work (“call suppliers,” “send emails”) instead of the decision (“choose supplier A vs B,” “grant a delivery exception”). Rewriting work into decision language matters because it makes ownership and criteria visible.

3. Assign decision ownership to the closest capable role. Nadia solved her supplier problem by moving the “reschedule vs. proceed with partials” decision from a central approvals queue to the operations lead who owned the schedule impact. The rule wasn’t “anyone can do it.” It was “the operations lead decides within defined limits.”

4. Define the decision inputs your team must use. If your input set changes every time, your decisions will too. Nadia required a short checklist: next delivery date, job priority, customer commitment window, and cost impact range. She didn’t add more data; she reduced what mattered to a small, repeatable set.

5. Set a decision speed target and a fallback. Decision-centric doesn’t mean “decide instantly.” It means “decide fast enough to prevent churn.” Nadia set an internal target: decide within one hour of the supplier update for jobs scheduled inside the next two days. If the required inputs weren’t ready, she used a fallback rule (proceed with partials for low-priority jobs, pause high-priority jobs until the inputs arrive).

Think of it like driving with a compass instead of a map. A map tells you where you could go; a compass keeps you oriented even when roads change.

Quick comprehension check: when you look at your one selected decision, can you point to the owner, list the required inputs, and describe the time limit?

Making It Work

Use Nadia’s supplier-change example as your build template-because it’s common, measurable, and painful when it’s slow.

First, collect one week of decision moments tied to that supplier issue. Then convert them into a decision rule set.

1. Pick the decision scope. Nadia focused on “reschedule vs. proceed with partial loads” for work starting within the next 48 hours. That scope prevented the team from turning every supplier change into a major rewrite.

2. Create a one-page decision record. It doesn’t need fancy tools....