Home / Insights / Planning

Planning · 3 min read

What a Planner Needs on Monday Morning

A planner starts the week with a short list of problems and about two hours to deal with them before the first meeting. Whatever the planning system shows at that moment decides whether it gets used. Most planning projects spend far too little time on this.

Why Most Dashboards Are Ignored

I have seen many planning dashboards built with care and then left alone after the first month. The reasons are nearly always the same. They show everything, so nothing stands out. They show data from last week, when the planner needs to act on this week. And they answer a manager’s question, not the planner’s.

A planner on Monday morning does not want a picture of the business. They want to know which five things will go wrong if they do nothing, and where to click to fix them.

Plan by Exception

Exception-based planning means the system does the routine work and only puts in front of the planner what needs a human decision. That sounds obvious. In practice it takes discipline to set up, because every exception has to be defined, tuned and owned.

On the programmes I have worked on, these design rules made the difference:

  • Every alert needs an action. If nobody knows what to do when it appears, delete it.
  • Rank alerts by impact. A shortage on a top customer next week comes before a small surplus in month three.
  • Tune the thresholds with the planners. Start strict, look at the alert list together after two weeks, and loosen what is noise.
  • Give each alert an owner. Shared alerts are nobody’s alerts.
  • Link straight to the fix. One click from the alert to the planning view where the planner can change the plan.
Screenshot to add
SAP IBP alert overview (Fiori): custom alerts for projected stock below safety stock and capacity overload, sorted by severity, with drill-down to the planning view

Few KPIs, Measured the Same Way Every Week

A planning team needs a handful of KPIs, not thirty. For most of the teams I work with, forecast accuracy or bias, service level, stock against target and plan adherence in the factory cover what matters. Pick the few that match your planning problem.

More important than which KPIs you pick is that the definition does not change. If forecast accuracy is calculated one way in demand review and another way in the monthly report, people stop trusting both. Write the definition down and keep it in one place.

Put It in a Rhythm

Alerts and KPIs only help when they feed a fixed rhythm. Daily, the planner works the exception list. Weekly, supply and demand planners meet to agree the short-term plan. Monthly, the S&OP cycle runs through demand review, supply review and a decision meeting with management.

Each meeting should see the same numbers the planner sees, cut to the right level. When the management meeting uses a different spreadsheet from the planning system, the system has already lost.

Test It on a Real Monday

Before go-live, sit next to a planner on a Monday morning with the new system. Do not demo. Let them work. Note where they hesitate, where they open Excel and where they ask a colleague. That one morning will tell you more about the design than any test script.

Zakaria Rziki is a partner at NES and an SAP supply chain solution architect. Ask him a question →

How Long Is Your Planners’ Alert List on a Monday?