<!---->
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]
相关推荐
增量收集(Incremental Collecting)是解决内存碎片问题的一种方法,它将垃圾收集的工作分散到多次执行过程中,以减少单次GC对程序的影响。 新一代的垃圾回收算法,如Garbage First(G1)收集器,旨在更好地处理大...
企业管理软件小史(摘自企业信息化:需求变化引发软件危机)
要使用`gdb`调试程序,首先需要通过`gdb filename`命令加载要调试的程序文件。例如,`gdb my_program`会启动`gdb`并关联到`my_program`。 2. **设置断点** - `break`命令用于设置断点,可以按行号指定,如`break ...
随机需求条件下的供应商柔性分析和选择模型摘自论文资源库.doc
React Native的核心理念是"Learn once, write anywhere",即学习一次,到处编写。这意味着开发者可以用一套语言和库来开发iOS、Android甚至是Web应用。 ### 2. JavaScript基础知识 作为本项目的基础,你需要熟悉...
- 精确计算与近似计算:并非所有题目都需要精确计算,大部分情况只需求得满足条件的近似值。 - 简化技巧:通过提取数据的主要特征,减少计算的复杂性,例如找比例、倍数等关系。 - 使用估算和比例:在不影响答案...
### 用户定义与UI设计 #### 一、引言 在当今移动互联网时代,用户体验(User Experience, UX)...通过学习这些知识,开发者不仅能够提升自身的UI设计能力,还能够更好地满足用户需求,为用户提供更加优质的产品和服务。
"Wiki-split"项目就是这样一个专门针对NLP研究的资源库,它包含了从Wikipedia中精心挑选和编辑的一百万个英语句子,每个句子都被巧妙地拆分为两个部分,以保持原句的完整意义。这一创新的数据集为研究人员提供了训练...
https://www.cnblogs.com/solitarywares/p/7629893.html require用于建立states之间的关系,这种依赖关系以<state name> : 的形式来定义 Requisites有两种形式,require和require_in,分别表示依赖和被依赖的关系
Anaconda指的是一个开源的Python发行版本,其包含了conda、Python等180多个科学包及其依赖项。 [1] 因为包含了大量的科学包,Anaconda 的下载文件比较大(约 531 MB),如果只需要某些包,...-------------摘自百度百科
个世界顶级摄影及相关网站-摘自《影像视觉》杂志(完整版).doc
Laravel开发-lara-pdf-merger-php-7-2 摘自https://github.com/deltaaskii/lara-pdf-merge。将each()(在php 7.2中折旧)替换为foreach。
### 数据挖掘工具IBM DB2 Intelligent Miner for Data教程 #### 关于本教程 本文档摘自IBM官方手册《使用IBM DB2 Intelligent Miner for Data》,适用于版本6.1。为便于理解和应用,作者对原始文本进行了轻微调整...
单片机与运算放大器(运放)的结合在电子工程和自动化领域中扮演着重要角色。运放是一种集成电路,...《单片机-运放的应用(摘自OHM丛书)》这本书可能会涵盖这些基本概念以及更多高级应用,是深入学习和实践的好资源。
这就要求项目管理者在设计商业智能系统时,需要深入了解业务流程、业务用户的需求,以及如何将数据转化为有价值的商业洞察。 一个成功的商业智能系统会对业务决策制定者提供信息和工具,帮助他们制定出更具操作性和...
1. 机器学习为什么要使用概率 2. 概率学派和贝叶斯学派 3. 何为随机变量和何又为概率分布? 4. 条件概率,联合概率和全概率公式: 5. 边缘概率 6. 独立性和条件独立性 7. 期望、方差、协方差和相关系数 8. 常用概率...
- 业务分析术语表摘自《政府商务办公室术语表/缩写词表》,版权所有归英国政府商务办公室所有,并获得HMSO和政府商务办公室的许可后在本书中使用。 - BABOK®和Business Analysis Body of Knowledge®为国际业务分析...
根据标题“TI电源管理方案,摘自TI官方网站”以及描述“TI电源管理方案,摘自TI官方网站,可以通过学习提高自己电源知识”,我们可以了解到这部分文档主要介绍了德州仪器(Texas Instruments,简称TI)在电源管理...
并行通信是指数据各位可以通过多条线同时传输,⼀次传送8bit、16bit、32bit甚⾄更⾼的位数,相应地就需要8根、16根、32根甚⾄更多的信号线,优点是传输速率⾼,缺点就是线多成本就⾼了,抗⼲扰能⼒差,因⽽适⽤于短...
第6版更加突出了软件过程,增加了敏捷开发方法,论述了很多人们称之为“21世纪工程学科”的重要主题。 对第6版的内容做了如下划分,更便于课堂教学及自学使用: ●第一部分 软件过程,介绍了惯例模型和敏捷过程模型...