We all know examples of failed products and companies. The main reason is usually because they failed to meet customer needs better than the alternatives. Their focus was on the specific solution rather than the problem. This is also known as failing to find Product-Market Fit.
Product Managers, need to know which customer needs will their product solve. These unserved needs for a target customer are the market. They can target those needs but not change or control them. This is the problem space.
They best way to mitigate “solution pollution” is by mastering the problem space before anything else.
On this section
Problem Space vs. Solution Space
The problem space is where the needs of your target customer live. These can be anything from pain points, desires, or jobs-to-be-done. They define markets segments.
The solution space is any specific implementation to build a product. They can be any product or representation of a product, built for customer use.
Customers don’t care about your solution. They care about their problems - Dave McClure
Experience says customers are not likely to communicate their needs clearly. It’s not how the human brain works. We have a natural tendency to think in terms of solutions.
The job of Product Managers is to read between lines in the solution space to define the problem space.
The Product/Market Fit Pyramid
Marc Andreesen coined the term Product/Market Fit as “being in a good market with a product that can satisfy that market” in a well-known blog post.
But this doesn’t say much about how to get there. That’s why Dan Olsen created a framework called Product/Market Fit Pyramid.
This framework separates the key components in 5 layers. Each layer depends on the layer immediately beneath it. Each layer is a hypothesis you need to confirm before moving up:
- Target Customer: Who are they?
- Underserved Needs: What are their needs?
- Value Proposition: How the customer benefits and how our product is better.
- Feature Set: The functionality that supports those benefits.
- User Experience (UX): What the customer interacts with to get the benefits.
Fall in love with the problem not the solution, and the rest will follow - Uri Levine
The first three layers live in the problem space. The other two are what customers see and interact with and live in the solution space. The biggest pitfall is to get stuck in the later.
Product Managers need to make sure their work ties back to solving a real customer problem.
Assesing Product Opportunities (POA)
The purpose of a good product opportunity Assessment (POA) is to either:
- Prevent the company from wasting time and money
- Understand and define success
What is possible is always changing. That’s why opportunities for new products exist. Sometimes good opportunities are not ready for productization just yet.
This process help Product Managers to evaluate if an opportunity is promising or not. The real challenge is to do it quick and effective:
The 10 fundamental questions
- Exactly what problem will this solve? (value proposition)
- For whom do we solve that problem? (target market)
- How big is the opportunity? (market size)
- How will we measure success? (metrics/revenue strategy)
- What alternatives are out there now? (competitive landscape)
- Why are we best suited to pursue this? (our differentiator)
- Why now? (market window)
- How will we get this product to market? (go-to-market strategy)
- What factors are critical to success? (solution requirements)
- Given the above, what’s the recommendation? (go or no-go)
The first and the third questions are the hardest to answer. Product Managers need to have a compelling statement of the problem they are trying to solve and its size.
This is a first draft and a just a glance of what Product/Market Fit means. Take the time to learn from the resources below. We keep them up to date!
Do you have any feedback? Please, let us know here.