1. A product succeeds because it solves a problem for people. This sounds very basic, but it is the single most important thing to understand about building good products.
2. The first step in building something new is understanding what problem you want to solve, and for whom. This should be crystal clear before you start thinking about any solutions.
3. The second question you should ask yourself is “why is this particular problem worth solving?”
4. If the audience you are building for is narrowly defined (and one that you are a part of), then you may be able to rely on your intuition to guide your product decision-making. If not, then you should rely on research and data to inform your decisions.
5. The problem you’re trying to solve should be easy to communicate in a sentence or two and resonate with someone from your target audience. If not, consider that a big red flag.
(1) The most common error I’ve seen among seed-stage startups is that they devote insufficient time to understanding the user’s problem before thinking about their proposed solution to it. The Job To Be Done framework prevents that error, because it forces you to research and define the user’s “Job To Be Done” in isolation from your proposed solution.
(2) “If the audience you are building for is narrowly defined (and one that you are a part of), then you may be able to rely on your intuition to guide your product decision-making.” See: The benefits and risks of founding a startup to satisfy a personal need.
(3) Cf. (i) What problem are you solving?, (ii) Four simple questions to help you get product-market fit, (iii) Documenting your product-market fit hypotheses.