Product validation is not about collecting compliments for an idea. It is about finding credible evidence that a specific group of people has an important problem and will change its behavior to solve it.

Write Down the Assumptions

List what must be true about the customer, problem, proposed outcome, adoption path, and business model. Rank those assumptions by uncertainty and impact so the team tests the ones most likely to invalidate the idea first.

Study Existing Behavior

Ask people to walk through how they handle the problem today. Look for repeated work, improvised tools, delays, and money already being spent. Current behavior is stronger evidence than opinions about a hypothetical product.

Test the Outcome Without the Full Product

Use a prototype, concierge service, landing page, or manually delivered workflow to test whether users value the result. The experiment should isolate the core promise rather than imitate every detail of a finished application.

Ask for Meaningful Commitment

Useful signals require some cost: time, data, access to colleagues, a pilot agreement, or payment. A commitment demonstrates that the problem matters enough for a customer to act.

Turn Evidence Into a Build Decision

Summarize what was learned, which assumptions remain uncertain, and what the smallest useful release must prove next. Validation should narrow the product, not produce a larger list of requested features.