Customer feedback playbooks
Turn customer reports into clear, comparable product decisions. Choose a scenario, then the decision you need to make.
Duplicate feedback requests
Several customers may describe the same problem with different words, channels, or levels of detail. Treat duplication as an evidence question so demand remains visible without counting one underlying issue multiple times.
Conflicting feedback requests
Customers can ask for opposite outcomes, expose different constraints, or describe different segments using the same feature name. Make the conflict explicit and segment the evidence before choosing a product direction.
Vague bug report
A report such as it is broken may signal a severe failure or a missing question. Turn vague language into a bounded observation, preserve what is known, and avoid manufacturing reproduction details or a cause.
High-volume low-impact feedback
A frequent request may describe a minor inconvenience, a duplicated workflow habit, or a noisy channel. Separate volume from harm so repeated low-impact friction receives a fair queue decision without crowding out severe failures.
Small cohort with severe pain
A small number of customers can experience a blocker, irreversible mistake, or high-cost workaround that broad demand counts miss. Make severity and affected context visible without exaggerating the size of the cohort.
Stale feedback requests
Old feedback can remain valid, become obsolete after product changes, or signal a recurring problem that never received a decision. Recheck evidence and current customer context before treating age as either proof of irrelevance or urgency.
Cross-channel duplicate feedback
The same request may arrive through support, in-product feedback, sales conversations, or operational channels. Reconcile cross-channel evidence without losing source-specific context, privacy boundaries, or the timing that explains urgency.
Missing reproduction details
A report may identify a real customer cost while omitting the steps needed to reproduce it. Preserve the observed outcome, request the smallest discriminating detail, and keep investigation scope bounded until the missing path is known.
Feedback prioritization disagreement
Teams may agree on the facts but disagree about queue position, severity, or strategic fit. Make the disagreement inspectable by separating evidence, assumptions, tradeoffs, and the decision rule used to resolve it.
Premature feedback closure
A request can be closed because a related change shipped, a reporter went quiet, or a workaround was found even though the original outcome remains uncertain. Verify closure against evidence and keep follow-up paths visible.