A prototype answers a question
Before building, we decide what we need to learn: whether a journey makes sense, data is sufficient or an integration works under real conditions.
Three ways to test
- Interface prototype: check the user journey before full implementation.
- Technical proof: test an integration, data source or infrastructure constraint.
- MVP: a limited version that solves one problem for a defined user group.
What remains after the experiment
Evidence for the hypothesis, observed limitations and a recommendation: continue, change direction or stop. Not every experiment needs to become a product.