agendIQ
TemplatesPricing
Sign inStart free

Product

  • Agenda builder
  • Live meetings
  • Video calls
  • Chair
  • Presentations
  • Integrations
  • Notes for everyone

Free tools

  • Agenda maker
  • Online timer
  • Wheel spinner
  • Team generator
  • Word cloud generator
  • AI quiz generator
  • Meeting cost calculator
  • Meeting games
  • Guides
  • All free tools
  • Templates
  • Pricing
Sign inStart free

Free forever · Pro free for 14 days. No card needed.

  1. Home/
  2. Templates/
  3. Workshops/
  4. 5 whys workshop

Workshop · Problem solving

5 whys workshop

Ask why, one level at a time: everyone answers from their phone, the room keeps the best-supported cause, adds evidence and ends with a fix.

45 minutes6 blocksFree Free template
Use this template

Free to use and to run live. No card needed.

Problem
What, where, when, how big
Why 1
Why did this happen?
Why 2
Why did that happen?
Why 3
And why was that?
Why 4
Keep going
Why 5
Something we can change?
Evidence
A record, a log, a measurement
Corrective action
What we change, who, by when
5 whys8 areas

In short

The 5 whys is a root cause technique: you ask 'why?' about a problem, then about each answer, until you reach a cause you can fix. This template runs it as a 45-minute group session with a guided board, answers from everyone's phone at each level, an evidence area and a corrective action with an owner.

Time
45 minutes
People
2 to 10
Board
Problem, 5 whys, evidence, action
Plan
Free
Made forAny teamManufacturingSoftware & productHealthcare· Updated October 4, 2026
Share

01Inside

What's inside

5 whys with 8 areas, and a 45-minute agenda that runs it.

“Answer the current why with one cause you could check”

  • ProblemWhat, where, when, how big
  • Why 1Why did this happen?
  • Why 2Why did that happen?
  • Why 3And why was that?
  • Why 4Keep going
  • Why 5Something we can change?
  • EvidenceA record, a log, a measurement
  • Corrective actionWhat we change, who, by when

The agenda

By the end of this meeting, we have a cause chain backed by evidence and one corrective action with an owner and a date.

45 min · 6 blocks, drawn to scale Fits exactly
  1. Ground rules: causes, not culprits, 3 minutes 3
  2. Agree the problem statement, 5 minutes 5
  3. Why, why, why: one level at a time, 20 minutesBrainstorm 20
  4. Read the chain backwards, 7 minutesDiscuss 7
  5. Corrective action, owner and date, 7 minutesDecide 7
  6. How we'll know it worked, 3 minutes 3
011233445 min
  1. +0′Ground rules: causes, not culpritsTip: If an answer names a person, ask what made that mistake easy to make. The process is the patient here, not the people.3 minInfo
  2. +3′Agree the problem statementTip: Specific and measurable: 'Line 2 stopped 4 times on Tuesday, losing 90 minutes', not 'the line is unreliable'. Replace with your own problem.5 minDecide
  3. +8′Why, why, why: one level at a timeTip: Everyone posts an answer to Why 1 in two minutes. Keep the best-supported answer, then ask why again. Add any proof to Evidence as you go. Stop when you reach something you can change, even if that's before five.20 minBrainstorm
  4. +28′Read the chain backwardsTip: Read it from the bottom up with 'therefore': 'there was no strainer, therefore scrap got into the pump, therefore...'. If a step doesn't follow, that why is wrong.7 minDiscuss
  5. +35′Corrective action, owner and dateTip: Fix the cause at the bottom of the chain. Add a quick containment step if the problem could happen again before the fix is in.7 minDecide
  6. +42′How we'll know it worked3 minWrap-up

02In the room

What happens when you run it

The shared screen, every phone and the summary afterwards, drawn from this template.

  • 5 whys notes
    Problem
    Why 1
    Why 2
    Why 3
    Why 4
    Why 5
    Evidence
    Corrective action

    On the shared screen

    A board the whole room fills

    Ideas land on the board from every phone, with no names on the notes. Then everyone dot-votes what matters most.

  • 10:02

    Answer the current why with one cause you could check

    ProblemWhy 1Why 2Why 3
    Your idea, in a sentence Add to Problem

    On every phone

    Ideas from every phone at once

    People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.

  • 5 whys

    Summary

    Sent

    In short

    Top notes

    • 7 dots
    • 5 dots

    Afterwards

    A summary that writes itself

    Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.

03How to run it

How to run this meeting, step by step

  1. 1

    Write a specific problem statement in the first area before anyone asks why.

  2. 2

    Ask each why out loud and give the room two minutes to answer from their phones. Keep the answer with the best evidence and move on.

  3. 3

    Stop when you reach a cause you can change; five is a guide, not a rule.

  4. 4

    Read the chain backwards with 'therefore' to test it, then agree one corrective action with an owner and a date.

04Questions

Questions people ask

Something else? Browse all workshops or open this one and change anything you like.

Still deciding?

Run your next meeting on it. Every new account gets Pro free for 14 days, no card.

  • Free forever after the trial
  • Your guests never sign up
  • Calls are never recorded
Start free
What is the 5 whys technique?

A simple root cause method from the Toyota Production System: ask why a problem happened, then why that happened, about five times, until you reach a cause you can fix.

What is a 5 whys example?

Taiichi Ohno's classic: a machine stopped because a fuse blew; the fuse blew because a bearing was poorly lubricated; the pump wasn't pumping enough; its shaft was worn; there was no strainer, so scrap got in. The fix is a strainer, not a new fuse.

Do you always have to ask why five times?

No. Stop when you reach a cause you can act on. Some problems need three whys, some need more than five.

Built from

The structure, wording and safety points in this template follow these published sources.

  • Atlassian Team Playbook: 5 whys analysisatlassian.com

Keep going

Goes well with

  • All workshops
  • Templates for any team
  • Timeline
    Factors
    Why? Why? Why?
    Root causes
    Actions
    Workshop·Any teamFree
    Root cause analysis workshopA blame-free RCA in 75 minutes: timeline, contributing factors, five whys on the top causes and actions ranked by how strongly they fix the system. 75 min
  • The effect
    People
    Methods
    Machines
    Materials
    Measurement
    Environment
    Drill down: why?
    Workshop·Any teamFree
    Fishbone diagramAn Ishikawa board with the six M categories, causes added from phones, dot voting on the likely ones and a five whys drill-down on the top three. 60 min
  • Plan and watch
    Act now
    Accept and monitor
    Reduce cheaply
    Workshop·Any teampro
    Risk register workshopCollect risks from the whole team, place them together on a likelihood and impact grid, then give each serious one a response, an owner and a review date. 60 min
  • Plan
    Do
    Act
    Check
    Workshop·ManufacturingFree
    PDCA cycle boardPlan, do, check, act for small improvement experiments: review last cycle's result, decide to adopt, adapt or abandon, and plan the next test. 45 min
  • Background
    Current condition
    Goal
    Root cause analysis
    Countermeasures
    Implementation plan
    Follow-up
    Workshop·Manufacturingpro
    A3 problem solvingThe A3 from background to follow-up on one board, filled by the owner and challenged by the team, with a mentor review agenda. 60 min
  • Strengths
    Weaknesses
    Opportunities
    Threats
    Workshop·Any teamFree
    SWOT analysisStrengths, weaknesses, opportunities and threats on a live board filled from phones with no names on the notes, then dot-voted and turned into TOWS strategies. 60 min
  • Who
    What
    Why
    Central topic
    How
    Where and when
    What if
    Workshop·Any teamFree
    Mind map boardA live mind map: the topic in the middle, six branches around it, and everyone adding ideas from their phone, then grouped into sub-branches. 40 min
  • Tasks and decisions
    Clear: one A
    Needs an owner
    Too many cooks
    Workshop·Any teamFree
    RACI chart workshopFill the RACI live at kickoff: tasks come in from phones, the room agrees one Accountable per row, and rows with no owner or too many cooks get flagged. 50 min

Open it, make it yours, run it live.

Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.

Use this template More workshops

Free forever · Pro free for 14 days · No card needed · Guests never sign up

agendIQ

Meetings are boring. Let's make them fun. Plan the agenda, run it live with a call that follows it, and leave with decisions.

Product

  • Plan a meeting
  • How it works
  • Video calls
  • Interactive presentations
  • Meeting timer
  • Pricing
  • Integrations
  • API and webhooks
  • Join with a code
  • Sign in

Templates

  • Presentation templates
  • Games & quizzes
  • Workshop templates
  • Meeting kits
  • Weekly team meeting agenda
  • Retrospective meeting agenda
  • 1:1 meeting agenda
  • All 507 templates

Free tools

  • AI agenda maker
  • Meeting cost calculator
  • Video meetings
  • All free tools
  • Online timer
  • Wheel spinner
  • Random team generator
  • Word cloud generator
  • AI quiz generator
  • Question bank

Guides

  • Meeting games & icebreakers
  • How to write a meeting agenda
  • How to run effective meetings
  • Meeting minutes & action items
  • AI meeting assistant

Compare

  • Mentimeter alternative
  • Slido alternative
  • Free video calls compared
  • Google Meet alternative
  • Zoom alternative
  • Miro alternative
  • Otter.ai alternative
  • Kahoot alternatives
  • Gamma alternative

Trust

  • Privacy Policy
  • Terms of Service
  • Calls are never recorded
  • Votes stay anonymous
  • Guests never need an account
© 2026 Agendiq30 sectors · 507 templates · Participants never need an account

5 whys workshopFree template

Use it