Cycle time reduction is one of the most requested outcomes in process consulting. It is also one of the most misunderstood. The assumption is usually that the process needs to be speeded up. In most cases, the process does not need to be speeded up. It needs to have the waiting removed from it.

Distinguish between work time and wait time

In most business processes, the ratio of actual work time to total elapsed time is lower than people expect. A purchase order that takes four days to process might contain six hours of actual work. The remaining time is waiting: waiting for approval, waiting for a system to update, waiting in a queue. Cycle time reduction almost always means reducing wait time, not reducing work time. Identifying which is which is the first step.

Map where transactions queue

Every process has points where transactions accumulate and wait. These are usually approval gates, system interfaces, or handoff points between teams or departments. Mapping queue locations and measuring average queue time at each one tells you where to focus. In our experience, two or three queue points typically account for the majority of total cycle time. Fixing those two or three points produces most of the available improvement.

Examine batch processing habits

Many organisations process transactions in batches: approvals are reviewed once a day, invoices are processed on Tuesdays and Thursdays, reports are run weekly. Batching reduces the frequency of setup but increases average wait time for individual transactions. Reducing batch frequency, or eliminating batching entirely for high-priority transaction types, is often the fastest available cycle time reduction. It requires no system change and no capital investment.

Redesign approval gates before eliminating them

Approval gates exist for reasons. Before removing one, understand what risk it was designed to manage and whether that risk is still real. In many processes, approval gates were designed for a transaction volume or risk profile that no longer applies. The gate can often be replaced with a sampling regime or a threshold-based exception trigger, which preserves the risk management function while removing it from the critical path for the majority of transactions.

Measure after each change, not just at the end

Cycle time reduction projects that measure only at the end cannot tell you which change produced which result. Measure after each significant change. This tells you what is working, allows you to stop changes that are not producing results, and gives you a clear evidence base for the improvement. It also makes the final report considerably more credible to senior stakeholders.

The organisations that achieve lasting cycle time reductions are the ones that measure carefully, change one thing at a time, and do not declare victory until the new numbers have held for at least eight weeks.