An idea becomes easier to evaluate when it is expressed as a specific problem for a specific group of people. Product validation helps founders learn before committing to a large build. Every article here is meant to be used: a method to try, a question to ask before the next build or a decision to make with better evidence. The related pieces continue the same thread rather than repeating it.
Define the narrowest useful problem
Choose the user and situation where the need is clearest.
Identify the riskiest assumption
Decide what must be true for the product to be useful and find the simplest way to test it.
Build an MVP around learning
The first version should support a real learning goal rather than imitate every feature of a mature product.
Turn the idea into a useful test
Write down the audience, current behaviour and most uncertain assumption before choosing a solution. A small interview, workflow sketch or focused prototype can produce better evidence than a broad build with no clear learning objective.
Choose a connected next step
Use the related links to continue with student innovation, Buildfest, startup validation, technology experiments or the Venture Studio process. Each route adds context and provides a relevant way to discuss an idea with Vedspace Ventures.
