Prompt · Customer Success

Low Adoption Rescue

Diagnoses why a team isn't adopting and builds a re-engagement plan around their workflow.

Have ready: Provide seat activity, feature usage, and workflow description

Fill in · 7 fields

team namecompany nameXYlistdescribe how they work day-to-daywhat was tried

Your prompt

Diagnose low adoption for [team name] at [company name]. Facts: [X] of [Y] seats active in the last 30 days, the features they use are [list], the features they ignore are [list], their workflow is [describe how they work day-to-day], and past training attempts were [what was tried]. First, give me your best hypothesis for WHY adoption is low, with 2 alternative hypotheses ranked by likelihood. Then build a 30-day rescue plan: week-by-week actions, which specific workflow of theirs we should embed into first, who the internal mobilizer should be and how to recruit them, and what success looks like at day 30 (a number, not a feeling). End with the hard question: is this a training problem, a product-fit problem, or a priority problem?

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Customer Story Extractor

Cancellation Save Script

Feature Request Triage

Stakeholder Map Builder

Renewal Risk Email

Proactive Outage Notice