AI Blocks › Lead and manage people
Learn what really caused a failure, and fix it without overreacting
Describe a failure. Get a no-blame review plan, a checked chain of whys and sized fixes.
Find why it went wrong and fix it in proportion is a free AI workflow for the job "Lead and manage people". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Thinking: high
What it does
After a failure, teams tend to do one of two things. They patch what they saw and the same problem returns. Or they plan a rebuild that costs more than the failure did. A review that turns to blame makes both worse, because people start hiding problems. This workflow follows the five whys method as Eric Ries adapted it from Taiichi Ohno. It first sets up the review: a narrow target, everyone affected in the room, a moderator and rules that keep blame out. It then asks why until it reaches a process or training cause. Last, it makes a proportional investment: a small fix at every level for a small problem, a larger one for a larger problem, each with one owner, a date and a check.
You give it
- What went wrong, when, who noticed and how often it has happened
- The people and teams involved, and how much they trust one another (optional)
- Logs, messages or customer comments (optional)
- How much it hurt (customers affected, time or money lost, optional)
- Your notes (optional)
You get
- A class of failure, a trigger rule, who must attend, a moderator and ground rules
- A chain of whys with evidence at each level and a cause you can change
- One fix at each level, sized to the pain, with an owner, a date and a check
- A recurrence rule and a plain-words write-up for the team
Use it when
- Something broke or missed its date and you want to stop it happening again.
- Your last review ended with one person being blamed.
- Someone wants a full rebuild after a small failure.
Steps
- Five whys session planner: Describe a failure and your team. Get who must attend, a trigger rule, ground rules and a no-blame agenda.
- Root cause finder: Paste a problem that keeps coming back. Get a chain of whys checked against facts, the fixable cause and a prevention check.
- Problem response planner: Paste a chain of whys. Get a fix at each level, sized to the pain, with an owner, date and check.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Describe the failure in a few lines and name the people involved. Send the plan to attendees before the review.
- Share the write-up with everyone, and check each fix on its date.