• 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

5 Why's

5 Why’s

The 5 WHYs method is an iterative interrogative technique, pioneered at Toyota Motor Corporation in the 1930s, to explore the root cause underlying a specific pain-point/problem, by asking 'Why' five times.

In most cases, the observed pain point is only the symptom of a real problem that lies underneath. The 5 WHYs methodology is very simple, yet effective tool to get to the root cause of a problem. In this methodology, we ask "Why (so)?" multiple times to the user or whoever we are interviewing. Five times is a general thumb rule, but sometimes, we get to the root cause in lesser or more iteration. The idea is to keep asking "Why (so)?" question, till there is no further answer to it. The final answer is considered as the root cause of the observed pain-paint - the Problem that needs to be solved to address all other issues observed earlier.


5 WHYs methodology is used during Empathy interviews with the users, as well as interviews with stakeholders. The data is gathered for the root cause problem for further analysis in next phase. 

Cause and effect mapping (Fish-Bone or ISHIKAWA diagram)

Fish-bone Diagram

Cause-and-effect diagram, also knows as Fish-bone or Ishikawa diagram, organizes possible causes for a problem by graphically displaying them with increasing detail.

The cause-and-effect diagram is based on the assumption that an effect (mapped as head of the fish) is often caused by multiple factors (mapped as spines of the fish). Each of these causes is then mapped as effect of some other causes, iteratively, till no further branching is possible. 


Here, User's pain-point (effect) is analyzed for possible causes, which are again fragmented into sub-causes. The objective of this diagram is to map all the possible root causes (which we call as the Problems) of the observed pain-points of the user. The data is gathered for the root causes for further analysis in next phase. The cause-and-effect diagram can be used as an alternate to or in conjunction with 5 WHYs (each cause is detailed by asking 'Why' questions, five times).  


mind mapping

Mind Mapping

Mind mapping is another methodology to break-down problems into sub-problems, iteratively, till no further branch-out is possible.

For Mind mapping, we usually start in the middle of the page with the central theme (observed pain-point) and from there we work outward in all directions to create a growing diagram composed of keywords, phrases, concepts, facts and figures. It differs from the cause and effect diagram in a way that Mind Mapping also considers the associated factors (with possible correlation and no causal relationship) and uses more of creative (abductive) reasoning to possibly explain the problems, as it evolves into branches. The stronger the association, the nearer their branches are. 


The objective of this diagram is to map all the possible root causes (Problems), so as to gather further data and information on it for analysis in next phase. 

By end of this phase, the pain-points of user(s) in each Use case, are converted into number of Problems, which possibly are the root cause of the pain-point. For each problems, detailed data and information are available.

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