Order-to-Cash Queue Diagnosis
A manufacturer ships about 1,200 orders per month over 21 working days. Order-to-cash has six stages: order entry, credit check, fulfillment, shipping, invoicing, and cash application. End-to-end average cycle time is 12.4 days against a 7-day target. Stage data show order entry takes 0.8 days of work, credit check averages 3.0 days of waiting plus 0.3 days of work, fulfillment 2.1 days, shipping 1.4 days, invoicing 3.3 days of waiting plus 0.5 days of work, and cash application 1.0 day. Pricing errors cause 18% of orders to be reworked, and 30% miss the daily invoice cutoff, adding at least one day. The credit team lead wants two more analysts because the queue is long. The CFO wants a quantified diagnosis before approving headcount or changing batch schedules.
1. Using the data, calculate the approximate value-added work, queue time, and work-in-process. What is the main constraint, and what additional data would you request before approving a fix?
Read the worked answer
Work = 0.8 + 0.3 + 2.1 + 1.4 + 0.5 + 1.0 = 6.1 days. Queue/wait = 3.0 + 3.3 = 6.3 days. Total = 12.4 days, which matches the reported cycle time. Throughput = 1,200 / 21 ≈ 57.1 orders per day. By Little's Law, average WIP ≈ 57.1 × 12.4 ≈ 708 orders. The largest single waits are invoicing at 3.3 days and credit check at 3.0 days; combined they account for 6.3 of the 12.4 days, so the main constraint is queueing around approval and invoicing, amplified by 18% rework and 30% cutoff misses. Before approving a fix, request arrival timestamps, staffing and utilization, batch release rules, rework causes and stage, order mix, customer service levels, and the distribution-not just the average-of queue times. Averages can hide a few very late orders and mask whether the problem is capacity, batching, or variability.
2. The credit team lead argues that adding two analysts will fix the delay. Evaluate this proposal using queuing and process logic.
Read the worked answer
Adding capacity only helps if credit is capacity-constrained and work arrives smoothly. The data show 3.0 days of waiting versus 0.3 days of work; that ratio often signals batching or a release policy, not insufficient analysts. If credit approves in twice-weekly batches, average wait approaches half the batch interval even at low utilization; two more analysts may reduce processing time but leave most of the 3-day wait intact. Also, 18% pricing rework and 30% invoice cutoff misses create additional load and variability. Before adding headcount, request arrival timestamps, approval batching rules, utilization, and rework causes. Test low-cost changes first: risk-based auto-approval for repeat customers, continuous release, delegated limits, and error-proof pricing. If utilization is above roughly 85% and arrivals are variable, adding capacity may still be justified-but as part of a package, not as the sole fix.
3. Design a measurement plan to prove improvement and avoid suboptimization.
Read the worked answer
Measure end-to-end, not only credit productivity. Primary: order-to-cash cycle time from order receipt to cash application, segmented by order type and rework status. Flow: WIP, queue time at credit and invoicing, throughput, and percent of orders missing invoice cutoff. Quality: first-pass yield, pricing-error rate, rework hours, credit decision accuracy, and bad-debt or compliance exceptions. Use a baseline of 12.4 days and 18% rework, and track distributions and control charts rather than monthly averages alone. Add customer-facing on-time delivery and invoice accuracy. Guardrails: credit risk tolerance, audit exceptions, and collections performance. Review weekly during pilot. This prevents the credit team from improving its local queue by pushing errors downstream or by approving risky customers just to clear WIP.