Market-Product Fit
Define the market and its problem before forming the product hypothesis
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 97%
Market-product fit reverses the familiar solution-first interpretation of product-market fit. The team first defines the market, the people within it, the problem they experience, the category in which they seek solutions, and the motivation strong enough to produce action. Only then does it form a product hypothesis designed to fit those conditions. Customer conversations, support evidence, and observed behavior inform the problem definition before significant product investment. The output is not merely a product idea but an evidence-backed explanation of why a particular product should fit a clearly understood market. This sequence reduces the risk of treating an internally attractive concept as proof of external demand and keeps product development centered on the customer rather than the founder’s preferred solution.
Origin
Extracted from Marketing Against The Grain’s discussion of Brian Balfour’s four fits and his problem-first market-product fit model.
Core principles
- 01Start with the problem rather than the solution
- 02Define exactly who belongs to the market
- 03Understand why customers are motivated to act
- 04Place the product in a clear category
- 05Build the product hypothesis from customer evidence
How to run it
- 1
Define the Market
Specify who experiences the relevant situation and which people are genuinely in scope. Avoid broad labels that conceal meaningful differences among potential customers.
Pro tip Define the market tightly enough that you can recruit representative people for discovery.
Watch out A market described as everyone is too vague to guide product decisions.
- 2
Discover the Problem
Talk to customers and study their behavior to identify a recurring, consequential problem. Understand the journey that produces the problem rather than merely asking whether people like an idea.
Pro tip Ask how people currently handle the problem and what triggers them to seek an alternative.
Watch out Leading questions can manufacture apparent demand for a preferred solution.
- 3
Establish Motivation
Determine why customers care about solving the problem and what makes them willing to change behavior, spend money, or adopt a tool. Distinguish mild inconvenience from urgent demand.
Pro tip Look for existing workarounds, spending, or repeated effort as evidence of motivation.
Watch out Interest without meaningful motivation rarely sustains adoption.
- 4
Clarify the Category
Identify the category of tools or alternatives customers associate with the problem. This reveals expectations, competitors, and the mental shelf on which the product must fit.
Pro tip Use the language customers already use when describing alternatives.
Watch out Inventing a category too early may obscure how customers actually evaluate solutions.
- 5
Form the Product Hypothesis
Design a product concept around the validated market, problem, motivation, and category. State why the proposed product should fit those conditions.
Pro tip Keep the first hypothesis narrow enough to test cheaply.
Watch out Do not treat the hypothesis as validated merely because discovery preceded it.
- 6
Test the Fit
Put the proposed solution in front of the defined market and measure meaningful adoption or retention behavior. Feed the evidence back into both the product and problem definitions.
Pro tip Prioritize behavioral evidence over compliments or stated intent.
Watch out If the product fails, revisit the problem assumptions instead of adding features automatically.
In the wild
The episode describes Figma as spending years defining its problem before gaining traction. After traction emerged, founder Dylan Field continued talking with customers and reading help and support tickets to understand how the business should grow and scale.
→ Customer evidence informed both the initial product direction and later scaling decisions.
When evaluating a founder, Kieran asks how the founder arrived at the problem or solution. Strong founders can describe extensive conversations with prospective customers, the problems uncovered through those conversations, and how those findings shaped the product they began building.
→ The product thesis is grounded in discovered demand rather than retrofitted to an existing idea.
Common mistakes
Building the Solution First
Starting with a product and then searching for a problem encourages confirmation bias and may produce a solution nobody is motivated to adopt.
Defining the Market Broadly
An imprecise market definition makes discovery evidence inconsistent and prevents the team from knowing whose problem it is solving.
Mistaking Interest for Motivation
Customers may praise an idea without changing behavior or paying for it. Strong fit requires a meaningful reason to act.
Is it for you?
Best for
It is best for founders, investors, and product teams exploring a new product or major market expansion.
Not ideal for
It is not ideal for mature products making small, well-understood optimizations within an established market.
From the transcript
“Brian's argument is you should start with problem first, not solution first.”
“Clearly defined market, basically clearly define who is in the market, the category of tools that you belong to, the problem that you solve, and…”
“It's like truly understanding the problem and then building a product to solve that problem.”
From the episode
3 Frameworks to Transform Your Business