How to measure process cycle time
To measure process cycle time, record the workflow from start to finish and split the total into work time, the active steps, and wait time, the queues and handoffs in between, so you see where the days actually go. People underestimate cycle time because they only feel the active work, not the waiting. Ledgerium AI records the real process and separates work from wait on every step, so cycle time is measured from observed runs rather than estimated.
How to tell you have this problem
- A process takes days end to end but only minutes of actual work
- Nobody can say how much of the cycle is work versus waiting
- Estimates of how long the process takes are based on the active steps only
Why this happens
Cycle time gets underestimated because people report the active work and forget the waiting between steps. A task that takes ten minutes of work can take three days of cycle time, and without separating work from wait the queues that consume most of the elapsed time stay invisible.
The old way
Ask people how long the process takes and average their answers. They report the active work they remember and leave out the waiting, so the estimate captures a fraction of the real cycle time and the queues stay hidden.
With Ledgerium
Record the process from start to finish. Ledgerium measures each step and splits it into work time and wait time, so cycle time is the sum of observed activity and queues, and you can see which part, the work or the wait, drives the elapsed time.
Step-by-step
- 1
Record end to end
Capture the workflow from the first step to the last.
- 2
Split work from wait
Review how much of each step is active versus waiting.
- 3
Total the cycle time
Add work and wait across the steps to get the real cycle time.
- 4
Find the biggest wait
Identify the queue or handoff that adds the most elapsed time.
- 5
Re-record to track it
Capture again after a change to see cycle time move.
Common mistakes
- Reporting only the active work and ignoring the waiting
- Estimating cycle time from memory instead of measuring it
- Treating a fast task as a fast cycle when it waits in a queue
How Ledgerium captures this
1. Install the extension
Add the Ledgerium recorder to Chrome. No screenshots and no keystrokes are ever captured.
2. Record the real workflow
Perform the process once. Ledgerium captures the structured steps, timing, and system context.
3. Get the output
Receive an SOP, a process map, and a workflow intelligence report generated from the real work.
Worth knowing
Ledgerium measures the browser-based steps it records. Wait time inside physical or desktop-only steps needs separate observation to include in the cycle time.
Frequently asked questions
- Record the workflow from start to finish and split the total into work time and wait time. Cycle time is the sum of observed activity and queues, measured from real runs rather than estimated.
- Work time is the active steps someone performs; wait time is the queues and handoffs in between. Cycle time is both together, and the wait is usually the larger and more hidden part.
- Because people report the active work they remember and forget the waiting. A ten-minute task can carry days of cycle time once the queues between steps are counted.
- Usually the largest wait. The recording ranks where elapsed time accumulates, so you target the queue that adds the most rather than speeding up an already-fast active step.
- Re-record the process after a change and compare. Watching the work and wait split move shows whether the cycle time actually dropped and where the remaining delay sits.
Document the real process, not the remembered one
Record a workflow once and generate an SOP, a process map, and an improvement report from how the work actually happens.
Free plan includes 5 documented workflows per month. No screenshots ever captured.