Back to Details

five-whys

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Five Whys - Root Cause Analysis

Five Whys - 根本原因分析

Systematic guide to uncovering root causes through iterative questioning, originally developed by Sakichi Toyoda for Toyota Motor Corporation.
这是一份通过迭代式提问来挖掘根本原因的系统性指南，最初由丰田佐吉为丰田汽车公司开发。

When to Use This Skill

何时使用该方法

  • Investigating recurring problems
  • Debugging system failures
  • Understanding customer churn
  • Analyzing project delays or budget overruns
  • Post-mortem analysis
  • Process improvement initiatives
  • 调查重复出现的问题
  • 调试系统故障
  • 理解客户流失原因
  • 分析项目延迟或预算超支
  • 事后复盘分析
  • 流程改进举措

Core Concepts

核心概念

The Method

方法流程

Problem Statement
    ↓
Why? → Answer 1
    ↓
Why? → Answer 2
    ↓
Why? → Answer 3
    ↓
Why? → Answer 4
    ↓
Why? → Answer 5
    ↓
Root Cause Identified
    ↓
Solution Implementation
问题陈述
    ↓
为什么？ → 答案1
    ↓
为什么？ → 答案2
    ↓
为什么？ → 答案3
    ↓
为什么？ → 答案4
    ↓
为什么？ → 答案5
    ↓
确定根本原因
    ↓
实施解决方案

Key Principles

关键原则

PrincipleDescription
Facts over assumptionsBase questions on data, not guesses
Systems over individualsFocus on process failures, not blame
FlexibilityGo beyond 5 questions if needed
VerificationValidate findings with evidence
原则说明
基于事实而非假设基于数据提出问题，而非猜测
聚焦系统而非个人关注流程故障，而非指责个人
保持灵活性若有需要，可超出5次提问
验证结论用证据验证发现的问题

Questioning Techniques

提问技巧

Standard Approach

标准方式

For each iteration, ask:
  • Why did this happen?
  • What caused this situation?
  • What led to this outcome?
在每一轮提问中，可以问：
  • 为什么会发生这种情况？
  • 是什么导致了这个问题？
  • 是什么引发了这个结果？

Alternative Phrasing (Less Confrontational)

替代表述（更温和）

When direct "why" questions feel threatening, use softer alternatives:
当直接问“为什么”会让对方有压力时，可以使用更温和的表述：

Root Cause Investigation

根本原因调查

Instead of...Try...
Why did this happen?What was going on when this happened?
Why did you do that?What were you trying to accomplish?
Why is this broken?How do you suppose we ended up here?
避免使用...建议使用...
为什么会发生这种情况？当问题发生时，当时的情况是怎样的？
你为什么要那么做？你当时想要达成什么目标？
为什么这个东西坏了？你觉得我们是怎么走到这一步的？

Understanding Motivation

理解动机

Instead of...Try...
Why do you want this?What happens if we don't get this done?
Why does this matter?What problems does this solve?
Why is this urgent?What do you think will happen if we delay?
避免使用...建议使用...
你为什么想要这个？如果我们不完成这个，会有什么后果？
这个为什么重要？这个能解决什么问题？
为什么这么紧急？你觉得如果我们推迟会发生什么？

Understanding Decisions

理解决策依据

Instead of...Try...
Why did leadership decide this?What were the reasons we went this direction?
Why this approach?How do you see this working long term?
避免使用...建议使用...
领导层为什么做出这个决定？我们选择这个方向的原因是什么？
为什么用这种方法？你认为这种方法长期来看会如何运作？

Analysis Framework

分析框架

Step 1: Define the Problem

步骤1：定义问题

Be specific and measurable:
❌ Bad:  "The system is slow"
✅ Good: "Page load time increased from 2s to 8s after the March release"

❌ Bad:  "Customers are unhappy"
✅ Good: "Customer churn increased by 40% over three months"
要具体且可衡量：
❌ 错误示例："系统运行缓慢"
✅ 正确示例："3月版本发布后，页面加载时间从2秒增加到8秒"

❌ 错误示例："客户不满意"
✅ 正确示例："过去三个月，客户流失率上升了40%"

Step 2: Iterate Through Whys

步骤2：迭代提问“为什么”

Document each level clearly:
Problem: Customer churn increased by 40%

1. Why? → Customers canceling after free trial
2. Why? → Not seeing enough value during trial
3. Why? → Not completing the onboarding process
4. Why? → Onboarding too complex, requires too much setup
5. Why? → Product lacks automation and intelligent defaults

Root Cause: Poor onboarding experience due to lack of automation
清晰记录每一层的答案：
问题：客户流失率上升了40%

1. 为什么？ → 客户在免费试用后取消订阅
2. 为什么？ → 试用期间没有感受到足够的价值
3. 为什么？ → 未完成入职流程
4. 为什么？ → 入职流程过于复杂，需要大量设置操作
5. 为什么？ → 产品缺乏自动化功能和智能默认配置

根本原因：由于缺乏自动化功能，导致入职体验不佳

Step 3: Identify Solutions

步骤3：确定解决方案

Target the root cause, not symptoms:
Symptom-level fix (avoid):
├── Offer discounts to retain customers
└── Send more reminder emails

Root cause fix (preferred):
├── Build automated data import
├── Create intelligent defaults by industry
├── Simplify onboarding to 3 steps
└── Add progress indicators
针对根本原因，而非症状：
针对症状的修复（应避免）：
├── 提供折扣以挽留客户
└── 发送更多提醒邮件

针对根本原因的修复（推荐）：
├── 构建自动化数据导入功能
├── 根据行业设置智能默认配置
├── 将入职流程简化为3个步骤
└── 添加进度指示器

Output Template

输出模板

After completing analysis, document as:
markdown
undefined
完成分析后，按以下格式记录：
markdown
undefined

Five Whys Analysis

Five Whys 分析报告

Problem Statement: [Clear, measurable problem description]
Analysis Date: [Date]
Participants: [Who was involved]
问题陈述： [清晰、可衡量的问题描述]
分析日期： [日期]
参与人员： [参与分析的人员]

Question Chain

提问链

  1. Why? [First answer with evidence]
  2. Why? [Second answer with evidence]
  3. Why? [Third answer with evidence]
  4. Why? [Fourth answer with evidence]
  5. Why? [Fifth answer with evidence]
  1. 为什么？ [第一个带证据的答案]
  2. 为什么？ [第二个带证据的答案]
  3. 为什么？ [第三个带证据的答案]
  4. 为什么？ [第四个带证据的答案]
  5. 为什么？ [第五个带证据的答案]

Root Cause

根本原因

[Identified root cause - the systemic issue to address]
[确定的根本原因——需要解决的系统性问题]

Recommended Solutions

推荐解决方案

PrioritySolutionExpected ImpactEffort
High[Solution 1][Impact][Effort]
Medium[Solution 2][Impact][Effort]
Low[Solution 3][Impact][Effort]
优先级解决方案预期影响实施难度
高[解决方案1][影响][难度]
中[解决方案2][影响][难度]
低[解决方案3][影响][难度]

Success Metrics

成功指标

  • [How will we measure if the solution worked?]
undefined
  • [我们将如何衡量解决方案是否有效？]
undefined

Classic Examples

经典示例

Manufacturing Example (Toyota Original)

制造业示例（丰田原版）

Problem: Machine stopped operating

1. Why? → Motor overheated
2. Why? → Wasn't lubricated enough
3. Why? → Oil pump failed
4. Why? → Filter was clogged
5. Why? → No regular maintenance schedule

Root Cause: Lack of preventive maintenance procedures
Solution: Implement maintenance schedule and checklist
问题：机器停止运行

1. 为什么？ → 电机过热
2. 为什么？ → 润滑不足
3. 为什么？ → 油泵故障
4. 为什么？ → 过滤器堵塞
5. 为什么？ → 没有定期维护计划

根本原因：缺乏预防性维护流程
解决方案：实施维护计划和检查清单

SaaS Example

SaaS示例

Problem: Customer churn increased 40%

1. Why? → Customers canceling after free trial
2. Why? → Not seeing enough value during trial
3. Why? → Not completing onboarding
4. Why? → Onboarding too complex
5. Why? → Lacks automation and smart defaults

Root Cause: Poor onboarding experience
Solutions:
- Automated data import from popular tools
- Intelligent defaults based on industry
- Simplified 3-step onboarding
- In-app progress indicators

Result: 60% decrease in churn, 35% increase in trial conversion
问题：客户流失率上升40%

1. 为什么？ → 客户在免费试用后取消订阅
2. 为什么？ → 试用期间没有感受到足够的价值
3. 为什么？ → 未完成入职流程
4. 为什么？ → 入职流程过于复杂
5. 为什么？ → 缺乏自动化和智能默认配置

根本原因：入职体验不佳
解决方案：
- 从主流工具导入数据的自动化功能
- 基于行业的智能默认配置
- 简化为3步的入职流程
- 应用内进度指示器

结果：流失率下降60%，试用转化率提升35%

Software Bug Example

软件Bug示例

Problem: Production API returning 500 errors

1. Why? → Database queries timing out
2. Why? → Query taking 30+ seconds
3. Why? → Missing index on frequently queried column
4. Why? → Index was dropped during migration
5. Why? → Migration script lacked index recreation step

Root Cause: Incomplete migration testing process
Solutions:
- Add index verification to migration checklist
- Implement automated index coverage tests
- Create pre-production performance benchmarks
问题：生产环境API返回500错误

1. 为什么？ → 数据库查询超时
2. 为什么？ → 查询耗时超过30秒
3. 为什么？ → 频繁查询的列缺少索引
4. 为什么？ → 迁移过程中索引被删除
5. 为什么？ → 迁移脚本缺少重建索引的步骤

根本原因：迁移测试流程不完整
解决方案：
- 在迁移检查清单中添加索引验证步骤
- 实施自动化索引覆盖测试
- 建立生产前性能基准

Best Practices

最佳实践

Do

应该做的

  • Use data - Support answers with evidence and metrics
  • Involve diverse perspectives - Different viewpoints reduce blind spots
  • Focus on systems - Ask "what process failed?" not "who failed?"
  • Document everything - Create audit trail for future reference
  • Verify root cause - Test that fixing it would prevent recurrence
  • 使用数据 - 用证据和指标支撑答案
  • 纳入多元视角 - 不同观点可减少盲区
  • 聚焦系统 - 问“哪个流程出了问题？”而非“谁犯了错？”
  • 记录所有内容 - 创建审计跟踪，供未来参考
  • 验证根本原因 - 测试修复该原因是否能防止问题再次发生

Avoid

应该避免的

  • Stopping too early - Surface answers are usually symptoms
  • Personal blame - "John made a mistake" is never the root cause
  • Single path - Complex problems may have multiple root causes
  • Assumptions - Always verify with data
  • Skipping steps - Each "why" should logically follow the previous
  • 过早停止提问 - 表面答案通常只是症状
  • 指责个人 - “约翰犯了错”永远不是根本原因
  • 单一分析路径 - 复杂问题可能有多个根本原因
  • 依赖假设 - 始终用数据验证
  • 跳过步骤 - 每一个“为什么”都应逻辑上承接上一个答案

Communication Tips

沟通技巧

  • Give people time to respond - embrace silence
  • Ask one question at a time
  • Resist the urge to clarify before they answer
  • Focus on curiosity rather than interrogation
  • Frame as collaborative problem-solving
  • 给对方时间回应 - 接受沉默
  • 一次只问一个问题
  • 在对方回答前不要急于澄清
  • 保持好奇心而非审问心态
  • 以协作解决问题的方式沟通

Integration with Other Methods

与其他方法的结合

The Five Whys works well alongside:
MethodCombined Use
KaizenContinuous improvement cycles
Six SigmaDMAIC problem-solving
Fishbone DiagramVisualizing multiple cause categories
Pareto AnalysisPrioritizing which problems to analyze
Post-mortemIncident review sessions
Five Whys可与以下方法配合使用：
方法结合用途
Kaizen持续改进循环
Six SigmaDMAIC问题解决流程
Fishbone Diagram可视化多类原因
Pareto Analysis优先确定需要分析的问题
Post-mortem事件复盘会议

Resources

参考资源