Validate the riskiest assumptions behind an idea before committing to a full production build. Find out whether the problem matters to the people you intend to serve, whether they can use the proposed solution, whether your team can build it, and whether the business case makes sense. The test can be small: a conversation, a clickable prototype, a technical spike, or pricing research. Validation informs what to build next; it cannot remove every uncertainty or guarantee success.
What validation can—and cannot—tell you
Product ideas carry different kinds of risk. A customer may have a genuine problem but dislike your proposed workflow. A prototype may be easy to use while depending on data or integrations your team cannot access. Even a solution people value and can use may not make economic sense for the business.
Atlassian’s product discovery guidance frames the questions as customer value, usability, technical feasibility, and business viability. SurveyMonkey’s guide, dated August 27, 2026, maps research methods to those questions. Evidence about one does not settle the others: an enthusiastic interview is not a usability test, and a waitlist click does not establish that a product can be built or sustained.
Validation is a way to reduce uncertainty enough to make a better next decision—not a certification that an idea will succeed. As Atlassian’s article by Megan Cook puts it, quoting Marty Cagan, discovery is meant “…to quickly separate the good ideas from the bad. The output of discovery is a validated product backlog.” The excerpt is attributed to Cagan’s book Inspired (Atlassian’s product discovery guide).
#1 Best Overall
Start with the problem, not the pitch
Write down who encounters the problem, when it happens, and what they currently do about it. Look for concrete behavior: workarounds, repeated complaints, abandoned tasks, support requests, or patterns in product usage. Customer conversations, feedback, and usage evidence can reveal needs before the team settles on a particular feature or product direction (Aha!’s guide to validating product ideas; Atlassian).
Separate what you know from what you are assuming. “People struggle to reconcile these records every week” is a claim to investigate; “they will pay for our dashboard” is a further assumption. A hypothetical expression of interest may help generate a question, but observed needs and current behavior offer a stronger starting point for deciding what to test.
Make the assumptions explicit and rank the risks
List the conditions that must hold for the idea to work. A short list often includes whether the intended customer has the problem, whether the proposed flow makes sense, whether the required technology and data are available, and whether the offering can support a viable business.
Choose the open assumption that is both consequential and uncertain. If getting the workflow wrong would force a major redesign, test the workflow before polishing the interface. If the idea depends on a difficult integration, ask engineering to investigate that dependency early. Aha! recommends focusing a proof of concept on the part of the experience carrying the most risk or uncertainty, and identifying assumptions and the evidence that would support moving forward.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Choose a test that matches the question
Pick a method according to the uncertainty you need to reduce. These methods produce different kinds of evidence; none proves an entire idea on its own.
| Question | Possible test | What the result speaks to |
|---|---|---|
| Do customers value this solution? | Customer interviews, surveys, or concept tests | Reported needs, reactions to a concept, or stated interest—not demonstrated usability or business viability |
| Can customers use it? | Interactive prototype and usability testing | Where people understand, hesitate, or get stuck in the tested flow |
| Can the team build it? | Engineering scoping or a focused technical proof of concept | Technical constraints such as integration, data access, and implementation risk |
| Does the business case work? | Concept and pricing research | Responses to a proposed offering or price—not proof of actual sales or sustainable economics |
This risk-to-method mapping follows SurveyMonkey’s product-development research guide and Aha!’s guidance. Consider the strength and type of evidence, test cost and reversibility, how realistic the test needs to be, and whether the result could change your next decision. A survey may efficiently explore a concept or price, for example, but it cannot show where a person gets stuck in a workflow.
Build only enough to learn
Match the realism of the test to the question. A sketch or low-fidelity clickable prototype may be enough to find out whether users can follow a basic sequence. If the interaction depends on realistic data or system behavior, a narrow proof of concept may be more informative. Neither requires building the complete product.
For a prototype test, observe what participants do as they try the task rather than relying only on a post-test opinion. Note the point where they pause, choose the wrong control, or ask for help. Use those observations to revise the flow and test again while changes remain inexpensive. Aha! recommends gathering feedback in context, iterating, and keeping a proof of concept focused on the highest-risk area.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a technical test, isolate the dependency that could invalidate the plan—such as whether a necessary integration or data source is accessible—rather than implementing surrounding features. For demand or pricing questions, make the concept clear enough that people can respond to the same offer. The right test is the smallest one that yields evidence useful for the decision at hand.
Rank #4
Decide in advance what would change your mind
Before running a test, record what result would increase confidence, what would reveal a weakness, and what will remain unknown. Set a decision rule appropriate to the stakes and the test design; there is no universal interview count, survey sample size, or conversion threshold established by the cited guidance.
Afterward, compare the result with the assumption it was meant to test. Interview comments describe what people say; prototype observation shows behavior in the tested interaction; engineering scoping assesses technical constraints. Keep those evidence types distinct when deciding whether to proceed, revise, or stop.
- Proceed when the key evidence supports the direction and remaining uncertainty is acceptable for the next step.
- Revise and test again when evidence points to a fixable problem, such as a confusing flow or a mismatch between the concept and the need.
- Stop or reconsider when a critical assumption is contradicted or the cost of addressing the risk changes the case for the idea.
Validation does not answer every question. If important uncertainty remains, make the next test more targeted rather than treating a favorable signal as a blanket endorsement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
Keep discovery connected to delivery
Discovery helps a team decide what is worth building; delivery implements, tests, and ships it. They are connected activities, not a requirement to finish all research before writing any code. A focused technical spike can itself be part of learning, and evidence from implementation or use may send the team back to refine its assumptions. Atlassian and SurveyMonkey both describe discovery as connected to ongoing product work rather than a one-time gate (Atlassian; SurveyMonkey).
Scale the effort to the decision. A low-risk change may need only a quick check with users or existing feedback. A costly, hard-to-reverse product bet may justify multiple tests across customer value, usability, feasibility, and viability. The point is not to delay coding; it is to avoid spending heavily on an assumption that a smaller test could have challenged.
Further reading
For a fuller treatment of product discovery, Atlassian’s discussion names Marty Cagan’s Inspired: How to Create Tech Products Customers Love. Check the edition and availability where you buy books.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
