Rethinking S&OP: from monthly ritual to decision engine

Most S&OP fails the same way. A beautiful process nobody follows feeds numbers nobody believes into a meeting that ends with a request for better numbers. The calendar invite survives; the decisions don’t.

The ritual, diagnosed

Walk into a struggling S&OP cycle and you’ll find the same four things.

• Review without decision. The executive meeting is a presentation. Options are described; none is chosen. The real choices are made afterwards, by email, by the loudest function.
• Numbers without ownership. The demand number is “from the system”, the supply number is “from the plants”, and the gap between them belongs to nobody.
• Cadence without consequence. Miss the pre-S&OP deadline and the cycle still runs. Within a year, every deadline is advisory.
• Tooling that mirrors the spreadsheet. Kinaxis or IBP was configured to reproduce the old workbook, so it inherits the old arguments.

Rebuilding around decisions

Start with the decisions, not the steps. List the six to ten decisions the cycle must produce — which demand to chase, which supply constraint to relieve, which customer to short, which capital to approve. Design backwards from each: what information, from whom, by when.

One plan. Not a demand plan, a supply plan and a financial plan that get reconciled in the meeting. One plan, in one system, with the gaps visible before the meeting so the meeting can close them.

Named owners and an accountability rhythm. Each number has a person. Each decision has a deadline and a record. The executive meeting reviews what was decided last cycle and what happened — which is the only way a plan earns trust.

Cadence with teeth. The cycle runs on the clock. Inputs that miss the gate are excluded and visibly so. It feels harsh for two cycles, then it becomes the reason the process works.

Tooling to match. Configure the platform for the decisions, not the slides. Scenario comparison, not variance reporting. A scorecard the executive can read in three minutes.

What “trusted” looks like

You’ll know the rebuild has worked when three things happen: the executive meeting gets shorter, the number of decisions it records goes up, and someone outside supply chain quotes the plan as fact in their own meeting.

That’s the outcome our S&OP / IBP Transformation work is measured on. The first gate is a two-week assessment of your current cycle — decisions, owners, cadence, tooling — that ends with a plan you can act on.

Rebuilding it, in the order that works

Most S&OP rebuilds fail in the same way the original did: they start with the process map. Start with the decisions instead, and the process falls out of them.

Week one to two: list the decisions. Get the six to ten decisions the cycle must produce, written as decisions — “which constrained line do we protect”, “which customer do we short”, “do we approve the capital for the second shift” — not as activities. If the list is longer than ten, the cycle is doing work that belongs elsewhere. If it is shorter than four, you have a reporting meeting, not a planning cycle.

Week three to four: work backwards to inputs. For each decision, what has to be known, by whom, by when. This is where the real cadence appears, and it is usually different from the one in the current process document.

Week five to eight: name the owners. Every number gets a person. Not a function — a person. The demand number belongs to a named commercial leader who will be in the room when it is wrong. This step generates more resistance than any other, and it is the one that makes the difference.

From week nine: run it with teeth. Inputs that miss the gate are excluded and visibly so. Two cycles of that feels brutal; by the third, the deadlines hold themselves.

The tooling question, answered honestly

Kinaxis or IBP will not fix an S&OP process, and configuring either to reproduce your existing spreadsheets guarantees you inherit every argument you already have.

What the platform genuinely changes is the cost of asking “what if”. When a scenario takes twenty minutes instead of two days, the executive meeting stops being a presentation of one number and becomes a comparison of three options — which is what a decision looks like. Configure for that, and leave the variance reporting to the reporting tools.

One practical rule: build the executive scorecard before you build the workbooks. It forces the conversation about which measures the business will actually be run on, and everything downstream inherits that clarity.

The measures that tell you it worked

Forecast accuracy is the obvious one and the least useful in the first year — it moves slowly and it is contested. Better early indicators:

• Decisions recorded per cycle, and how many were revisited next cycle. Rising decisions and falling revisits is the shape you want.
• Time from data cut to executive meeting. If it is more than five working days, most of the cycle is spent preparing rather than deciding.
• Number of separate demand numbers in circulation. The target is one. Most organisations start at three or four and are surprised to learn it.
• Whether anyone outside supply chain quotes the plan. Unmeasurable, and the truest signal there is.

The part nobody budgets for

An S&OP rebuild is a change of who decides what. That is a political programme wearing a process programme’s clothes, and it needs executive air cover that survives the first genuinely unpopular decision the new cadence forces.

If that sponsorship isn’t real, the cycle reverts within two quarters — not because the design was wrong, but because the first time the process produced an answer somebody senior disliked, the process lost. Secure that before the first workshop, and treat its absence as a reason to delay rather than a risk to log.