5 ws and h

The 5 Ws and H is a questioning framework that uses six fundamental questions-Who, What, When, Where, Why, and How-to gather comprehensive information about a problem, situation, or opportunity. Originally from journalism, it's widely used in product development, problem-solving, and requirements gathering to ensure thorough understanding before jumping to solutions.

Why it matters

People naturally jump to solutions before fully understanding problems. A user reports a bug, and engineers start debugging before asking basic questions. A stakeholder requests a feature, and the team starts designing before understanding the underlying need.

The 5 Ws and H slows this down productively. By systematically asking each question, you surface information that might otherwise be missed. The framework is simple enough to remember and apply in any situation, from a quick conversation to a formal requirements session.

The six questions

Who identifies the people involved. Who experiences this problem? Who is affected by this decision? Who needs to be consulted? Who will use this feature? Understanding the "who" often reveals that different groups have different perspectives and needs.

What defines the situation itself. What exactly is happening? What is the problem or opportunity? What has been tried before? What are the constraints? Getting precise about "what" prevents misunderstanding and scope creep.

When establishes timing and frequency. When does this occur? When did it start? When is it most severe? When does a solution need to be in place? Temporal context often reveals patterns and urgency.

Where locates the issue. Where does this happen? In which product area? In which market or region? Where in the user's journey? Location can point toward causes and shape solutions.

Why seeks motivation and cause. Why is this a problem? Why does it matter? Why does it happen? Why hasn't it been solved already? The "why" questions often provide the most valuable insights.

How examines process and method. How does this currently work? How should it work? How will we know if we've succeeded? How will the solution be implemented? "How" bridges understanding and action.

Using the framework

The questions can be asked in any order, but starting with "what" often grounds the conversation before exploring other dimensions. "Why" typically deserves extra attention-it's where the deepest insights live.

Not every question applies equally to every situation. In a bug investigation, "when" and "where" might be critical. In strategic planning, "why" and "who" might matter more. Use the questions that fit the situation rather than mechanically asking all six.

The framework works for quick clarification or deep investigation. In a meeting, you might run through the questions in a few minutes. For a major initiative, each question might require substantial research.

In product work

Product managers use the 5 Ws and H constantly, even without naming the framework:

Understanding feature requests: Who asked for this? What exactly do they need? Why do they need it? When do they need it? How are they working around it today?

Bug triage: Who is affected? What exactly happens? When does it occur? Where in the product? Why might this be happening? How can we reproduce it?

User research: Who are we studying? What do they need to accomplish? When do they do this task? Where are they when they do it? Why do they do it this way? How could it be better?

Defining requirements: Who will use this? What must it do? When must it be ready? Where does it fit in the product? Why is this the right solution? How will we measure success?

Avoiding common pitfalls

The questions are starting points, not limits. Follow interesting threads even if they don't fit neatly into one question. If a "who" answer reveals something important, explore it before moving on.

Don't accept surface-level answers. "Who uses this?" answered with "our customers" isn't useful. Push for specificity: which customers? In what role? Under what circumstances?

Beware of leading questions disguised as the 5 Ws. "Why don't users like this feature?" assumes they don't. "Do users like this feature, and why or why not?" is more neutral.

The framework is for gathering information, not for interrogating people. Ask questions with curiosity, not accusation. "When did this break?" sounds different than "When did you break this?"

Related frameworks

The 5 Ws and H complements other problem-solving approaches:

Five Whys goes deep on causation, asking "why" repeatedly to find root causes. The 5 Ws and H goes broad across dimensions.

Jobs to Be Done focuses specifically on what users are trying to accomplish and why. It's a more structured approach to the "who/what/why" questions.

Root Cause Analysis uses the 5 Ws and H as an input to systematic problem investigation.

The frameworks aren't competing-they serve different purposes and can be used together.

Simplicity as strength

The 5 Ws and H has endured because it's simple enough to use in the moment. You don't need special training, templates, or tools. The questions are intuitive and memorable.

This simplicity makes it practical for everyday use. Before committing to a solution, pause and ask: Do I understand the who, what, when, where, why, and how? If not, gather that information first.

Klero helps answer the 5 Ws by organizing customer feedback so you can see who is requesting features, what they need, when they need it, why it matters to them, and how they describe the problem. This context makes the framework's questions answerable with real data rather than assumptions.