When tool-wait exceeds 15% of workflow time in a frequent…

When This Fires

• After Before upgrading any tool, measure whether it's the actual…'s active-work vs. tool-wait measurement identifies high tool-wait percentages
• When a workflow feels sluggish but each individual step seems fast enough
• When deciding whether a tool upgrade is justified
• The final atom in the RL series: complements Before upgrading any tool, measure whether it's the actual… (measure before upgrading) with the specific threshold that justifies action

Common Failure Mode

Tolerance of accumulated micro-waits: "It only takes a second to load" — but it loads 100 times per day. The individual wait is below the attention threshold; the aggregate wait is a significant constraint.

The Protocol

(1) For your most frequently repeated workflows, measure tool-wait time as a percentage of total elapsed time (Before upgrading any tool, measure whether it's the actual…). (2) If tool-wait < 15% → the tool is not the constraint. Optimize elsewhere. (3) If tool-wait 15-30% → the tool is a moderate constraint. Investigate: can the wait be reduced through configuration, caching, or upgrading? If a simple fix exists, implement it. (4) If tool-wait > 30% → the tool is a severe constraint. Evaluate replacement tools (Define the specific job the tool must do in one sentence…, Limit tool candidates to 2-3 before evaluating — more…, Pick a tool with 5 minimum requirements, select the first…) with specific attention to speed in your high-frequency operations. (5) After any tool change, re-measure (Re-measure 2 weeks after any constraint fix) to verify the wait time reduction translated into throughput improvement.