Measure actual elapsed time over 3-4 cycles before…
Before optimizing any workflow step, measure actual elapsed time across three to four execution cycles rather than relying on felt difficulty or estimated duration, because subjective experience systematically misidentifies bottlenecks.
When This Fires
- Before any attempt to optimize a personal or team workflow
- When you "know" which step is the bottleneck but haven't actually measured
- When workflow optimization efforts haven't produced the expected time savings
- Complements Optimize only the single slowest step — improvements… (optimize only the bottleneck) by ensuring you identify the actual bottleneck first
Common Failure Mode
Optimizing the most annoying step instead of the slowest step. The emotionally aversive step draws attention because it produces the most subjective suffering, but it may account for only 10% of elapsed time. Meanwhile, the genuine bottleneck (often something mundane like waiting for approvals, context-switching between tools, or manual data transfer) sits unoptimized because it doesn't feel like a problem.
The Protocol
(1) List all steps in your workflow. (2) For 3-4 execution cycles, record the start time and end time (wall clock) of each step. Include setup, transitions, and idle time within the step. (3) Calculate average elapsed time per step across cycles. (4) Rank steps by elapsed time. The longest step is your bottleneck — regardless of which step feels hardest. (5) Direct all optimization effort at the top-ranked step (Optimize only the single slowest step — improvements…). Do not optimize other steps until the bottleneck shifts. Re-measure after each optimization to verify the bottleneck has actually moved.