Product-market fit is the state where your product so clearly solves a real problem for a specific group of users that they actively seek it out, return to it consistently, and tell others about it without prompting. Most founders treat finding it as a marketing or distribution challenge. It is a design challenge first.
How users experience your product directly determines whether they understand its value, whether they come back, and whether they tell others. A product solving the right problem with a confusing interface will fail to achieve PMF even if the market exists.
Users will not wait long enough, return frequently enough, or engage deeply enough to confirm that the product is worth using.
This is the connection most product advice ignores. PMF gets discussed in terms of positioning, audience selection, and growth channels. The design of the product itself — how clearly it communicates value, how fast it gets users to the core outcome, how it behaves when things go wrong — is rarely part of the PMF conversation. It should be the centre of it.
This guide draws on over a decade of leading product design across global startups and SaaS companies. It covers how design decisions directly accelerate or delay product-market fit, what the data actually shows about design and retention, and the specific design mistakes that cause founders to misread their PMF signal.
What this guide covers:
- Why product-market fit is a design problem, not just a market problem
- The specific design decisions that accelerate or delay PMF
- How to read PMF signals correctly when design is confounding your data
- The Sean Ellis test and what it does not tell you about design
- How to use design iteration to move from weak PMF signal to strong PMF signal
- How Ruhcraft approaches product design in the context of PMF validation
Why PMF Is a Design Problem
Marc Andreessen, who coined the term in 2007, defined product-market fit as “being in a good market with a product that can satisfy that market.”
That second part (a product that can satisfy) is almost entirely a design question.
Satisfying users requires that they understand what the product does within seconds. It requires that they can complete the core task without confusion. It requires that the experience of using the product is smooth enough that they associate it with positive outcomes rather than frustration.
All of those requirements are design requirements.
You can have the right product for the right market and still fail to achieve PMF because the design prevents users from experiencing the value. This happens constantly. The founders who get stuck below the PMF threshold are often not in the wrong market.
They are in the right market with a product that is too hard to understand or too slow to deliver its core value.
According to research published across multiple product analytics platforms, the median time to achieve PMF for B2B SaaS companies is 12 to 24 months.
The teams that find it in 3 to 6 months share one consistent characteristic: they invested heavily in user research and design validation before building, which means users experienced clear value faster because the product was designed around real user behaviour rather than founder assumptions.
The Most Direct Measure of PMF and What It Reveals About Design
Sean Ellis, who led early growth at Dropbox, Eventbrite, and LogMeIn, developed the most widely used PMF measurement in the industry.
The question is simple: “How would you feel if you could no longer use this product?”
Users respond with “Very disappointed,” “Somewhat disappointed,” or “Not disappointed.”
The threshold: 40% or more responding “Very disappointed” is the widely accepted signal of PMF.
Ellis tested this against hundreds of startups. Companies above 40% consistently achieved sustainable growth. Companies below 40% that tried to scale consistently burned through capital without gaining traction.
This question is one of the most useful tools in early-stage product development. It is also frequently misread in ways that mask design problems.
What the Sean Ellis Test Does Not Tell You
The test measures whether users would miss the product. It does not tell you why they would not miss it.
When your score is below 40%, there are three possible explanations.
The first: you are in the wrong market. The problem you are solving is not urgent enough for your target audience to care deeply.
The second: you are targeting the wrong users within the right market. You have the right product but you are measuring the wrong segment.
The third: you are in the right market targeting the right users, but the design prevents them from experiencing the core value clearly enough to feel dependent on it. They are somewhat interested but not hooked because the experience is not smooth enough to generate that level of reliance.
Most PMF advice focuses on the first two explanations. The third is at least as common, especially for technical founders who built the right thing but did not invest in how it is experienced.
Superhuman is the most instructive example. In 2017, their Sean Ellis score was 22%, well below the 40% threshold. Rahul Vohra did not pivot to a new market. He segmented the responses and found that a specific sub-group — mobile professionals sending over 100 emails per day — scored 58%. He then redesigned the product specifically for that group, removing everything that did not serve their experience. The score moved from 22% to above 40%, not through market repositioning but through product and design refinement focused on the right user segment.
The Five Design Decisions That Most Directly Affect PMF
These are not theoretical. They are the decisions that consistently determine whether users experience enough value to generate a strong PMF signal.
Decision 1: Time to Value
Time to value is how long it takes a new user to experience the core benefit of your product for the first time. This is the single most design-sensitive metric in early-stage products.
Research from multiple SaaS analytics platforms shows that users who reach their first moment of value within the first session have 50% higher 30-day retention than users who do not.
Design controls time to value almost entirely. The onboarding flow determines how many steps a user must complete before experiencing anything useful. The empty state design determines what a user sees before they have added any data. The information architecture determines how easily a user can find and complete the core task.
A product that delivers its value in the third session is asking users to trust it twice before they have experienced it once. Most users will not do this.
If your PMF signal is weak and your retention curve drops sharply in the first week, time to value is almost certainly the design problem to fix.
One metric that directly measures this is activation rate — the percentage of new users who complete a specific action that correlates with long-term retention. For Slack, this was teams exchanging 2,000 messages. For Dropbox, it was saving one file successfully. For most products, identifying and designing toward this activation moment is the highest-leverage design work available.
Decision 2: Onboarding Clarity
Onboarding is the most consequential design in any early-stage product. It is the moment that determines whether users invest in learning the product or decide it is not worth their time.
Research consistently shows that 60 to 70% of SaaS trial users never return after their first session. Most of that drop-off happens in the onboarding flow, not because the product lacks value, but because the onboarding failed to communicate it clearly and quickly.
The most common onboarding design mistakes that suppress PMF signals:
Asking for too much information before delivering value. Every field you require before a user can experience the product is a reason to leave. A startup that asked users to complete a 12-field profile before accessing the core feature reduced that requirement to 3 fields and improved week-1 retention by 47% based on pre/post data from their own analytics.
Not showing users what to do first. An empty dashboard with no guidance is one of the most reliable ways to lose a new user. The first action should be obvious, immediate, and rewarding.
Explaining features instead of demonstrating value. Feature tours describe what buttons do. Value onboarding shows users what they can accomplish. The difference is significant. Users need to experience the outcome, not hear about it.
Decision 3: Core Journey Friction
Every point of confusion in the core user journey costs you PMF signal.
When users encounter friction — a flow that is unclear, a button that does not do what they expected, an error message that does not explain what went wrong — they take one of two actions. They work around it if the value is obvious enough. Or they leave.
At the early stage, when the value has not yet been demonstrated clearly, most users choose the second option.
A useful way to quantify this: according to Nielsen Norman Group research, 5 usability tests surface 85% of critical usability issues. Running usability tests before launch is not a design best practice. It is a PMF acceleration strategy. Every friction point you find and fix in testing is a friction point that would have otherwise suppressed your PMF signal post-launch.
Products with 3 or more prototype iterations before launch are 50% less likely to fail, per research cited by Hootsuite’s product analytics team. That statistic is a design investment return, not a coincidence.
Decision 4: Empty State Design
Empty states appear when a user has signed up but has not yet created any data, completed any setup, or performed any action that the core feature requires to function.
For most products, the empty state is the most-seen screen in the entire product. It is also the most neglected design in most MVPs.
A well-designed empty state does four things:
- Confirms that the user is in the right place
- Shows what the product will look like when they have data
- Gives them a clear, specific first action
- Makes that action feel worth taking by previewing the outcome
A poorly designed empty state — which usually means a blank screen with a generic “No data yet” message — leaves the user with no reason to continue. It signals that the product is either unfinished or indifferent to new users.
Empty state quality is directly correlated with activation rate. Activation rate is directly correlated with PMF signal strength. This chain of causation makes empty state design one of the most impactful design investments in an early-stage product.
Decision 5: Error and Failure State Design
When something goes wrong in your product — a failed action, an invalid input, a network error, a missing permission — what happens?
If the answer is a generic error message, an unresponsive screen, or a broken flow with no recovery path, you have a design problem that is actively suppressing your PMF signal.
Users who hit an error and cannot recover do not think “the product had a bug.” They think “the product does not work.” The distinction matters because one is a technical problem and the other is a trust problem. Trust problems do not show up in error logs. They show up in churn data and in Sean Ellis scores that will not move above 40%.
Design all failure states explicitly:
- Validation errors: explain what is wrong and what the correct input should be
- Network failures: confirm the error and offer a clear retry path
- Permission failures: explain why access is blocked and what the user should do
- Empty results: distinguish between “no results exist” and “no results match your search”
How Design Iteration Moves the PMF Signal
The Superhuman example is the most-cited case of using product refinement to move a PMF score. But the mechanism is consistent across many products.
Here is how the process works in practice.
Step 1: Run the Sean Ellis test with your active users. Send it to users who have used the product at least twice in the past two weeks. A minimum of 40 responses gives you a directional signal.
Step 2: Segment the results. Do not look at the overall percentage first. Look at which user segments score highest and which score lowest. The segment with the highest “very disappointed” score is your real target user. The segment with the lowest score may be the wrong audience for this product.
Step 3: Interview users who said “very disappointed.” Ask them specifically what they would miss most. Their answers reveal which design elements are most central to the product’s core value. Protect and strengthen those elements.
Step 4: Interview users who said “not disappointed.” Ask them where they got confused, what they expected that they did not find, and what would have needed to be different for the product to be useful. Their answers almost always reveal specific design problems in the onboarding flow or core journey.
Step 5: Design and test against the specific friction points identified. Do not redesign the product. Fix the specific points of confusion identified by users who did not find value. Prototype the changes. Test them. Ship the validated improvements.
Step 6: Re-run the Sean Ellis test 60 days after shipping the design changes. Compare to the baseline. If the score has moved up, you have confirmed a design improvement with a measurable PMF impact. If it has not, the friction was not the primary cause and you need to look at the market and audience variables.
Teams that talk to users weekly find PMF 2 times faster than teams that talk to users monthly, per Startup Genome research. The constraint is not insight availability — users will always tell you what is not working. The constraint is the cadence of design iteration.
The PMF Metrics to Track Alongside the Sean Ellis Test
The Sean Ellis test gives you a directional signal. These quantitative metrics give you the precision to act on it.
Day 7 and Day 30 retention rate. If your retention curve flattens after the first week, users are finding ongoing value. If it continues declining toward zero, they are not. Benchmark for B2B SaaS: above 80% at 30 days indicates strong PMF alignment. Below 40% at 30 days is a clear signal that users are not finding enough value to return. For consumer products, Day 30 retention above 10% is considered a PMF signal.
Activation rate. The percentage of new users who complete the specific action correlated with long-term retention. If this is below 30%, your onboarding flow is losing users before they experience core value. This is a design problem with a design solution.
Time to first value. How many minutes or sessions does it take for a new user to complete the core journey for the first time? Every minute and every session added to this number reduces the probability of return.
Support ticket content. Before 100 users, read every support ticket manually. The language users use when they are confused tells you exactly where the design is failing. Tickets that describe confusion about navigation, feature location, or expected behaviour are direct design feedback.
Churn interview themes. When users cancel or go inactive, interview 5 of them per month. Ask specifically where the product stopped being useful. Answers that cluster around the same point in the flow indicate a design problem at that stage.
What Weak PMF Signal Usually Means for Design
Below 25% on the Sean Ellis test is a clear signal to stop and diagnose before continuing to build.
Most product advice at this point suggests pivoting the market or refining the audience. That may be correct. But before making that call, run this design audit first.
Can a stranger complete your core journey in under 5 minutes without any guidance? If not, the time-to-value problem is suppressing your signal regardless of market fit.
Does your onboarding ask for information before delivering value? Every pre-value step you can remove will increase activation rate, which directly improves PMF signal.
Does every error state explain what went wrong and how to fix it? Generic errors create distrust faster than almost any other design failure.
Does your empty state give users a clear first action? A blank screen after signup is a design failure that shows up as churn, not as “wrong market.”
Does the core value of your product require more than one session to be experienced? If yes, the product needs a design intervention before the PMF signal can be trusted.
If all five of these questions pass, and your Sean Ellis score is still below 40%, then the market or audience hypothesis needs to be re-examined. But check the design first. It is the faster and cheaper problem to fix.
FAQs on Product Market Fit Design
What is the connection between product-market fit and design?
Design directly controls how quickly users experience a product’s core value, how clearly they understand what to do next, and how smoothly they can complete the core journey. All of these factors affect whether users return, whether they tell others, and whether they would be disappointed without the product. A product solving the right problem with a confusing or slow design will consistently produce a weak PMF signal even in a strong market.
How do you know if your low PMF score is a design problem or a market problem?
Run a design audit first. If a stranger cannot complete your core journey without guidance in under 5 minutes, if your onboarding asks for information before delivering value, or if your error and empty states do not guide users clearly, the design is likely suppressing your PMF signal regardless of market fit. Fix those specific design problems and re-run the Sean Ellis test 60 days later. If the score moves, the problem was design. If it does not move, the problem is audience or market.
What is the Sean Ellis test and what threshold indicates product-market fit?
The Sean Ellis test asks users one question: “How would you feel if you could no longer use this product?” with options of “Very disappointed,” “Somewhat disappointed,” or “Not disappointed.” A score of 40% or more responding “Very disappointed” is the widely accepted threshold for PMF. Ellis developed this benchmark from testing across hundreds of startups. Companies above 40% achieved sustainable growth; those below 40% that attempted to scale consistently burned capital without gaining traction.
How does onboarding design affect product-market fit?
Onboarding determines how quickly new users reach the core value of the product. Research shows that 60 to 70% of SaaS trial users never return after their first session, and most of that drop-off happens during onboarding. Users who experience core value in their first session have significantly higher 30-day retention. Since PMF signals like the Sean Ellis test and retention curves are built on active user behaviour, poor onboarding suppresses both metrics by preventing users from ever experiencing the value they would otherwise rely on.
Can you improve product-market fit signal through design changes alone?
Yes, if the core problem and market are right. Superhuman moved from a Sean Ellis score of 22% to above 40% through product and design refinement focused on a specific user segment, without changing their core market. The mechanism is consistent: identify the users who score highest, understand what they value most, design to amplify that value and remove friction for that segment, and re-measure. Design iteration cannot create PMF in the wrong market. But it can reveal and unlock PMF that exists but is being obscured by a confusing or slow product experience.
The Bottom Line on Product Market Fit Design
Product-market fit is most commonly lost before it is found, not in the market, but in the product experience.
The right problem, the right market, and the right user segment are necessary conditions for PMF. They are not sufficient ones. The product must deliver its core value clearly, quickly, and reliably enough that users become dependent on it.
That dependence is created through design. Time to value, onboarding clarity, core journey friction, empty state quality, and error state design are not cosmetic concerns. They are the mechanisms through which users experience value or fail to.
Founders who treat PMF as a distribution and messaging problem miss the largest lever available to them. The product itself — how it behaves in the hands of a first-time user — is where PMF is won or lost most consistently.
Fix the design. Measure the signal. Iterate based on what users actually do, not what they say.
If you are working on a product where the PMF signal is weaker than expected and you want a design partner who has connected design decisions to growth outcomes across 10+ global products, get in touch at ruhcraft.com/contact-us/.