Extend a board that ends at Released, Deployed or Done with one adoption/learn lane, so a team stops treating deployment as success. Coaches where to put the lane and at what altitude, its entry and exit criteria, what telemetry has to exist first, how to limit it, how to backfill the work already closed as Done, and how to answer the overhead objection honestly. Use when features ship and nobody knows whether anyone uses them, when AI use cases are deployed and unused, or when a spec-driven board has a column for every step of the software and none for the human on the other end. For the numbers behind the limit this puts on the new state, use wip-limit-configuration-coach. If the epics themselves are written as output, run outcome-framing-coach first. If the question is broad — AI pilots with no clear return, or "where do we start" — run ai-activity-to-impact first; it finds the constraint and routes here.