Give each workflow change 3-5 executions before deciding…
Give each workflow change at least three to five executions before deciding whether to keep, modify, or revert it, to distinguish persistent effects from noise and prevent oscillation.
When This Fires
- After implementing a workflow change and evaluating whether it worked
- When tempted to revert a change after a single bad execution
- When workflow improvements seem to "not stick" — possibly reacting to noise
- Complements Exactly one improvement per execution cycle — not zero… (one improvement per cycle) with the evaluation patience threshold
Common Failure Mode
Impatient reversion: "I tried the new template and the first report took longer, so I reverted." The first execution with any change is often slower due to unfamiliarity. The second and third executions, with the learning curve past, might be significantly faster. Reverting after one data point discards changes that need a short learning period to show their value.
The Protocol
(1) After implementing a change (Exactly one improvement per execution cycle — not zero…), commit to running the workflow 3-5 times before evaluating. (2) Record the key metrics (Track workflow quality with tension-paired metrics…) for each execution. (3) After 3-5 executions, review the pattern: Consistent improvement (3+ of 5 executions show better metrics) → keep the change. Consistent degradation (3+ of 5 executions show worse metrics) → revert. Mixed results (roughly equal better/worse) → the change is likely neutral; keep it if it feels better, revert if it doesn't. (4) Do not make additional changes during the evaluation period — that would confound your experiment (Exactly one improvement per execution cycle — not zero…). (5) After concluding the evaluation, identify the next single improvement and restart the cycle.