When S&OP Becomes Theater, and How to Turn It Back Into Planning

The Monday Ritual

Monday morning. A pharma company’s cross-functional team gathers for its monthly S&OP meeting. Demand planners present their forecasts. Supply planners show capacity constraints. Finance reviews the financial implications. After two hours of discussion, a plan emerges. Everyone signs off.

By Friday, the plan is fiction.

Most S&OP processes have a hidden consequences gap: a plan that looks aligned on Monday and is fiction by Friday. The gap is not between the plan and reality. It is between the plan and the incentives that override it.

The Week After Planning

Tuesday: A key account calls with an urgent request. Sales commits to a delivery date that wasn’t in the plan. They never checked it. In most pharma and CP companies, sales updates their own plan and informs supply chain after the fact.

Wednesday: Operations shifts production to cover the commitment. The carefully balanced schedule adjusts. Someone else’s order moves back.

Thursday: Supply chain notices the inventory build for next month’s promotion just got raided. The promotion that marketing has already committed to retailers.

Friday: Finance asks why actuals diverged from plan. Again.

The S&OP meeting produced a document. It did not produce constraints that shaped behaviour.

The Difference Is Whether Deviation Has Consequences

If your plan can be ignored without consequence, you don’t have a plan. You have a report.

A reporting process tells you what happened. It produces forecasts, budgets, and reconciliations. These documents inform decisions but don’t bind them.

A planning process creates constraints that shape behaviour. It produces commitments with consequences. When someone deviates, they must explain which trade-off they’re making and who bears the cost.

Most organisations run the first and call it the second.

Ask what happens when someone deviates from the plan. If the answer is “nothing, we just update the forecast,” you have a reporting process dressed as planning. If deviation requires escalation, explanation, and a documented trade-off, you have actual planning.

You can have world-class IBP templates and still be doing theater if deviation has no consequences.

Why Theater Persists

S&OP theater persists because it serves organisational needs that have nothing to do with planning.

It creates the appearance of alignment. Executives can tell the board that cross-functional teams meet monthly to coordinate. The meeting happened. Alignment was discussed. The box is checked.

It distributes blame. When results miss targets, everyone was in the room. Everyone signed off. No individual is accountable because the collective approved the plan.

It avoids conflict. Real planning forces trade-offs. Someone’s number goes down so someone else’s can go up. Theater lets everyone keep their optimistic forecasts. Reality sorts it out later.

It satisfies the process. Large organisations require planning processes. The process requires meetings, documents, and sign-offs. S&OP delivers all three without requiring the harder work of actual coordination.

The ritual continues because stopping it would require admitting it wasn’t working.

What Theater Actually Costs

The cost of running reporting as planning is not abstract. It shows up in numbers that every operations leader tracks.

OTIF drops. The Monday plan assumed 92% on-time-in-full. By Friday, three key account overrides reshuffled the production schedule. OTIF lands at 78%. The gap is not a forecasting error. It is the direct result of commitments made outside the plan.

Expediting costs spike. Every unplanned commitment creates a chain of corrections. Air freight to cover a raided inventory build. Overtime to recover the shifted production schedule. In one chemicals company, 40% of monthly logistics cost was expediting driven by plan deviations that were never visible at the time of the commitment.

Working capital bloats. When the plan is unreliable, every function builds its own buffer. Sales overstates demand to secure supply. Operations holds safety stock against unpredictable schedule changes. Finance sees inventory climbing and cannot trace it to any single decision. The buffers compound because nobody trusts the plan.

Margin erodes invisibly. Discounts committed without visibility into production cost. Volume shifts that change the cost base after pricing was agreed. Each individual deviation looks small. In aggregate, they are the difference between the margin the plan projected and the margin the quarter delivers.

None of these show up as “S&OP failure” in any report. They show up as operational noise. That is what makes theater so persistent: the cost is real but the cause is invisible.

What Planning Actually Requires

Planning that shapes behaviour requires three things S&OP meetings rarely provide.

Explicit constraints. Not guidelines. Constraints. If warehouse capacity is 50,000 pallets, that’s a hard limit. If working capital is capped at €15M, that’s a boundary. Constraints must be known before decisions are made, not discovered after.

Visible trade-offs. Today, sales commits without seeing the supply impact. That is not a people problem; it is a systems problem. No tool in the current workflow surfaces the trade-off at the point of commitment. When sales wants to commit to an order outside the plan, they should see immediately: this delays Customer B’s shipment by three days, or this pulls inventory from next month’s promotion. The trade-off is explicit before the commitment, not reconstructed after.

Accountable deviation. Someone who deviates from the plan must document why. Not as punishment, but as organisational learning. If sales consistently overrides demand plans for key accounts, maybe the demand plan needs to weight key accounts differently. The deviation becomes data.

Without these, S&OP produces documents that describe intentions. It does not produce infrastructure that shapes decisions.

The Consequences Gap

Planning assumes decisions will follow the plan. Reality is that decisions follow incentives. When the incentive to satisfy a key account exceeds the consequence of deviating from the plan, deviation is rational.

Most S&OP processes have no mechanism to close this gap. The plan exists. Deviation happens. Someone reconciles the numbers. The cycle repeats.

Closing the gap requires making the consequences of deviation visible before the decision. Not after, when finance asks what happened. Before, when sales is about to commit.

Unless decision rights and incentives reflect the constraints in the plan, S&OP will always lose to local firefighting.

This is not a meeting problem. It is an infrastructure problem.

From Ritual to Infrastructure

The meeting is not the planning. The consequences are.

Organisations that transform S&OP from theater to planning don’t do it by running better meetings. They do it by building infrastructure that makes constraints visible, trade-offs explicit, and deviations documented.

When a salesperson opens the system to commit to a delivery, they see: this order fits within plan, or this order requires pulling from these allocations, will delay Customer B by three days, and increases working capital exposure by €400k. The trade-off is visible before they commit, not discovered when operations adjusts the schedule.

When demand changes, the system shows the capacity impact, the inventory implication, and the financial effect in real time. The cross-functional view is continuous, not monthly.

When someone deviates, the deviation is captured. Not as surveillance, but as learning. The pattern of deviations reveals where the plan fails to match reality. That signal improves the next plan.

The Real Test

Next time you leave an S&OP meeting, ask yourself:

• Will anyone’s behaviour tomorrow be different because of what we decided today?
• If someone deviates from this plan next week, will there be consequences?
• Can I trace from this plan to the constraints it creates?

If the answers are no, you didn’t just do planning. You did theater.

The meeting felt productive. The document looks professional. The process was followed.

But the plan will meet reality on Tuesday. And reality will win.

If you recognise the theater, start small: pick one kind of deviation, say key account overrides, make the trade-off visible before the commit, and document it. Then let that data reshape the next plan.