Navigating the Problem Space vs Solution Space Dilemma

Have you ever jumped to a solution before fully understanding the problem? You’re not alone. Consider the Hutzler 571. 

In 1989, an inventor named William Sheffield patented the Hutzler 571 Banana Slicer, a “tool which has a frame circumscribing an area into which a typical banana readily fits, and a plurality of spaced ribs or blades disposed transversely”. By all accounts, it worked reasonably well. But did this solution address a problem that people actually had? 

This scenario is more common than you think. Often referred to as ‘a solution looking for a problem’, this concept underscores the crucial distinction between problem spaces and solution spaces. The problem space encompasses all of the customer challenges and aspirations, while the solution space represents the products designed to address those needs. But just because you can do something doesn’t mean you should.

Albert Einstein once said, “If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem and five minutes thinking about solutions.” If he had been presented with the Hutzler 571 banana slicer, one imagines he might have asked, “Is there a pressing need for the ability to rapidly slice bananas that a reasonably sharp knife couldn’t accommodate?”

Gaining clarity on these concepts can significantly transform your innovation and product development approach. 

In this episode of the Product Management Insights podcast, Dan Olsen, author of The Lean Product Playbook, says “We need to go back a few steps because this brings up one of the most important concepts, which is problem space versus solution space”.

What is Problem Space?

The problem space is a crucial area of focus that encompasses the full range of challenges, pain points, and unmet needs experienced by customers. It’s not just about identifying obvious issues; it requires a deeper understanding of the context in which these problems arise including:

• Customer Challenges: Various obstacles and difficulties faced by customers
• Pain Points: Specific issues that cause frustration or dissatisfaction
• Unmet Needs: Gaps in the current market or product offerings
• Contextual Understanding: Circumstances surrounding the problem(s)
• Customer Aspirations: What customers hope to achieve or improve
• Emotional Factors: How feelings influence customer experiences and perceptions

By thoroughly investigating the problem space, businesses can ensure they address the root causes rather than merely treating symptoms.

To effectively map out the problem space, comprehensive user research is essential. Techniques such as interviews, focus groups, surveys, and observational studies can uncover valuable insights into the lives of your target audience. This process enables you to gather nuanced information about their behaviors, preferences, and unmet needs, allowing for a more refined understanding of the problem you need to solve.

It's also important to consider the broader context that affects the problem space, including market dynamics, technological changes, and socio-economic factors. By integrating these external elements into your analysis, you can gain a holistic view of the problem space to identify not only what the problems are, but also how they manifest and evolve within various environments. This foundational understanding equips you to innovate effectively and develop solutions that resonate with your customers.

Why Explore the Problem Space?

Spending time in the problem space allows you to fully understand user needs and challenges. This deep dive will often reveal hidden issues and opportunities that may be missed if you jump to solutions.

As Olsen says, “Most of the discussions you have with your team, stakeholders, sales, and clients are about features or solutions. If you take a step back and think about it, there’s a nuance which is, ‘Okay, you’re asking for feature X. Why are you asking for feature X?’”

This nuanced exploration of the problem space will not only help you identify a good solution, but will also have implications on how you market your solution.

Root Cause Analysis

To effectively solve a problem, it’s vital to explore underlying factors rather than merely addressing symptoms. Navigating between the problem space and solution space during the development process allows you to uncover fundamental issues, leading to more sustainable and impactful solutions. 

Understanding the dynamics at play will not only enhance problem-solving efforts but also empower your team to develop solutions that genuinely meet customer needs. Here are two tools you could use to get at the Root Cause Analysis

• The 5 Whys: An iterative questioning technique that uncovers the cause-and-effect relationships behind a problem.
  
  
• Fishbone Diagram: Also known as the Ishikawa or cause-and-effect diagram, it visually represents potential causes of a problem, aiding in systematic analysis.

By employing these tools, teams can foster a culture of thorough investigation that enhances the quality of solutions devised. Taking the time to conduct root cause analysis enables businesses to tackle the real issues, ultimately improving customer satisfaction and driving innovation.

Reframe Opportunities

Exploring the problem space allows teams to shift their perspectives and view challenges as potential avenues for innovation. This mindset is essential for creating successful products, as it involves integrating both problem space and solution space to develop optimal solutions for previously identified user problems. When problems are approached with an open mindset, they can transform into opportunities that drive creative solutions and enhance customer value.

Here are some key ways to reframe challenges into opportunities:

• Change Perspective: Adjusting your viewpoint can uncover hidden possibilities within challenges, fostering a culture of innovative thinking.
  
  
• Turn Problems into Opportunities: For instance, if usability issues arise, consider them a chance to enhance user experience, thereby boosting customer satisfaction and loyalty.
  
  
• Innovate Constantly: Embracing challenges allows exploration of fresh, transformative solutions that can create lasting value for the business.

This approach not only encourages a proactive stance towards problem-solving but also strengthens the overall effectiveness of product development initiatives. By cultivating a mindset that embraces challenges as opportunities, businesses are better positioned to identify innovative solutions that resonate with their customers and address their true needs.

Stakeholder Alignment and Collaboration

Product management is essential for successfully navigating the problem space and fostering a collaborative environment. It takes such a mile-up overview of a situation to avoid the trap of rushing to a solution, and many eyes are always better than two.

By engaging stakeholders, you can cultivate a shared understanding of critical issues, ensuring that everyone is on the same page regarding customer needs and the problem to be solved.

To achieve this alignment, consider implementing workshops where participants can collaborate, discuss, and reach consensus on priorities and objectives. Additionally, regular meetings can maintain transparency and facilitate ongoing communication, enabling teams to stay updated and focused on common goals.

By prioritizing stakeholder alignment and collaborative efforts, organizations will enhance their problem-solving capabilities, ultimately leading to innovative solutions that resonate with customers, effectively address actual needs, and achieve total buy-in from the entire team.

‍

Into the Solution Space

Once you’ve fully understood the problem space, it’s time to move into the solution space. The solution space includes specific implementations of products, their features, and design elements like mockups and wireframes. This phase involves generating, evaluating, and refining solutions for the identified problems. 

Ideation Sessions

Running brainstorming sessions is essential for product teams to generate a plethora of solution ideas. Brainstorming teams should take the time to explore user challenges deeply before jumping to solutions. These sessions should focus on creating an open and inclusive atmosphere where every participant feels encouraged to contribute without fear of judgment.

To maximize creativity and inspire out-of-the-box thinking, consider employing diverse ideation techniques such as SCAMPER (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse) or Mind Mapping.

Ideation Techniques

• SCAMPER: This is a powerful ideation technique used to stimulate creative thinking and generate innovative solutions. SCAMPER is an acronym that stands for seven different approaches designed to help teams examine an existing product, service, or problem from various perspectives – Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse. Participants can discover new opportunities for improvement and transformation by thoroughly exploring the problem space versus the solution space to identify genuine user needs and avoid the common pitfall of prematurely jumping to solutions.
  
  
• Mind Mapping: Mind mapping is not just a simple brainstorming tool; it serves as a dynamic framework for visually organizing information, fostering deeper understanding and connections between ideas. At its core, a mind map begins with a central theme or problem at the center, from which related concepts branch out in a structured yet flexible manner. This non-linear format encourages participants to explore associations between various ideas, leading to the identification of innovative solutions that may not have initially been apparent.
  
  
• Affinity Diagrams: Affinity diagrams are incredibly useful for organizing and visualizing a multitude of ideas, making sense of the chaos that often arises during brainstorming. By allowing team members to group and categorize ideas based on their natural relationships, this technique promotes a deeper understanding of patterns and overarching themes. This can be particularly beneficial in identifying common threads and converging on innovative solutions, as it aids in distilling vast amounts of information into manageable categories, enabling teams to focus on the most impactful areas for development.
  
  
• Storyboarding: This visual technique involves creating a series of illustrations or images that depict how a product or service will be used by customers over time. By mapping out the user experience in a narrative format, teams can identify key interactions, pain points, and opportunities for enhancement. Storyboarding encourages empathy as team members see the journey from the customer’s perspective, enabling them to create solutions that truly resonate with customer needs. This immersive approach to ideation can inspire innovative designs and solutions that might otherwise be overlooked in a purely analytical environment.

These methods help participants visualize connections, explore different perspectives, and push the boundaries of conventional thinking, which can lead to unexpected and innovative solutions. 

Furthermore, such comprehensive approaches will help you identify any unintended consequences or problems your solution might introduce. In his banana-slicing ideation process, Einstein might have asked, “Where amongst my clutter of kitchen gadgets am I supposed to store this device I will use only once in a blue moon?”

Prototyping and Testing

After identifying top ideas, the next step is to create quick prototypes to be tested with users to gather valuable feedback. One common mistake product managers make is rushing into solution creation without adequately exploring the problem space, which hinders the identification of the best solution. When we are too close to a problem and too invested in our solution, we lose perspective on how others might view them.

The solution space encompasses all products, features, and design elements that address customer needs. Seeing firsthand how customers interact with your solution will quickly show you how successfully you have solved a problem, or even if the problem needed a new solution in the first place. Prototypes serve as tangible representations of ideas, allowing teams to evaluate concepts in a real-world context.

It’s important to remember that these prototypes don’t need to be perfect; they should merely be functional enough to convey the concept. This iterative process aids in refining solutions based on user responses and allows for adjustments before full-scale launches. One example of such an approach is the Lean MVP model.

Tools such as Sketch or Figma are highly effective for rapid prototyping, making it easier to create and modify designs in response to feedback.

Feasibility Matrix Framework

Conducting a thorough feasibility analysis from the user's perspective is critical for ensuring that your proposed solutions are realistic, sustainable, and aligned with strategic goals. This step involves assessing the technical, financial, and operational viability of each idea to confirm they can be successfully implemented. It’s essential to consider potential risks and obstacles and strategize on how to mitigate them.

A feasibility matrix is an essential tool for evaluating the potential of various project ideas or solutions based on multiple criteria, ensuring they align with your strategic goals. This matrix helps streamline decision-making and allocate resources effectively while identifying and mitigating potential risks.

Following Olsen’s structured approach, the matrix is designed around an “Importance versus satisfaction” framework, laid out with the vertical (Y-axis) reflecting the importance of a need to the target customer, and the horizontal (X-axis) representing the satisfaction level with existing solutions.

From there, you can see the various quadrants:

• Low Importance: The lower two quadrants represent needs deemed low in importance, which should typically be avoided in focus areas (e.g. I don’t need to slice bananas very often).
  
  
• High Importance, High Satisfaction: The upper right quadrant identifies a competitive market where existing solutions already address important needs. Strategies for differentiation are crucial here (e.g. Does a sharp knife I already own not slice bananas?).
  
  
• High Importance, Low Satisfaction: The upper left quadrant highlights market opportunities, revealing significant needs that presently lack sufficient solutions, indicating the potential for innovation and development (e.g. We have found a consumer subset that needs to slice many bananas, and knives are too slow for their needs).

Olsen also introduces a quantitative approach termed the “Opportunity score,” which helps identify the most promising market opportunities by concentrating on high-importance needs that currently enjoy low customer satisfaction with existing solutions.

Collaboration with Cross-Functional Teams

Fostering collaboration with cross-functional teams enriches the solution space by allowing diverse perspectives to inform product development. Engage team members from various departments (such as marketing, sales, and customer support) to contribute their insights.

This holistic approach ensures that the solutions developed resonate with not only the technical and operational aspects but also align with market needs and customer expectations. By embracing collaborative efforts, organizations empower their teams to be agile and innovative, leading to well-rounded solutions that can efficiently address customer challenges.

By thoroughly exploring the solution space, businesses can generate effective, customer-centric solutions that not only resolve current challenges but also lay the foundation for future innovations. This proactive stance encourages a culture of creativity, collaboration, and continuous improvement, ultimately enhancing customer satisfaction and driving business success.

Balancing the Problem Space vs Solution Space

The Solution space is not without value. Consider Apple’s iPad. Upon its release, many people were not sure they needed a device that was somewhere between an iPhone and a laptop. But in the fullness of time, many uses were found for the solution and many users now find it indispensable. In this case, the solution found its problems, but that is often the exception rather than the rule.

To navigate the complexities of product development effectively, Olsen advocates for a balanced approach between problem and solution spaces, emphasizing the critical role of a product manager in this process. Olsen’s methodology begins with a deep understanding of the core issue rather than hastily moving to solutions. This ensures that teams are not only addressing the right problems but also tailoring their solutions to meet genuine customer needs.

By asking, “Why are you asking for feature X?”, Olsen encourages teams to reveal the real underlying problems to focus on what truly matters to the customer.

Summarizing the key strategies for balancing the Problem Space vs the Solution Space:

• Understand the Problem: Step back to identify and understand the underlying problem before proposing solutions.
  
  
• Engage with Customers: Validate the problem by talking to customers and using their language to ensure alignment.
  
  
• Focus on the Problem Space: Begin brainstorming sessions in the problem space to deeply explore issues before jumping to solutions.
  
  
• Learned Mindset: Cultivate a mindset that values both problem and solution spaces, a skill that product managers can instill in their teams.
  
  
• Balance Conversations: While solutions often dominate discussions, consciously explore and clarify the problem space to maintain balance.

By implementing these strategies, teams can ensure their products solve the right problems and resonate deeply with customer needs, ultimately creating greater value and satisfaction. This balanced approach is crucial for developing solutions that genuinely meet and exceed customer expectations, solve real problems, and don’t leave customers with another useless gadget cluttering up their kitchens.

‍