The first failure mode is treating activity as evidence. More tickets, interviews, meetings, integrations, or dashboards can still leave a company no closer to a better decision.
This lane stays on evidence. The test is whether research changes a product decisions, pricing decisions, segment focus, sequencing calls, or investment decisions. It should not turn into empathy work, lifecycle messaging, or strategy theater.
The mistake in pre-interview research is creating a document that sounds complete without forcing a decision. Teams describe the market and list stakeholders, but leave the hard part untouched. The better move is naming the decision boundary: what are we choosing, what are we refusing, who owns it, and what evidence would change our mind?
An interview note is weak until tied to a decision. "Three customers mentioned reporting" is trivia. "Finance admins cannot approve renewals without exportable audit evidence, so the reporting bet moves ahead of dashboard cosmetics" is evidence that changes the plan.
Build a research question list small enough for planning or review meetings. Include the decision and owner; evidence and tradeoff; next checkpoint and the condition that would force a change. If the list exceeds two pages, it likely hides weak thinking behind completeness.
A useful review answers three questions: What did we learn? What will we stop doing? What decision changes now? If a meeting can't answer these, the work is background, not a tool for the operation.
Field test: pick one current initiative and rewrite it through this lens before adding new process. If the rewrite exposes no tradeoff, owner, or next decision, the team has found the real work.
This is part 2 of 10 in Discovery and Customer Research Without Theater.
