Author: Laura Klein
validating
what we think - we shouldn't ever assume we know what users want. Instead we do interviews and research to create hypothesis about and then test ituser-centered
with a relentless focus on learning from users.agile
with a focus on short feedback cycles on the product.data-driven
- it requires us to think about the metrics that drive business outcomes, measuring whether our ideas are moving those metrics in the right direction and then, understanding why.avoids waste
by helping identify what won't work before writing a single line of code and enables us to spend our time wisely.iterative
- we are constantly building small things, learning from them, generating new ideas and building the next version.You have markets
, problems
and products
Markets are the group you think will want to buy your product. Problems are the reason people are going to buy your product. Product is the way you'll solve the problem.
You need to check that a problem actually exists in your target market and is it large enough. Be specific about who your target market: e.g. women is a very broad market, teachers in low-income government schools of Haryana is much more specific. This makes it more likely to find a group of people with overlapping behaviours containing a pattern and a similar small problem you can solve, which will help you with your early decisions.
<aside> 💡 Overlapping behaviours > Pattern > Early Decisions
</aside>
This simply means - talking to your users.