• Home
  • Introduction
    • Who is a Good Designer?
    • Types of Reasoning
    • What is Design Thinking?
  • Existing Models
    • Honeycomb/Double Diamond
  • New 'Synergy' Model
    • Synergy Model
  • Empathize
    • Introduction - Empathize
    • Listen to the Pain-points
    • Interview for Empathy
    • User, Journey & Use case
    • Process and Stakeholders
    • Pain-points to Problem
  • Define
    • Introduction - Define
    • Problems Categorization
    • Data Analysis
    • Statistical Analysis
    • Define Success
    • Define Problem Statement
  • Ideate
    • Introduction - Ideate
    • Brainstorming
    • Analogies & Benchmarking
    • Categorization of Ideas
    • Proposals & Evaluation
    • Business Case
  • Develop
    • Introduction - Develop
    • Development Planning
    • Product Roadmap
    • Design Principles
    • Rapid Prototyping
    • Prototype Plan & Build
    • Solution Build
    • Development Testing
    • Acceptance Testing
    • Product Release
  • Implement
    • Introduction - Implement
    • Prepare to Launch
    • Influencing the Decision
    • Crossing the Chasm
    • Solution Enhancement
  • Summary
  • More
    • Home
    • Introduction
      • Who is a Good Designer?
      • Types of Reasoning
      • What is Design Thinking?
    • Existing Models
      • Honeycomb/Double Diamond
    • New 'Synergy' Model
      • Synergy Model
    • Empathize
      • Introduction - Empathize
      • Listen to the Pain-points
      • Interview for Empathy
      • User, Journey & Use case
      • Process and Stakeholders
      • Pain-points to Problem
    • Define
      • Introduction - Define
      • Problems Categorization
      • Data Analysis
      • Statistical Analysis
      • Define Success
      • Define Problem Statement
    • Ideate
      • Introduction - Ideate
      • Brainstorming
      • Analogies & Benchmarking
      • Categorization of Ideas
      • Proposals & Evaluation
      • Business Case
    • Develop
      • Introduction - Develop
      • Development Planning
      • Product Roadmap
      • Design Principles
      • Rapid Prototyping
      • Prototype Plan & Build
      • Solution Build
      • Development Testing
      • Acceptance Testing
      • Product Release
    • Implement
      • Introduction - Implement
      • Prepare to Launch
      • Influencing the Decision
      • Crossing the Chasm
      • Solution Enhancement
    • Summary
  • Home
  • Introduction
    • Who is a Good Designer?
    • Types of Reasoning
    • What is Design Thinking?
  • Existing Models
    • Honeycomb/Double Diamond
  • New 'Synergy' Model
    • Synergy Model
  • Empathize
    • Introduction - Empathize
    • Listen to the Pain-points
    • Interview for Empathy
    • User, Journey & Use case
    • Process and Stakeholders
    • Pain-points to Problem
  • Define
    • Introduction - Define
    • Problems Categorization
    • Data Analysis
    • Statistical Analysis
    • Define Success
    • Define Problem Statement
  • Ideate
    • Introduction - Ideate
    • Brainstorming
    • Analogies & Benchmarking
    • Categorization of Ideas
    • Proposals & Evaluation
    • Business Case
  • Develop
    • Introduction - Develop
    • Development Planning
    • Product Roadmap
    • Design Principles
    • Rapid Prototyping
    • Prototype Plan & Build
    • Solution Build
    • Development Testing
    • Acceptance Testing
    • Product Release
  • Implement
    • Introduction - Implement
    • Prepare to Launch
    • Influencing the Decision
    • Crossing the Chasm
    • Solution Enhancement
  • Summary

Design Thinking

Design ThinkingDesign ThinkingDesign Thinking

define problem statement oR POINT-of-VIEW (POV)

Problem Statement

Problem statements are concise descriptions of the problems, in actionable manner, with clear articulation of the current and desired states that makes the guideline for creating user-centric solution.

The shortlisted problems along with respective Use cases and Success metrics are framed into actionable Problem statement(s). The objective of a Problem statement is to provide clear guardrails and direction to the team, in terms of "What do they need to solve and for Whom?" while ideating and evaluating multiple solutions (in the next phases). Therefore, we must not try to address too many problems in one problem statement. Categorize, prioritize and frame the problem statement accordingly.  We can have more than one Problem Statements at the end of the Define phase (however, it is recommended not to have more than 3, so as to retain the focus of team). The problem statement must not have any references to specific solutions.


Writing a Problem statement is a 4-step process:  

1. Put the problem in the Context: Explain 4Ws of the problem - What is the problem?  Who does it impact ? Where and When it impacts them ?

2. Explain the Relevance of the problem: Explain Why it is important to solve ? What pain-point it results into ? How does that pain-point effect User and Business?

3. Back-up your claims with Data-points: Provide evidence/data to back-up your claim.

4. Define the Desired state: Provide the desired state of the problem, after implementation of the solution in the form of SMART goals.


Depending on the scenario, the length of a Problem statement might be a few lines, a paragraph or half a page, but it must not be beyond that. 

How might we

HMW

How Might We (HMW) questions turns problems into opportunities for generative thinking and organizes how we think about the problem and possible solutions. It acts as seed to brainstorming.

How Might We (HMW) questions rephrase the Problem statement in the form of open-ended questions, to lead us to all the possible forms of solutions to the Problem statement(s). The solution of a Problem statement can be in form of Product, Service, Process, or Business Model, or mix of these. It is a 4-step process:


1. Start with a point-of-view/problem statement

2. Break down the POV/problem statement

3. Write as many How Might We's as you can

4: Decide on which to move forward

With this phase, the problem space gets concluded with Problem Statement(s) that needs to be addressed to solve User's Pain-point or meet User's need; and How Might We (HMW) questions to trigger actions for the next phase in 'Solution space'.

Next Page

Copyright © 2025 Design Thinking - All Rights Reserved.

Powered by

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept