--- name: diagnose-a-stalled-ai-rollout description: A named reason your team is not using the tool, tied to one rung of the adoption ladder, with the specific fix for that rung. license: MIT metadata: author: The Revenue AI Report version: 1.0.0 last-reviewed: 2026-09-04 source: https://www.therevenueaireport.com/skills/diagnose-a-stalled-ai-rollout --- # Diagnose Why an AI Rollout Did Not Stick A named reason your team is not using the tool, tied to one rung of the adoption ladder, with the specific fix for that rung. ## When to use this skill - Usage dropped after launch week and nobody can say why. - A leader is about to fund another training event to fix an adoption problem. - You need a defensible answer for the CRO or CEO on why the rollout is not working. ## Inputs to collect - What was rolled out, to whom, and on what date - What training, examples, and practice time people actually received - Current usage numbers, even rough ones - Two or three quotes from people who stopped using it ## Process 1. Collect the inputs above. Thin input produces a confident, wrong answer. 2. Learn: Someone explains it. First exposure to the content. Training deck, SOP, or launch email. 3. Observe: Watch what good looks like and what bad looks like. Without both, a person cannot tell where they stand. Examples library, recorded calls, pass and fail samples. 4. Practice: A safe place to try, fail, and try again. No stakes, no judgment, no live customer. Sandbox, role play, dry runs. 5. Apply: Real work, real deals, real risk. The first live rep. 6. Feedback: An honest read on the work, measured against a standard. Not how did it go. A measurement. 7. Teach: Teach it to someone else. This is the rung that locks it in. If a person can teach it, they understand it. 8. Write the verdict and the next action with an owner and a date. 9. Have one person who did the work review the output before you share it. ## Decision rules - Fix the lowest failing rung first. A higher rung cannot hold when the one under it is missing. - Practice means reps with no customer on the line. A live deal is not practice. - Feedback means measurement against a written standard, not a check-in conversation. - If people cannot teach it to a new hire, treat the skill as fragile even when usage looks fine. ## Output requirements - A six-row card: rung, evidence, pass or partial or missing. - One named root-cause rung with the reasoning. - A two-week fix with an owner, a deliverable, and a measurable check. ## Quality checks - Every rung verdict cites evidence you supplied, not general advice. - The fix targets one rung, not all six. - The measurable check can be read from a system you already have. ## Limitations - The ladder explains adoption, not whether the tool is any good. A bad tool fails every rung. - Usage data without quotes tends to produce a confident but shallow read. ## Example input Rolled out an AI call-summary tool to 40 reps on July 8 with one 60-minute session. No sandbox. No example library. Usage fell from 62 percent in week one to 11 percent by week five. Two reps said they did not know what a good summary looked like. ## Example output Root cause: Observe. Nobody saw a good and a bad summary, so Practice and Feedback had no standard to work against. Fix: publish six annotated examples, three pass and three fail, and score ten summaries per manager against them for two weeks. ## Review checklist - Did a manager who ran the rollout agree with the rung verdicts? - Is the fix small enough to finish in two weeks? - Is there a date to re-check usage? ## Works with - Playbook: Make conversation data do work (L3) (sales, L3) https://www.therevenueaireport.com/playbooks/conversation-data-to-work-l3 - Playbook: Turn dormant seats into one shipped workflow (L2) (enablement, L2) https://www.therevenueaireport.com/playbooks/dormant-seats-workflow-l2 - Playbook: The 30-day first workflow (L2) (general, L2) https://www.therevenueaireport.com/playbooks/first-workflow-30-day-l2 - Tool: Mindtickle Call AI (Sales & Revenue Intelligence) https://www.therevenueaireport.com/tools/mindtickle-call-ai - Tool: Cu (Meeting & Voice AI) https://www.therevenueaireport.com/tools/cu - Tool: Gong (Sales & Revenue Intelligence) https://www.therevenueaireport.com/tools/gong - Tool: Balto (Sales & Revenue Intelligence) https://www.therevenueaireport.com/tools/balto - Tool: Allego (Sales & Revenue Intelligence) https://www.therevenueaireport.com/tools/allego ## Rules of conduct - Write for a Director, VP, or operator. Short sentences. Explain uncommon terms. - Separate facts from assumptions. Never hide uncertainty. - Do not invent numbers, benchmarks, quotes, or customer names. - Do not send messages, change CRM records, or publish anything unless the user explicitly asks. - Flag when a decision needs human review. ## Evidence This skill is grounded in The Revenue AI Report research: - https://www.therevenueaireport.com/research/adoption-curve - https://www.therevenueaireport.com/research/what-works - Related analysis: https://www.therevenueaireport.com/blog/enablement-in-the-age-of-agents - Applies the framework: https://www.therevenueaireport.com/frameworks/lopaft Source and updates: https://www.therevenueaireport.com/skills/diagnose-a-stalled-ai-rollout