A high-demand product line was consistently failing to meet customer need -- not because of quality defects or lack of capacity, but because of how the production schedule was structured. The operation was running on a push-based, forecast-driven system that produced in large batches, creating significant peaks and valleys in product availability.
When the product was available, it sold well. When it was not -- which was increasingly often -- customers ordered from competitors. The sales team had been escalating availability concerns for months. The root cause had never been properly addressed.
A value stream mapping session quickly illustrated the core issue: the push system was creating inventory in the wrong places at the wrong times. Finished goods would build up when demand was low, then deplete rapidly when orders spiked. The replenishment signal was a weekly production schedule based on historical averages -- entirely disconnected from real-time demand.
Key findings from the VSM and flow analysis:
"The problem was not that we could not build the product. The problem was we were not building it at the right time, in the right quantity, in response to the right signal."
Analyzed 12 months of sales data to establish average daily demand, peak demand factors, and component lead times. Used this data to calculate bin sizes, safety stock levels, and replenishment trigger points.
Created a two-bin system where an empty bin automatically triggers a production order. Designed Kanban cards with clear information: part number, quantity, replenishment point, and destination.
Conducted hands-on training with production operators, warehouse staff, and supervisors. Ran a two-week parallel period before full cutover.
Tracked replenishment cycle times, stockout frequency, and finished goods turns weekly for the first 90 days. Adjusted bin quantities twice based on actual demand patterns.
-- Scott Hacker, MBA | Quality and CI Manager | Kansas City, MO