Field notes · 2026-02-19
Treating support tickets as an adoption signal
Customer conversations often reveal why a feature is reached but not retained.
Usage events show where people clicked. Support tickets and chat transcripts show what they hoped would happen next.
During a feature adoption assessment, we tag tickets that mention the feature by name, by adjacent screens, or by the job the feature was meant to replace. Patterns emerge quickly: permission confusion, missing export formats, or unclear ownership of a shared setting.
Those themes should sit beside the funnel, not in a separate slide deck. A drop after the second step means more when you can quote the exact wording customers used that week.
Ask support leads for a short weekly digest during the first fortnight after ship. Five themes with example phrases are enough. Volume alone without language is a weak signal.
Closing the loop matters: when product changes address a theme, tell support what changed and when. Adoption work is shared work, not a private analytics exercise.