Hypothesis-driven design is a useful method to help us build the right product.
We can think of hypothesis as a design bet. For example, ‘I bet that if we move the account creation step to after the user has completed the order, we’ll see an increase in sales’.
Before we create our hypotheses, we should check the problem we’re solving really exists. Therefore, our board is split into 2 main parts:
Issues that we want to validate
Hypotheses that we want to test
By separating the things we know from the things we want to learn, we can make better design decisions.