MethodsArticlesCompareAbout
MethodsArticlesCompareAbout
Methods5W1H Method
ParticipatoryProblem DiscoveryQualitative ResearchBeginner

5W1H Method

Frame design problems comprehensively by systematically answering six fundamental questions with your team.

The 5W1H method systematically breaks down design problems by answering Who, What, When, Where, Why, and How to build shared understanding.

Share
PeopleThe entire project team, including relevant stakeholders if possible.
InvolvementDirect User Involvement

The 5W1H method is a structured questioning framework that breaks any design problem into six fundamental dimensions: Who, What, When, Where, Why, and How. By systematically answering each question, teams build a shared, thorough understanding of the problem space before moving into solution mode. UX researchers, product managers, and design leads use this method at project kickoffs, during stakeholder workshops, and whenever a cross-functional group needs to align on scope, target users, and constraints. The framework originates from journalism and investigative reporting, where covering all six questions ensures no critical angle is missed. In a UX context, it prevents teams from fixating on a single aspect of the problem while neglecting others. The method requires no specialized tools or training, making it accessible to teams at any maturity level. Sessions typically run one to two hours and produce a comprehensive problem brief that guides subsequent research and design activities. The 5W1H is especially valuable when team members bring different assumptions to the table, as it surfaces and resolves those differences early.

WHEN TO USE
  • At project kickoff when the team needs a shared understanding of the problem before starting research or design.
  • When stakeholders from different departments bring conflicting assumptions that need structured resolution.
  • During requirements gathering to ensure all dimensions of the user experience are covered systematically.
  • When scoping a research study and you need to clearly define participants, context, timing, and methodology.
  • After a pivot or strategy change to re-examine the problem space from all six angles.
WHEN NOT TO USE
  • ×When the problem is already well-defined and the team needs to move directly into ideation or prototyping.
  • ×When you need deep quantitative analysis rather than a broad qualitative understanding of the problem space.
  • ×When working solo on a well-understood task where structured group facilitation adds unnecessary overhead.
  • ×When time pressure requires immediate action and there is no opportunity for a collaborative workshop session.
HOW TO RUN

Step-by-Step Process

01

What?

In this step, you clearly define the problem or the research question you aim to address. Specify what needs to be understood about user behavior, needs, and preferences. This is crucial for formulating an effective research strategy

02

Why?

Once you've defined the research question, you'll need to determine why this problem or question is essential to the user experience. Define the goals and objectives of your study and how they align with your overall business strategy. Understanding the 'Why' will help you build a solid foundation for your research.

03

Who?

Identify the target user group for your research, based on their demographics, interests, and behavior patterns. Create user personas to better empathize with and understand the end-users' needs. The 'Who' helps you develop a user-centric approach while conducting UX research.

04

When?

Determine the ideal timeframe to conduct your UX research. This should take account of factors like product lifecycle stages (e.g., design, development, launch), project deadlines, or key business events. The 'When' ensures that your research findings are timely and relevant.

05

Where?

Select the most suitable research location(s) based on your research question, target user group, and project constraints. Consider whether in-person or remote research methods are more appropriate based on resource availability, travel restrictions, or participant location preferences. The 'Where' step helps you optimize research logistics and efficiency.

06

How?

Choose the most suitable UX research method(s) for answering your research question, such as interviews, surveys, usability testing, or focus groups. Additionally, outline the procedures and tools you'll use to collect, analyze, and present your data. The 'How' ensures that your research process is well-defined and systematic.

EXPECTED OUTCOME

What to Expect

After completing a 5W1H session, the team will have a comprehensive problem brief that documents the target users (Who), the problem or opportunity (What), the context and environment (Where), the timing and triggers (When), the underlying motivation (Why), and the approach (How). This brief serves as a foundational reference throughout the project, ensuring all subsequent research, design, and development decisions are grounded in a shared understanding. The output typically includes a structured document or whiteboard artifact that can be shared with absent stakeholders, reducing the need for repeated alignment meetings later in the project.

PRO TIPS

Expert Advice

Encourage open and honest communication during discussions, creating a psychologically safe environment for all participants.

Prioritize facts and evidence over assumptions and feelings when addressing each of the six questions.

Recognize that some answers may require follow-up research or expert consultation; document these as open questions.

Timebox each question to prevent the group from spending disproportionate time on one area at the expense of others.

Use sticky notes or a digital whiteboard so each participant can contribute simultaneously before group discussion.

Start with 'What' and 'Why' to establish shared context before moving to 'Who', 'When', 'Where', and 'How'.

Revisit the 5W1H framework at project milestones to check whether initial assumptions still hold true.

Assign a facilitator who keeps the group focused on answering each question fully before moving to the next.

COMMON MISTAKES

Pitfalls to Avoid

Rushing Through Questions

Teams often speed through the six questions superficially. Allocate dedicated time for each question and use timeboxing to ensure depth without letting one question dominate the session.

Skipping the Why

The Why question is often treated as obvious and glossed over. Without a clear articulation of why the problem matters, teams risk building solutions that do not align with business goals or user needs.

No Follow-Up Action

Completing the 5W1H exercise without translating answers into actionable next steps wastes the effort. Always close the session by assigning owners, deadlines, and concrete follow-up tasks.

Excluding Key Stakeholders

Running the session without representation from engineering, business, or actual users leads to blind spots. Invite participants who can speak to all six dimensions with authority.

DELIVERABLES

What You'll Produce

Who Analysis

Documented target users, stakeholders, and their specific needs and expectations.

What Analysis

Defined tasks, user goals, features, and functions to address in the product.

Where Analysis

Mapped physical and virtual contexts where users will interact with the product.

When Analysis

Identified timing, frequency, and time-sensitive factors for user interactions.

Why Analysis

Documented motivations, objectives, and desired outcomes for users and business.

How Analysis

Established interaction flows, processes, and tools to support the experience.

FAQ

Frequently Asked Questions

METHOD DETAILS
Goal
Problem Discovery
Sub-category
Co-design sessions
Tags
5W1H methodsix questionsproblem framingproblem-solvingteam collaborationdesign thinkingproject kickoffstakeholder alignmentrequirements gatheringstructured inquiry
Related Topics
Design ThinkingProblem FramingStakeholder AlignmentRequirements GatheringLean UXUser-Centered Design
HISTORY

The 5W1H framework has roots in classical rhetoric, often attributed to Hermagoras of Temnos in the first century BCE, who outlined the essential elements of a complete argument. The approach was later adopted by journalists as the foundation of investigative reporting, ensuring every story answered Who, What, When, Where, Why, and How. In the mid-twentieth century, manufacturing and quality management adopted the framework, notably within Toyota's production system and Kaizen practices. The method entered the UX and product design field as design thinking and lean startup methodologies gained popularity in the 2000s. Practitioners recognized that the same structured questioning that makes journalism thorough could also prevent design teams from overlooking critical dimensions of a problem. Today, the 5W1H is a staple of project kickoffs, design workshops, and research planning sessions across industries.

SUITABLE FOR
  • Project kickoffs where cross-functional teams need to align on scope and goals
  • Framing ambiguous design problems before jumping into solution mode
  • Structuring stakeholder interviews to ensure comprehensive coverage
  • Requirements gathering sessions that need to capture all dimensions of a problem
  • Onboarding new team members into an existing project's problem space
  • Workshop facilitation when discussions tend to go off track without structure
  • Scoping research studies by clearly defining participants, context, and objectives
  • Strategic planning sessions that need to balance user needs with business constraints
RESOURCES
  • 5W+H = Knowledge to Design an Excellent User Experience You may have heard that to design a good user experience you first need to understand the users and their needs, but what exactly do you need to know? It comes...
  • How to use a 5W1H method to have more productive conversationsYou roam from one meeting room to another, sit on a tall office chair, lean forward, observe the group throwing thoughts and comments around. You try to put the ideas together in your mind, but the…
  • 5W1H : UX framework for lean product developmentJust like in writing a good story, 5W and 1H can guide us in creating a good user experience in a lean product development process. The order would differ slightly from the method used for writing, but essentially a good user experience is about a maximizing the chance of a good story to happen for
  • Brainstorm product features quickly using the 5W1H frameworkWhat if you or the design team you're in is asked to propose to a prospective client a new feature for their existing product. You've…
RELATED METHODS
  • 5 Whys
  • Behavioral Mapping
  • Bodystorming

93 methods. Step-by-step guides. No signup required.

ExploreAll MethodsArticlesCompare
PopularUser TestingCard SortingA/B TestingDesign Sprint
ResourcesAboutArticles & GuidesQuiz

2026 UXAtlas. 100% free. No signup required.

93 methods. Step-by-step guides. No signup required.

ExploreAll MethodsArticlesCompare
PopularUser TestingCard SortingA/B TestingDesign Sprint

2026 UXAtlas. 100% free. No signup required.