“Your product isn’t failing. Your market might be. Or your organization might be. Knowing which one is the entire game.”
That sounds simple enough.
It isn’t.
When growth slows, customers drop off, or sales teams struggle to close deals, most companies immediately point at the product. The interface is confusing. The feature set is incomplete. The onboarding flow is too long. The website needs a redesign.
Have you heard someone say that? Have you said it yourself?
There’s no getting around it: product problems and market problems can look remarkably similar from inside the business. Both can produce disappointing revenue, weak adoption, frustrated teams, and a growing list of “urgent” improvements.
But they require entirely different responses.
Redesign the wrong thing, and you can spend a year making a market mismatch more attractive.
Table of Contents
- What is a product problem?
- What is a market problem?
- Why the difference matters
- When the problem is actually both
- How to diagnose the real problem
- The Decision Design lens
- Before you redesign, diagnose
What Is a Product Problem?
A product problem exists when the customer need is real, but your product is making it unnecessarily difficult to solve.
The market is there. The urgency is there. People want the outcome.
They just can’t reliably get there with what you’ve built.
Product problems often show up as:
- Confusing navigation
- Friction-heavy onboarding
- Missing capabilities
- Poor performance or reliability
- Inconsistent experiences across platforms
- Technical debt that slows every interaction
- Features that technically work but don’t match how people think
- A value proposition that disappears inside the interface
In other words, the product is failing in the solution space.
Customers may sign up, then abandon the experience. They may buy, then ask for refunds. They may tell your sales team, “This is exactly what we need,” followed immediately by, “But we can’t figure out how to use it.”
That distinction matters.
Frustration usually means someone cared enough to try.
A user who complains about a confusing workflow is giving you evidence that the underlying job matters. They are not indifferent. They are blocked.
And what blocks them may reveal more than a simple UX flaw.
As we’ve written about designing decisions instead of just designing logos, the experience customers encounter often reflects what is happening inside the organization. Fragmented products frequently point to fragmented ownership. A seven-step process may exist because seven teams are protecting seven different requirements.
The interface is where the organizational disagreement becomes visible.
What Is a Market Problem?
A market problem is different.
A market problem means the need is weak, the segment is wrong, the timing is off, or the category has changed around you. It is not primarily a question of whether your product is easy to use.
It is a question of whether enough people still want what you are offering : and whether they want it from you.
Market problems can come from:
- Solving a problem customers do not consider urgent
- Targeting buyers who do not have the budget or authority to act
- Choosing a segment that is too narrow, too broad, or poorly understood
- Entering a category after competitors have redefined customer expectations
- Building for a behavior that has changed
- Launching before the market is ready
- Launching after the market has moved on
- Communicating a benefit that does not resonate
No amount of button rearranging fixes this.
You can create a stunning interface for a product nobody needs. You can develop an elegant design system for a category customers have already abandoned. You can hire a top digital product design agency to polish every interaction : and still have a product-market problem.
A better-designed answer does not help if nobody is asking the question.
Market problems often produce indifference rather than frustration.
Prospects do not say, “I love the product, but the onboarding is too complicated.” They say, “This isn’t a priority.” Or they stop responding. Or they compare your offer to whatever they are already doing : including spreadsheets, email, manual work, or doing nothing at all.
According to Dan Olsen’s product-market fit framework, target customers and underserved needs form the foundation of product-market fit. Features and user experience come later.
Teams often rush to the top of the pyramid because features are easier to discuss than needs.
That is how “What should we build?” replaces “What problem is worth solving?”
Why the Difference Matters
The wrong diagnosis creates expensive momentum.
If you have a product problem but assume it is a market problem, you may abandon a valuable opportunity because customers are struggling to use what you built.
If you have a market problem but assume it is a product problem, you may keep adding features, redesigning screens, and optimizing conversion flows for an audience that is not interested.
Both paths are expensive.
The first wastes a good opportunity.
The second makes it harder to recognize that the opportunity is gone.
Here’s a practical way to think about the difference:
| Signal | Product problem | Market problem |
|---|---|---|
| Customer behavior | They try, use, complain, and drop off | They rarely try or engage |
| Customer emotion | Frustration or disappointment | Indifference or low urgency |
| Funnel pattern | Healthy interest, weak activation or retention | Weak interest from the start |
| Feedback | “This is hard to use” or “It’s missing something” | “We don’t need this right now” |
| Likely response | Improve the experience or solution | Reconsider the audience, need, timing, or position |
Of course, real businesses are rarely this tidy.
When the Problem Is Actually Both
Sometimes the market need is real and your product is still failing to meet it.
This is where many companies get stuck.
Customers have a legitimate problem, but your product is too difficult to adopt. Then the poor adoption makes the team question the market. The team changes the messaging. The new messaging attracts a different audience. That audience struggles with the product for entirely different reasons.
Now the company has created a diagnostic knot.
A strong market can be hidden behind a weak product.
Imagine a financial platform built for small businesses. The need is obvious: owners want better cash-flow visibility. But the product requires complicated setup, unclear integrations, and manual categorization.
Customers may want the outcome but reject the experience.
That is not proof that the market is wrong. It may be proof that the product is asking customers to do too much work before they receive value.
The reverse can also happen. A beautifully designed product may generate early interest because the category feels exciting, but retention falls once customers realize the underlying problem is not important enough to justify ongoing investment.
Pretty is not the same as useful.
How to Diagnose the Real Problem
You need three kinds of evidence: what the product says, what customers say, and what the data says.
1. Listen to what the product says
Watch where people struggle.
Do users abandon during onboarding? Do they repeatedly ask the same questions? Do they use workarounds? Do different customer groups navigate the product in completely different ways?
These are product signals.
Pay attention to friction, but do not treat every friction point as an isolated interface issue. A confusing workflow may indicate unclear ownership, competing requirements, or a product strategy that has never been resolved.
When ZIV helped redesign Lead Bank’s website, the work did not begin with colors and page layouts. It began with conversations with leadership, staff, and customers, followed by an audit of content, goals, and navigation. The result was a simpler experience because the team first clarified what the experience needed to accomplish. You can read the Lead Bank case study.
2. Listen to what customers say
Do not only ask whether customers like the product.
Ask what they were trying to accomplish before they found you. Ask what they do today. Ask what happens if they do nothing. Ask what has changed in their business, their category, or their expectations.
A customer saying, “I need this, but it is too hard to use” points toward a product problem.
A customer saying, “We do not really need this anymore” points toward a market problem.
The difference is not always in the words. It is in the level of urgency behind them.
3. Listen to what the data says
Data will not diagnose the problem for you, but it will tell you where to look.
Review the entire customer journey:
- Are people seeing your message but not clicking?
- Are they clicking but not signing up?
- Are they signing up but failing to reach the first moment of value?
- Are they activating but churning soon afterward?
- Are existing customers referring others?
- Are sales conversations increasing, or are you simply generating more unqualified attention?
Weak acquisition may indicate a market, positioning, or messaging problem.
Strong acquisition with weak activation suggests a product problem.
Strong activation with weak retention may indicate that the product’s promise is not being delivered over time : or that the original need is not important enough to sustain behavior.
Friction is usually a product signal. Indifference is usually a market signal.
Neither should be interpreted in isolation.
The Decision Design Lens
At ZIV, we approach this through Decision Design.
That means we do not start by asking, “What should the next screen look like?”
We start with a more useful question:
What decision is your customer failing to make?
Are they failing to decide that your product is relevant?
That may be a market or positioning problem.
Are they convinced it is relevant but unable to understand how it works?
That may be a product or experience problem.
Do they understand the value but hesitate because the category feels risky?
That may be a brand alignment problem.
Do they want to move forward but cannot get internal approval?
That may point to messaging, trust, or organizational friction.
The decision your customer cannot make helps identify the layer that is blocking progress.
This is why a creative consultancy needs more than visual talent. A brand strategy agency, customer experience design agency, or digital product design agency should be able to connect research, product behavior, brand expression, and organizational reality.
Otherwise, you are optimizing one layer while the real problem sits somewhere else.
Before You Redesign, Diagnose
A redesign can be exactly what your business needs.
It can also be a beautifully executed distraction.
Before you spend a year rebuilding your product, ask:
- Is the customer problem still urgent?
- Are we focused on the right segment?
- Do customers understand our value?
- Are they frustrated because the product is difficult : or indifferent because the need is weak?
- What does our data show at acquisition, activation, and retention?
- What organizational decisions are showing up as product friction?
The goal is not to defend the product or blame the market.
The goal is to tell the truth about what is blocking the customer’s decision.
You cannot design your way out of a market that does not care. And you cannot pivot away from a market that is waiting for a better product.
That is the difference.
At ZIV, we help leaders diagnose the layer that is creating friction : market, product, brand, organization, or some combination of all four : before investing in the wrong solution. Our approach brings together research, strategy, creativity, technology, and brand alignment to make the next decision clearer.
Want to know whether your business has a product problem, a market problem, or both?
Let us know. We can help you find the signal before you start redesigning the noise.
