Problem Statement Framework

Why is Problem Formulation So Important?

Einstein once said: “If I had an hour to solve a problem, I would spend 55 minutes defining the problem and 5 minutes finding the solution.” This highlights a fundamental truth in innovation work:

• An unclear problem formulation leads to ineffective or misdirected solutions.
• Many teams jump too quickly to solutions without deeply understanding the problem.
• A well-defined problem statement creates focus and alignment within the team.
• The right formulation opens up opportunities for creativity and innovation.
• A clear problem description makes it easier to evaluate potential solutions.

When Should You Use This Tool?

• At the beginning of a project to create clear direction.
• When you have identified a customer problem but need to define it more clearly.
• When the team has different opinions about which problem you are trying to solve.
• When previous solution attempts have failed.
• When you need to communicate the problem to stakeholders.
• When you want to evaluate if a problem is worth solving.

Components of an Effective Problem Description

A powerful problem description includes the following key components:

1. Who

Core Question: Who experiences the problem? Aspects to define:

• Specific target audience or user segment
• Relevant characteristics and context
• Why this group is important

2. What

Core Question: What specific problem are they experiencing? Aspects to define:

• Concrete description of the problem
• Symptoms and consequences
• Frequency and severity

3. Where/When

Core Question: In what context and when does the problem occur? Aspects to define:

• Specific situations or environments
• Timing or triggers
• Recurring patterns

4. Why

Core Question: Why is this a problem worth solving? Aspects to define:

• Consequences for the user
• Business or societal impact
• Connection to larger goals or needs

5. Insights

Core Question: What insights do we have about the underlying causes? Aspects to define:

• Deeper causes beyond symptoms
• Patterns from user research
• Surprising or counterintuitive discoveries

How to Formulate an Effective Problem Description

Step 1: Gather Data and Insights

• Conduct customer interviews and observations
• Analyze quantitative data about the problem
• Identify patterns and recurring themes

Step 2: Define the Target Audience

• Specify who experiences the problem
• Focus on a specific user group
• Describe relevant characteristics and context

Step 3: Articulate the Problem

• Describe the problem concretely and specifically
• Quantify the problem when possible
• Avoid mixing in solutions in the description

Step 4: Set the Problem in Context

• Describe when and where the problem occurs
• Identify triggers and situations
• Explain relevant circumstances

Step 5: Explain the Consequences

• Articulate why the problem is important to solve
• Describe the consequences for the user
• Connect to business goals or societal benefits

Step 6: Include Key Insights

• Add insights about underlying causes
• Include surprising discoveries
• Share relevant quotes from users

Step 7: Validate and Refine

• Test the problem description with users
• Ensure it resonates with the target group
• Refine based on feedback

Formats for Problem Descriptions

Standard Format

“[Target audience] experiences [problem] when [context], which leads to [consequences]. We have discovered that [insight].”

“How might we” Format

Reformulate the problem into an opportunity question: “How can we help [target audience] achieve [desired outcome] in [context] without [current obstacle]?”

POV (Point of View) Format

“[User] needs [need] because [insight].”

Criteria for an Effective Problem Description

A well-formulated problem description should be:

1. Specific

Focused on a clearly defined problem, not multiple problems at once.

2. User-Centered

Formulated from the user’s perspective, not the company’s or product’s.

3. Solution-Neutral

Describes the problem without suggesting specific solutions.

4. Actionable

Provides sufficient direction to generate meaningful solutions.

5. Validatable

Can be tested and validated with data and user feedback.

Common Mistakes to Avoid

1. Too Broad or Vague Formulation

An overly general problem description does not provide sufficient direction for solution development.

2. Embedded Solutions

Including hints of specific solutions limits creativity and innovation possibilities.

3. Focus on Symptoms Instead of Causes

Addressing superficial symptoms without understanding the underlying causes rarely leads to effective solutions.

4. Company-Centric Perspective

Formulating the problem from the company’s perspective instead of the user’s often leads to suboptimal solutions.

5. Assumptions Without Validation

Basing the problem description on assumptions instead of validated insights can lead the team in the wrong direction.

Resources for Further Study

Books

• “Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days” by Jake Knapp
• “Designing for Growth: A Design Thinking Tool Kit for Managers” by Jeanne Liedtka
• “The Design of Everyday Things” by Don Norman

Articles and Guides

• “The Art of Problem Framing”
• “From Problems to Opportunities: Reframing for Innovation”
• “Validating Problem Statements with User Research”

Videos

Var det här verktyget hjälpfullt?