kaizen:why

Guide iterative Five Whys analysis to identify root causes.

Updated Mar 4, 2026

Search Tags:#problem solving #root cause analysis #process improvement #kaizen #five whys #causal reasoning

Ready to run

npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-why

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen:why
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/kaizen/skills/why
Command: npx skills add https://github.com/dalawwa/labor-methods --skill kaizen-why

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative root-cause analysis is often stuck at symptoms. This skill guides teams through a structured Five Whys process to reveal underlying systemic issues.

Core Features & Use Cases

Guided Why chains (Why 1, Why 2, Why 3, etc.) to expose root causes.
Branching analysis to explore multiple potential causes and associated remedies.
Actionable outcomes: connects root causes to concrete improvement actions and preventive measures.
Suitable for product, operations, and process improvement contexts to reduce recurrence of issues.

Quick Start

State the issue clearly and begin the first Why iteration to uncover root causes.

Frequently Asked Questions about kaizen:why

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform root cause analysis when my team is stuck addressing symptoms?▼

Root cause analysis using the Five Whys technique iteratively asks why a problem occurs to move past symptoms and expose underlying systemic issues. This skill guides structured why-chains to reveal fundamental causes.

What is the best way to run a Five Whys analysis for process improvement?▼

Running a Five Whys analysis requires stating the issue clearly and iteratively asking why to drill down through each layer. The skill documents each step, explores branching causes, and surfaces actionable measures.

Can I use Five Whys for product and operations issues or is it only for manufacturing?▼

Five Whys is applicable across product, operations, quality, and business processes. The technique works wherever symptoms obscure underlying causes and long-term improvements are needed to reduce recurrence.

How do I connect root causes to concrete preventive actions after finding them?▼

Connecting root causes to preventive actions involves linking discovered fundamental issues to concrete improvement steps. The skill translates why-chain endpoints into actionable solutions and measures to stop recurrence.

What are the limitations of using Five Whys for causal reasoning in complex business processes?▼

Five Whys requires clear prompts and structured reasoning to guide users effectively. In complex scenarios, a single causal chain may miss multiple contributing factors, requiring branching analysis to explore potential causes.