Cutting Cycle Time: A One-Week Field Checklist Using Lean Six Sigma
When a process feels slow, the instinct is to ask people to work faster. Lean Six Sigma says the opposite: cycle time is mostly determined by how long work sits and waits, not by how quickly hands move. Coming out of the pandemic, with hybrid teams and supply that still arrived in fits and starts, the waiting got worse — approvals waited on someone at home, parts waited on a delayed shipment, handoffs waited on a reply. The good news is that waiting is visible and removable once you measure it honestly.
Cycle time is the elapsed time from when work starts to when it is delivered to the customer of that step. Within it, value-added time is the small fraction during which the product or service is actually being changed; everything else is delay, rework, or motion. A typical office or shop process is only a few percent value-added — which is exactly why there is so much room to cut without anyone working harder.
Measure the truth first (Define and Measure)
Name one process with a clear start and end, and one number that matters — for example, days from request received to request fulfilled.
Time real cases, not memories. Pull the last ten to twenty actual instances and record their true elapsed cycle time.
Walk the process and mark, at each step, the touch time (hands actually on the work) versus the wait time before it.
Compute the simple ratio of value-added time to total cycle time. The gap between them is your opportunity, and it is usually far larger than people expect.
Find and remove the waiting (Analyze and Improve)
Attack the longest wait, not the longest task. Sort your steps by wait time and start at the top. One stalled handoff often dwarfs every bit of hands-on work combined.
Cut the queue, not the worker. If items pile up before a step, the step is a bottleneck. Limit how much can wait there and feed it more evenly rather than pushing the person to rush.
Remove a handoff. Every transfer between people or systems adds a wait and a chance for error. Ask whether a step can be combined, automated, or done by the person before.
Replace batching with smaller pieces. Work held until "enough" accumulates waits the longest. Releasing in smaller, steadier amounts almost always shortens the end-to-end time.
Make the rule, not the hero, do the work. Replace "chase it manually" with a standard trigger — a clear definition of when an item is ready to pull — so flow does not depend on someone remembering.
Pilot on one lane before you scale. Test the change on a single product line, region, or team for a week, measure the same cycle-time number, and only then roll it out.
Hold the gain (Control)
Improvements decay unless someone watches them. Put the cycle-time number on a simple chart that the team sees daily, and agree on a threshold that triggers a conversation when it drifts back up. Write down the new standard so the next person inherits the improvement instead of the old habit. Done this way, a single week of honest measurement and targeted change can take double-digit days out of a process — not by anyone working faster, but by the work waiting less.
The discipline matters more than the tools. Follow the DMAIC order, trust the numbers over the anecdotes, and resist the urge to fix everything at once; the longest wait, removed, will teach you where the next one hides.
If you want a steady hand to find where time leaks out of your most important processes and to make the fixes stick, XNM's strategic advisory works alongside your team to do exactly that.