1 min lesson
Deliverable 2 - the stalled-rollout intervention
Use two rows in "Deliverable 2 - the stalled-rollout intervention" to state the practical decision rules.
Step 1 of 3
It's month four. Activation has stalled at 40% and depth-of-use is sliding. You have 20 minutes to diagnose from the data and prescribe - not to reach for “more training.”
The reflex answer to a stall is a blanket re-enablement push. That's the answer a panel is watching to see you avoid. A stalled account is almost never uniformly stalled. Segment first, then prescribe per segment.
Learn more
Full explanation
Where to Spend the Next Hour
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Map each segment by how hard it is to move against how much it returns - then triage, don't blanket.
For the dead team, resist guessing. Pull the telemetry and then talk to two or three engineers directly. A flatline usually has a specific cause: a security setting blocking the codebase index, a tech stack where the starter rules don't fit or a vocal senior engineer who tried it once and wrote it off.