惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - Franky
云风的 BLOG
云风的 BLOG
人人都是产品经理
人人都是产品经理
博客园 - 叶小钗
Engineering at Meta
Engineering at Meta
Vercel News
Vercel News
Y
Y Combinator Blog
B
Blog
Microsoft Azure Blog
Microsoft Azure Blog
C
Check Point Blog
M
MIT News - Artificial intelligence
Jina AI
Jina AI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Apple Machine Learning Research
Apple Machine Learning Research
Hugging Face - Blog
Hugging Face - Blog
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
Stack Overflow Blog
Stack Overflow Blog
F
Fortinet All Blogs
博客园 - 司徒正美
I
InfoQ
Google DeepMind News
Google DeepMind News
GbyAI
GbyAI
U
Unit 42

博客园 - 小熊bryan

坐视——做事——做势 InfoQ中文站正式升级为1.5版 编辑絮语 今年…… 书店的风景 要敏捷一点,再敏捷一点 对Ruby中Kernel的callcc方法的研究 理解ruby核心概念:Object, Class, Module, Kernel 再试试看 越来越觉得自己的博客像个包子 翻译作品:为敏捷团队设计协作空间 用元编程的方式向Ruby添加properties 【翻译】在ruby中实现attributes的lazily initialization(惰性初始化) 《Programming Ruby 中文版第二版》P577页singleton_method_undefined方法说明有点问题 是没有好音乐,还是我们没有好心境? Best of Ruby Quiz 之四 Animal Quiz之我的答案 Best of Ruby Quiz 笔记之三:GEDCOM Parser 使用REXML在ruby中处理xml 软件的业务价值来自哪里?——business value generally comes from using software
要问五次为什么--业务需求挖掘之道(摘自Wikipedia)
小熊bryan · 2007-07-22 · via 博客园 - 小熊bryan

5 Whys

From Wikipedia, the free encyclopedia

The five whys is a question asking method used to explore the cause/effect relationships underlying a particular problem. Ultimately, the goal of applying the 5 Whys method is to determine a root cause of a defect or problem. The following example demonstrates the basic process.

  • My car will not start. (the problem)
  • Why? The battery is dead. (first why)
  • Why? The alternator is not functioning. (second why)
  • Why? The alternator has broken beyond repair. (third why)
  • Why? The alternator is well beyond its useful service life and has never been replaced. (fourth why)
  • Why? I have not been maintaining my car according to the recommended service schedule. (fifth why, root cause)

The five iterations are not gospel; rather, it is postulated that five iterations of asking why is generally sufficient to get to a root cause. The real key is to encourage the troubleshooter to avoid assumptions and logic traps and instead to trace the chain of causality in direct increments from the effect through any layers of abstraction to the first or root cause.

The technique was originally developed by Sakichi Toyoda and was later used within Toyota Motor Corporation during the evolution of their manufacturing methodologies. It is a critical component of problem solving training delivered as part of the induction into the Toyota Production System. The architect of the Toyota Production System, Taiichi Ohno, described the 5 whys method as "... the basis of Toyota's scientific approach ... by repeating why five times, the nature of the problem as well as its solution becomes clear." [1] The tool has seen widespread use beyond Toyota, and is now also used within Six Sigma.

Some consider the 5 Whys to be a powerful mnemonic for engineers or technically savvy individuals to help get to the true causes of problems. It has also been criticized as being too basic a tool to analyze root causes to the depth that is needed to ensure that the causes are fixed. Reasons for this criticism include:

  • Tendency for investigators to stop at symptoms rather than going on to lower level root causes.
  • Inability to go beyond the investigator's current knowledge - can't find causes that they don't already know
  • Lack of support to help the investigator to ask the right "why" questions.
  • Results aren't repeatable - different people using 5 Whys come up with different causes for the same problem.

These can be significant problems when the method is applied through deduction only. On-the-spot verification of the answer to the current "why" question, before proceeding to the next, is recommended as a good practice to avoid these issues. [2]