How to stop discovery from confirming an untested idea

The risk appears when a founder describes the product first, explains why it matters and then asks whether the listener would use it. A polite answer can sound like demand while revealing little about actual behaviour.

Write down what would disprove the assumption

Before recruitment, state the belief being tested and the evidence that would weaken it. If the assumption is that manual reporting delays decisions, a participant who completes the task reliably in minutes should affect the conclusion.

GOV.UK’s research-planning method encourages turning assumptions into research questions. A founder can add a decision rule: what will the team stop, change or investigate if the answer is unfavourable?

Keep the rule flexible enough to recognise new information, but do not rewrite it solely to preserve the original product.

Separate observations from interpretations

“Participant copied data between three systems” is an observation. “Participant needs our integration platform” is an interpretation. Store them separately so another person can challenge the leap.

An illustrative Indonesian startup might discover that copying occurs only during a monthly exception, while its proposed subscription assumes daily usage. The finding could suggest a smaller tool, different pricing or no viable product at all.

Contradictory interviews deserve attention. Investigate whether they reflect different segments, process maturity or genuine disagreement. An average summary may hide the distinction that determines the right customer.

Review the evidence with someone outside the pitch

Invite a colleague to examine notes before reading the sales presentation. Ask which claims the research supports and which remain assumptions. Protect participant confidentiality when sharing material.

The review should result in a changed question or a clearer experiment, not simply a better summary slide. Track decisions alongside findings so the team can see whether learning altered development.

At the research review, ask each observer to identify the strongest evidence against the preferred explanation. This is not a vote on whether the founder is right. It is a way to expose a missing segment, alternative cause or assumption that the next experiment should examine before development expands.

GAT’s guide to go-to-market strategy explains why market clarity matters. Discovery contributes to that clarity when the founder permits evidence to narrow ambition. The objective is not to win agreement in every conversation; it is to choose a problem worth solving.