Chapter 19 / 20
19. When to Scale, Change, or Stop
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
Pilots are usually asked to produce a success story. The more valuable service may be to prevent a large mistake. If a triage assistant routes routine reports quickly but misses severe ones, stopping it is an outcome, not an embarrassment. If it helps only one task class, narrowing the workflow may be better than launching everywhere.
Return to the decision made before the pilot. Was the primary outcome customer resolution, reduced operating cost, a safer system, team capability, or individual growth? What was the baseline and comparison? What happened to the other three perspectives? An increase in local speed with a larger review queue is not an unambiguous gain. Nor is an unchanged incident count across a handful of changes proof that risk disappeared.
Choose among four verbs. Keep the bounded use when it meets the intended outcome and its guardrails. Change scope, permissions, process, or measurement when a fixable constraint limited it. Scale only when the result survives a harder comparison and the receiving teams can carry the workload. Stop when verification cost, harm, or weak demand defeats the case. State the decision owner, review date, and evidence that would reverse the decision.
Tools change, so a negative result from an old version does not settle the question forever; neither does a positive result from a different organization settle yours today. The DORA 2025 report describes AI as amplifying the surrounding system. That is a reason to revisit both the tool and the conditions that help it, not a reason to chase maximum autonomy as a maturity score.
At the junction: Ask a person who would bear the cost of scaling to make the strongest case against it. Write down what evidence would change their mind and what evidence would change yours. If neither can be specified, pause rather than treating momentum as proof.