User-Voice Research Pack

Serves: understand what users of a product or category actually experience and want — personas, jobs-to-be-done, requirements grounded in evidence rather than assumption.

Dimensions (priority order — prune to the decision):

1. Who they are & their jobs-to-be-done — the progress they're hiring the product to make
2. Complaint & workaround patterns — where current options fail them
3. Delight & switching triggers — why they stay, what made them move
4. Unmet needs & requests — what they ask for, and the deeper need under the ask
5. Their language — the words users say, versus the words vendors use

Craft (the non-obvious): mine 1–3★ reviews for pain and 5★ for why they stay; a workaround is unpriced demand — someone laboring around a gap has already voted; forums, Discord, and Reddit surface what surveys miss — people lie less when nobody's asking — but they over-sample the loud, so triangulate against reviews and any survey data; keep verbatim quotes, redacted — user words carry evidence paraphrase destroys, but usernames, handles, emails, and identifying links never enter the report or memlog; feature-request boards measure willingness to wait, not willingness to pay; distinguish loud power-users from the silent majority — count distinct voices, not thread length.

Freshness: sentiment ≤ 18 mo · complaints re-checked against the current version before citing.

Two-source classes: any prevalence claim ("most users…", "the top complaint is…") — two independent communities, not two threads in the same one.

Feeds (bmm): PRD (personas, requirements rationale) · UX research inputs · brief (problem) · product copy in the users' own language.