Building feels like progress
A product produces visible work: screens, features, demos and release dates. Problem research produces uncertainty, inconvenient contradictions and decisions to remove scope. That makes building emotionally easier even when it is economically more expensive.
The danger is not early building itself. It is using construction to avoid the question that could make the construction unnecessary.
Ask for behaviour before reassurance
Customer interviews can reveal context, alternatives and language. Observation can expose workarounds. A manual service can test whether an outcome is valuable. A prototype can test comprehension. A landing page or appropriately disclosed pre-order can test a stronger commitment.
None is definitive. The purpose is to buy a useful reduction in uncertainty before paying for a more expensive test.
Evidence & context: Strategyzer · Strategyzer
But sometimes you must build to learn
Yes. A technical risk may require a proof of concept, and customers may need to experience a new interaction before they can respond meaningfully. In some markets, a credible prototype is the only way to expose the real workflow.
The argument is not ‘never build early.’ It is ‘match the cost and fidelity of the test to the uncertainty.’ Do not build a complete system to answer a question that an interview, observation or manual pilot could answer.
Spend evidence in stages
Begin with the cheapest method capable of producing relevant evidence. Increase fidelity when the next uncertainty requires it. Before each step, write what result would change the decision; otherwise every outcome can be explained as encouragement.
The practical sequence is PROBLEM → CUSTOMER → EVIDENCE → SOLUTION. Read idea validation, then choose the smallest useful MVP.
Sources & further reading
- Business testing: is your hypothesis really validated?
Strategyzer. Practitioner guidance distinguishing directional discovery evidence from stronger evidence of real-world behaviour. Its evidence scale is a method, not a guarantee.
- Designing strong experiments
Strategyzer. Practitioner guidance on explicit hypotheses, relevant participants and well-designed artefacts. Experiment quality and interpretation still depend on context.
- Market research and competitive analysis
U.S. Small Business Administration. Official planning guidance on demand, market size, location, saturation and pricing. It is a research framework, not proof that a particular opportunity will succeed.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗