Silent Pilot-to-Production Promotion
Anti-pattern: let a well-performing pilot quietly expand in scope until it is a de facto production decision system, while keeping the 'pilot' label so it never trips the go-live governance gate.
Problem
Go-live governance is triggered by a discrete event, the declared transition from trial to production, but a pilot that succeeds is never explicitly graduated, so that event never fires. Scope expands by small increments that each look too minor to warrant re-classification, and the cumulative result is a system making consequential production decisions under a label that exempts it from the very controls its real stakes demand. The gap between the formal status and the operational reality widens silently, and the longer it runs the more disruptive an honest re-classification becomes, so no one initiates it.
Solution
The anti-pattern is enacted by treating 'pilot' as an open-ended status rather than a time-boxed trial with an exit condition. A pilot that performs well is left running; new user groups and decision types are added one request at a time, each too small to seem to warrant re-classification; outputs that were once advisory begin to be acted on directly; and the formal status is never revisited, so the system grows into a production decision engine while still classified as an experiment exempt from go-live sign-off. The remedy is the inverse: scope every pilot with an explicit expiry and exit criteria, define objective triggers (user count, decision stakes, traffic share, irreversibility of outputs) that force a graduate-or-retire decision, and treat crossing any trigger as a go-live event that must clear production governance before the scope expansion is allowed to stand.
When to use
- Recognise this anti-pattern when a pilot that performs well has no expiry and no exit criteria, so it simply keeps running.
- Recognise it when scope grows by small increments, more users, more decision types, more direct action on outputs, each approved as a minor pilot tweak with no re-classification.
- Recognise it when the formal status is still 'pilot' while the operational reality is a consequential production decision system that no go-live gate has ever scrutinised.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.