S&OP for companies without an S&OP team
Strip away the consulting vocabulary, and Sales & Operations Planning is one monthly meeting with three properties: everyone argues from one shared set of numbers, trade-offs are made visible before they are decided, and it happens every month, no matter what.
That’s it. The rest — software suites, maturity models, five-phase frameworks — is packaging.
I work in planning in the semiconductor industry, where S&OP is not optional: with lead times beyond 20 weeks, today’s planning mistake surfaces as next year’s crisis. What makes the process work at that scale is genuinely not the tooling. It is three habits: cadence discipline, clear decision rights, and the rule that there is only one demand number. All three transfer beautifully to a 50-person company — in fact, they are easier with five people in the room than with five hundred.
The mid-sized version: 90 minutes a month
Five inputs, prepared and distributed before the meeting — the meeting is for deciding, not for reading:
- Last month’s forecast scorecard. What did we predict, what happened, where were we systematically off? Starting here keeps everyone honest and makes the process self-correcting.
- Demand outlook by product family — a statistical baseline plus what sales actually knows (deals, churn, promotions), kept visibly separate from what sales hopes.
- Supply view — capacity, supplier constraints, critical purchase orders in flight.
- Inventory and backlog — where we are over, where we are under, in euros.
- Decision log review — what we decided last month, and whether it happened.
And three types of decisions, which are the actual output:
- Where do we bet? Which demand do we plan for, where do we deviate from the baseline, and who owns that deviation?
- What do we commit? Purchases, capacity, hiring — the irreversible stuff.
- What do we stop? Dead articles to clear, overstocks to sell down, products to stop protecting.
Roles are minimal but firm: one owner prepares the fact base (one person, not a committee), each function speaks to its own input, and the most senior person in the room breaks ties — with the decision written down. A one-line-per-decision log (what, who, by when) is the most underrated supply chain tool I know.
S&OE: the weekly sibling that protects the monthly meeting
Sales & Operations Execution is the short-horizon counterpart: twenty minutes, weekly, exceptions only. Which orders deviate from plan this week, what broke, who handles it.
Its real purpose is defensive. Without a weekly valve for operational firefighting, every fire invades the monthly meeting, and your S&OP quietly degenerates into a status call about last week’s crisis. The division of labor is simple: S&OE handles the next four weeks, so S&OP can handle the next four quarters.
How it fails — and the countermeasures
- It becomes a status meeting. Symptom: nice slides, no decision log. Countermeasure: if a month produces zero decisions, ask publicly whether the meeting was needed — the question alone fixes the next one.
- Data debates. Two numbers for the same thing meet in the room, and 40 minutes die arguing about whose export is right. Countermeasure: one fact base, one owner, distributed 48 hours before. Disputes about data happen before the meeting, never in it.
- Skipping busy months. The cadence is the product. A skipped month doesn’t pause the process — it tells everyone the process is optional. Busy months are precisely when trade-offs are biggest.
- Agenda sprawl. If it doesn’t fit in 90 minutes, the inputs weren’t prepared — fix the preparation, don’t extend the meeting.
A starter agenda
| Minutes | Topic |
|---|---|
| 0–10 | Forecast scorecard: what we said vs. what happened |
| 10–30 | Demand: outlook by family, changes since last month |
| 30–50 | Supply: constraints, capacity, critical purchase orders |
| 50–70 | Inventory & backlog: top overs and unders, in euros |
| 70–90 | Decisions: make them, log them, assign them, date them |
Takeaway — Run the monthly meeting three times before you judge it. The first one is awkward, the second one is useful, and by the third one it starts changing what people do between the meetings — which was the point all along.