Validating point of cause

You want to ensure that the market is big enough and that there are enough people willing to pay for your product or service.

Ideally, at the end of this exercise you should be able to understand your users’ interests and motivations better, and hone in on a small group of people who feel enough pain to buy your product.

This will help you learn how people do things, why them do them a certain way, and also what solutions or workarounds they are currently using to solve their problem.

And, in the remote case that you’ve been living under a rock and the whole lean startup movement somehow got past you, this post will try to bring you up to speed (and possibly, get you slightly ahead of the pack), provided you force yourself and your team to take action! Validating demand and validating the problem come first.

It involves constantly asking yourself the question: ‘Does this product really solve the problem, in the market we have identified? Product validation is more complicated and should be done via iteration.

Ideally, it looks something like this: Methodology, tools and techniques for validating the product or solution: You can use landing page tests to market and sell your product before it even exists.

Ideally, building and validating the product should go hand-in-hand and be an iterative process, with some amount of validated learning along the way (or at the very least, with every iteration you make).

This is the final step and comes after validating demand and validating the problem.


Leave a Reply