What is 5W2H: a complete guide with an example.

5W2H is a planning tool that organizes an action by answering seven questions: what, why, where, when, who, how, and how much. The name comes from the initials of What, Why, Where, When, Who, How, and How much. That's five questions that start with W and two that start with H, hence 5W2H.

Almost every meeting ends with someone saying "so let's improve this." A week later, nobody knows who agreed to do what, by when, or how much it costs. 5W2H exists to close that gap: it forces you to turn intention into action with an owner, a deadline, and a budget. This guide explains each question, compares it with 5W1H, walks through an annotated example, and shows how to connect the plan to PDCA and the Ishikawa diagram. If you just want the spreadsheet, go straight to the downloadable 5W2H template.

Where 5W2H comes from

5W2H is associated with quality management, where it's used as a support tool for building action plans, alongside others such as the PDCA cycle and the cause-and-effect diagram. It reached Brazil by that route and spread: today it's common in operations, sales, marketing, HR, and small projects. The questions themselves come from a classic investigative checklist, the same one journalists use to establish the facts of a story, and the cost question was added for use in action plans.

There are plenty of versions about who created it and when circulating online, and none of them is agreed upon. What matters is how it's used: seven questions, one table, one row per action.

The seven questions, one by one

What

This is the action, written as a verb plus the result: "install a barcode scanner at the shipping dock." Avoid topics ("logistics") and vague phrases ("improve communication"). A good rule of thumb: if you can't picture someone doing it on a Tuesday morning, it's not an action yet.

Why

The justification: the problem the action tackles or the result it aims for. This is the column that gets lost most often, because it seems obvious. But it's what lets you decide later what to cut when the deadline tightens: if an action doesn't have a strong "why," it's the first candidate to go. Avoid repeating the "what" in different words.

Where

The place of the action: a site, a department, a system, a channel. In companies with more than one address or more than one system, this column prevents the classic question "which branch is this for?" When the action is purely internal and there's no relevant place, you can write the department or system involved, but don't leave it blank: the question may reveal that the action spans more than one place.

When

The deadline, with a date. "By Oct 31" or "Oct 6 to Oct 10." Expressions like "soon," "next month," and "as soon as possible" are not deadlines. If the action has a distinct start and end, write both. If it depends on another action, write the condition ("after the budget is approved") and a cutoff date.

Who

The person responsible, by name. One person only. When you write "sales" or "the team," everyone assumes someone else will take care of it. If the action involves several people, name who answers for it and put the supporting people in the "how" column. If you need to make clear who executes, who approves, and who is only kept informed, the right tool is the RACI matrix.

How

The method: the main steps, the tool, the technique. This is where balance lives: too short ("do it") gives no guidance; too long turns the row into a manual. Two or three sentences are enough. When the "how" gets complicated, it's a sign the action should be split in two.

How much

The estimated cost, in reais, even when it's zero. A frequent trap is writing R$ 0 for everything done by the internal team, ignoring time. For big actions, it's worth estimating hours too. This number lets you add up the whole plan and take the total for approval.

5W2H vs. 5W1H: the difference

5W1H is the same checklist without the last question: what, why, where, when, who, and how. It works well for describing a situation or an action and is the original version of journalistic reporting. 5W2H adds cost, which makes it more useful in an action plan, where someone has to approve the spend and decide priority.

When to use 5W2H

• Action plan after a meeting. The most common case: the group decides to act and 5W2H records who does what.
• PDCA cycle. It's the natural way to detail the planning step (see below).
• Response to a nonconformity. Once you've found the cause, the corrective action plan is a 5W2H.
• Small project. A campaign, a layout change, opening a new branch: five to fifteen actions with an owner and a date.
• Post-incident. After a serious problem, the fix and prevention actions get an owner and a deadline.

It is not the best tool when actions depend on each other (step 3 only starts when step 2 ends). The table doesn't show the knock-on effect of a delay. In that case, combine the plan with a project schedule or a Gantt chart.

A complete, annotated example

Situation: an electrical supplies distributor in Joinville has 78% of orders delivered on time and wants to reach 92% by the end of November. The operations meeting identified the likely cause: manual checking at shipping creates errors and rework.

What this plan gets right

• The actions start by measuring. The first row keeps the team from buying a solution before confirming the problem.
• Every row has one person. No "the team," no "IT."
• The cost is added up. The plan's total is R$ 2,200, which makes approval quick.
• The last row closes the cycle. Without tracking the result, the plan becomes a list of completed actions, not of effects.

What could be better

The plan doesn't state the target number in each action, only in the initial situation. In larger plans, it's worth adding an extra "success metric" column (for example, "error-free checks on 95% of boxes"). And there's a hidden dependency: if the training includes using the scanners, it only makes sense after installation, and the plan's dates (training Oct 20 to Oct 24, installation by Oct 31) are in reverse order. That's the kind of problem a plain 5W2H doesn't show, but a schedule view makes obvious.

5W2H, PDCA, and Ishikawa: how the tools fit together

5W2H rarely works alone. It's the final step of a line of reasoning that starts with the problem.

From problem to plan

1. Define the problem with numbers. "78% of orders delivered on time, target 92%."
2. Find the causes. The Ishikawa diagram (or fishbone) organizes causes into categories such as method, labor, material, machine, measurement, and environment. The "five whys" dig deeper into the most likely one.
3. Pick the causes that weigh the most. Usually two or three.
4. Build the 5W2H. For each chosen cause, the actions that attack it.
5. Execute and verify. That's where PDCA comes in.

PDCA and where 5W2H fits

PDCA has four steps: Plan, Do, Check, and Act (standardizing what worked or correcting what didn't). 5W2H is the breakdown of the first one: the detailed "Plan." After the actions are carried out (Do), someone needs to check whether the number changed (Check) and decide what to do next (Act). The last row of the example above, "track on-time delivery for four weeks," is precisely the Check.

If the result didn't come, the cycle starts again: new causes, new plan. If it did, the change is standardized in a procedure or a work instruction, so it doesn't depend on the memory of whoever was there.

Common mistakes that kill the plan

1. Action too big. "Restructure logistics" doesn't fit in one row. Break it down until each row fits in two weeks and one person.
2. Collective owner. A department or team under "who" means nobody owns the action.
3. Vague deadline. Without a date, the action loses out to everything that has one.
4. Forgetting the "why." Without it, it's impossible to prioritize or cut.
5. Zero cost for everything. Almost every action consumes someone's hours. Even a rough estimate beats nothing.
6. A plan with no follow-up. The spreadsheet is finished in the meeting and forgotten the following week. Agree right then on who reviews it and when (weekly is ideal).
7. A plan that's too long. Past ten to fifteen rows, nobody reads it. Split by cause or by area.
8. Incompatible dates between actions. As in the example above: the dates need to respect the logical order.

How to track 5W2H without a spreadsheet

The weak point of a spreadsheet 5W2H is the day after: nothing alerts the owner that the deadline is approaching, and nothing shows the manager what's stalled. Someone has to remember to follow up, and that person is usually the busiest one.

The way out is to take the plan to where the work happens. If each row is a task with an assignee and a due date, the plan stops being a document and becomes work in progress. It's the same principle as any action plan: an action only exists once it shows up on the list of whoever will carry it out.

How to do 5W2H in Tasskee

1. Create a project for the action plan (or use an existing one).
2. Turn each row into a task. The "what" is the title; the "why," "where," and "how" go in the description; the "who" is the assignee; the "when" is the due date.
3. Record the "how much" in a custom currency field, so the cost is visible on each task. Custom fields are part of the Start plan or higher.
4. Turn on the automations for reminders before the deadline and alerts for stalled tasks: the plan starts following up on itself. Automations are available on all plans, with a monthly run limit.
5. Track it on the board in the weekly meeting: what moved, what got stuck, what's late. That's your PDCA Check.
6. Import from meeting minutes. If the plan came out of a meeting, the documents feature with AI turns the minutes into tasks (the AI works with your own provider's key).

If the plan has many chained steps, the same set of tasks can be viewed in a schedule with dependencies. And if your goal is bigger than an action plan, such as "double on-time delivery," it can become a key result of an OKR, with 5W2H as the plan that supports the number. To see the format applied in more situations, read the 5W2H examples.