Guide · Efficiency, margin and productivity
How to measure how long an order sits idle
A method to find where your orders wait, using the ones you've already delivered.
An order spends more time waiting than being worked on.
Days of work and of waiting at each step, in an example order
Quote
0.5 days work, 2.5 days waiting: 3 days
Approval
0.5 days work, 2 days waiting: 2.5 days
Credit
0.5 days work, 6 days waiting: 6.5 days
Production or picking
3 days work, 1.5 days waiting: 4.5 days
Invoicing
0.5 days work, 1.5 days waiting: 2 days
Delivery
2 days work, 1 days waiting: 3 days
The question
How long does an order take from the customer’s request to delivery? And how much of that time does it spend sitting, waiting on someone? The second question almost never has an answer, and that’s where the lead time is.
When to use it
When customers complain about lead times, when the team looks busy and everything still runs late, or before hiring people or buying a system to “move faster.”
Step by step
- Pick the orders. Take your last 20 or 30 delivered orders. A closed order has every date; an open one doesn’t yet.
- List the steps. Write down the path an order takes (intake, quote, approval, credit, production or picking, invoicing, delivery), using your team’s own names.
- Rebuild the dates. For each order, write down when it entered and left each step. Email, your system, WhatsApp and invoices usually have almost everything.
- Split work from waiting. For each step, estimate how much time someone actually worked on the order. The rest was waiting.
- Note who held it and how big it was. Record the person or department holding the order, and whether it was simple or complex.
- See where the waiting piles up. Rank the steps by total waiting time. Also check whether simple and complex orders follow the same path and the same people.
An example
At GE in Latin America, medical equipment took about 47 days to deliver. Following orders step by step showed that a US$ 20,000 order and a US$ 2 million order waited in the same queue, in the same shared departments: finance, credit, customer onboarding and proposals. Several departments checked the same things, in duplicate controls that added days. Splitting the flow by volume and complexity and cutting the duplicate checks brought delivery down to 4 days. The full case is in Problem reading 02.
The most common mistake
Asking instead of measuring. Each department knows its own work and doesn’t see the other queues, so each one points to a delay somewhere else. A spreadsheet with the dates ends that debate, because it shows where the order sat.
Do this tomorrow
Build a spreadsheet with one row per order and two columns per step, one for entry and one for exit. Fill it in with your last 5 delivered orders and see which step they sat in the longest.