Don't Panic: Product Market Analysis

Product market analysis is the disciplined way to decide whether a product has a credible chance to create and capture value. This is less glamorous than announcing a large market, but it has the useful property of making the decision visible before a team spends months defending it.

Start with a decision. Enter a segment, prioritize a problem, test an idea, reposition, or stop. Research without that destination tends to become a carefully organized collection of interesting facts, which is a fine hobby but a poor operating system. Name the owner, the time horizon, and the evidence that would change the answer.

Next comes the segment: a customer type, problem, context, and buying conditions. Then draw the market boundary. Total market, serviceable market, and reachable market are planning boundaries, not numbers that emerge from a spreadsheet carrying a tiny flag. They depend on the product's scope, geography, channels, and constraints. Write those assumptions down.

Use two kinds of evidence. Secondary research provides market context, industry structure, and economic conditions. Direct research shows how a defined audience describes a problem, works today, and reacts to an offer. Neither gets the whole job. Public data cannot prove adoption of a new product, while one interview cannot estimate an entire market. This is annoying, but it is also why both exist.

The real competition is not a neat row of named rivals. It includes adjacent products, internal workarounds, service providers, and no action. For each alternative, ask what outcome it provides, what it costs to switch or operate, and what evidence supports the claim. A feature difference matters only when the segment values that difference enough to choose it.

Turn the arrangement into a hypothesis: for this segment, in this context, this product achieves an outcome better than the alternatives. List the assumptions underneath it. Test the one that is both uncertain and likely to change the decision. Keep facts, assumptions, interpretation, and recommendation separate, because otherwise they merge into a document that agrees with itself very confidently.

Read the Course tab for the full evidence path and the Cheatsheet when building the analysis packet. The Practice Reference gives a repeatable session, the Exercise asks for a decision packet, and Field Notes covers the places where a tidy analysis can quietly become a less tidy bet.