When a 120-person furniture maker told me they were losing a customer a month to delivery delays, my first instinct wasn’t to look at their software. We went to the machines: were the saws breaking, was the finishing line slow? Turns out the machines were fine. They were waiting for parts that sat three feet away from the assemblers for two days, because nobody knew they were overdue.
Promise a Date You Can Actually Hit
Their salespeople promised anything to win the order. The production manager found out about the date when the customer called to ask where it was. That’s not scheduling, that’s guessing. We mapped the actual flow during an ERP Consulting exercise — average 14 days in “in-process” inventory, but only 2.5 days of real work happened on each order.
The Whiteboard That Started the Fight
A simple whiteboard listing every open order, its promised date, and the current status exposed something uncomfortable. The sales team’s “urgent” orders were shoved ahead of planned work, which made the planned work late, which created more “urgent” orders. A hopeless spiral.
- Make every order wait a full 24 hours before it’s rushed into production
- Create one freeze zone: the schedule is locked unless the owner approves a change in writing
- Track how often a promise date actually gets kept
Weekends Without Panic Calls
Within two months, their on-time delivery jumped from 52% to 84%, and nobody’s phone rang on Saturday anymore. The first exercise in our ERP Consulting review was a simple schedule freeze — the same shared list for sales, production, and the owner.
Here’s the part people ignore: the schedule isn’t a production problem. It’s a business promise problem.
If you run any shop that makes or processes physical things, do one thing this week: write down your last five orders, the promised dates, and the real dates. The pattern will tell you everything.