Signals Over Quotes: Turning Research into Decisions
Teams love collecting quotes. Quotes feel like proof. But quotes are often the weakest form of evidence—because people explain themselves poorly, and because one strong quote can overpower the real pattern.
Senior PMs use quotes for color, but they decide based on signals.
A signal is something that indicates real behavior or risk:
- confusion (users misinterpret the UI)
- hesitation (they pause at decision points)
- workaround behavior (they invent a different flow)
- abandonment (they quit the task)
- trust gaps (“I’d need to verify this before sending”)
- repeated questions (same confusion across users)
How to turn research into decisions:
Step 1: Separate observation from interpretation
Bad synthesis: “Users didn’t like it.” Good synthesis:
- Observation: “3/5 users looked for filters in the left nav.”
- Interpretation: “Their mental model expects filters as global, not per-widget.” Now you have a design direction.
Step 2: Quantify lightweight patterns
You don’t need statistics; you need clarity:
- “4/6 users missed the primary action.”
- “5/6 asked the same question.” Patterns are more convincing than quotes.
Step 3: Tie signals to decisions
Every research output should end with:
- Decision: what changes
- Why: which signal drove it
- Tradeoff: what we accept
- Residual risk: what remains
- Next test: if needed
A strong line:
“Research doesn’t produce answers; it produces evidence. My job is to convert evidence into decisions with clear tradeoffs.”
Quotes still matter—use them to communicate empathy and urgency. But don’t let a quote become the decision.