-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
292 lines (225 loc) · 11.9 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
<!doctype html>
<meta charset="utf-8">
<script src="https://distill.pub/template.v2.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.4/d3.min.js"
integrity="sha512-nfUlp2ZWPKWlnAH/OsMeAqRSYBxOdPYeBXwceyw6QqqZ7uTT/s5/eS1hMKphjVBouk0jf/JQ8ULVJRnEqSHkXA=="
crossorigin="anonymous" referrerpolicy="no-referrer"></script>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.min.css"
integrity="sha384-3UiQGuEI4TTMaFmGIZumfRPtfKQ3trwQE2JgosJxCnGmQpL/lJdjpcHkaaFwHlcI" crossorigin="anonymous">
<!-- The loading of KaTeX is deferred to speed up page rendering -->
<script defer src="https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.min.js"
integrity="sha384-G0zcxDFp5LWZtDuRMnBkk3EphCK1lhEf4UEyEM693ka574TZGwo4IWwS6QLzM/2t"
crossorigin="anonymous"></script>
<!-- To automatically render math in text elements, include the auto-render extension: -->
<script defer src="https://cdn.jsdelivr.net/npm/[email protected]/dist/contrib/auto-render.min.js"
integrity="sha384-+VBxd3r6XgURycqtZ117nYw44OOcIax56Z4dCRWbxyPt0Koah1uHoK0o4+/RRE05" crossorigin="anonymous"
onload="renderMathInElement(document.body);"></script>
<script type="module">
import mermaid from 'https://cdn.jsdelivr.net/npm/[email protected]/+esm'
</script>
<style>
.node circle {
fill: #fff;
stroke: steelblue;
stroke-width: 3px;
}
.node text {
font: 12px sans-serif;
}
.link {
fill: none;
stroke: #ccc;
stroke-width: 2px;
}
eqn-num {
display: none !important;
}
</style>
<d-front-matter>
<script id='distill-front-matter' type="text/json">{
"title": "Improving '5 Whys' root cause analysis with the Many Whys",
"description": "An evolutionary approach to root cause analysis.",
"published": "July 17 2023",
"volume": "1",
"doi": "Draft v0.8",
"authors": [
{
"author":"Adam Craven",
"authorURL":"https://adamcraven.com/",
"affiliations": [{"name": "Y-Align", "url":"https://y-align.com"}, {"name": "Principles.dev", "url":"https://principles.dev"}]
}
],
"katex": {
}
}</script>
</d-front-matter>
<d-title>
<p>Root Cause Analysis (RCA) is a tool used in problem-solving and decision-making processes. This paper examines an
evolutionary approach to RCA, referred to as the "Many Whys",". We focus on the methodology of this new
approach, and its advantages over an existing 5 Whys methods</p>
</d-title>
<d-article>
<a class="marker" href="#section-1" id="section-1"><span>1</span></a>
<h2 id="abstract">Abstract</h2>
<p>Root Cause Analysis (RCA) is a tool used in problem-solving and decision-making processes. This paper examines an
evolutionary approach to RCA, referred to as “The Many Whys,". We focus on the methodology of this new
approach, and its advantages over an existing method, “The 5 Whys”
</p>
<a class="marker" href="#section-2" id="section-2"><span>2</span></a>
<h2 id="introduction">Introduction</h2>
<p>In today's complex and fast-paced world, effectively identifying and addressing the root causes of problems
is a crucial aspect of decision-making processes. Root Cause Analysis (RCA) has traditionally been a valuable
tool in this regard. However, conventional RCA methods often fall short when dealing with multifaceted issues,
leaving room for improved problem-solving approaches.</p>
<a class="marker" href="#section-2.1" id="section-2.1"><span>2.1</span></a>
<h3 id="background-on-root-causes-analysis">Background on root causes analysis</h3>
<pre class="mermaid l-body">
graph TB
AP[Apparent Problem]
S1[Symptom of problem]
S2[Symptom of problem]
S3[Symptom of problem]
PRC1_1[Possible root cause]
PRC1_2[Possible root cause]
PRC2_1[Possible root cause]
ARC[Actual Root cause]
PRC3_1[Possible root cause]
PRC3_2[Possible root cause]
AP-->S1
AP-->S2
AP-->S3
S1-->PRC1_1
S1-->PRC1_2
S2-->PRC2_1
PRC2_1-->ARC
S3-->PRC3_1
S3-->PRC3_2
</pre>
<p>A root cause analysis attempts to find the underlying cause of a problem, that if resolved would be the most
effective solution the
problem or issue. It avoids immediately attempting to solve the problem and digs deeper.</p>
<div class="lorentzian">
</div>
<p>Effective problem-solving tends to follow a lorentzian distribution, such that resolving proximiate causes tend
to be ineffective at solving the problem. Whereas, accurate identification of the root cause tends to be very
effective at resolving the problem. Finally, distant causes whilst they objectively may be the ultimate cause as
to why a problem
exists - such as the fact that the big-bang occured - are ineffective in resolving that problem.</p>
<a class="marker" href="#section-3" id="section-3"><span>3</span></a>
<h2 id="problem">Problem</h2>
<p>The underlying problem is the limitation of traditional RCA methods, such as the "Five Whys", in
addressing complex issues with multiple causes and diverse branching problems. These methods tend to
oversimplify problems and often assume linear and singular causality, leading to incomplete understanding and
ineffective solutions. This problem impacts a wide range of industries and sectors, affecting decision-makers
who rely on RCA to solve critical issues.</p>
<a class="marker" href="#section-3.1" id="section-3.1"><span>3.1</span></a>
<h3 id="the-five-whys">The problem with '5 Whys'</h3>
<p>The five whys is a technique that asks the question “why” 5 or more times.</p>
<pre class="mermaid l-body">
graph TB
A[Problem: Our client is refusing to pay for leaflets we printed for him] --> B{Why?}
B -->|The delivery was late, so the leaflets couldn't be used| C{Why?}
C -->|The job took longer than expected| D{Why?}
D -->|We ran out of printer ink| E{Why?}
E -->|The ink was all used on a large last-minute order| F{Why?}
F -->|Root cause: We didn't have enough ink in stock, and couldn't order new supplies in time| G[Root Cause]</dt-mermaid>
</pre>
<p>Whilst the 5 Whys is easy to implement without supervision it has many cons <d-cite
key="Card2016-mo"></d-cite><d-cite key="FiveWhys2007"></d-cite>
</p>
<ul>
<li>5 Whys may oversimplify complex problems by often only considering a single root cause</li>
<li>Assumes linear causality: The 5 Whys method assumes that problems have linear and singular causes, whereas
many issues may have multiple contributing factors and complex relationships between them, that may prevent
one from reaching the final cause.</li>
<li>Inadequate exploration of branching-related problems: The 5 Whys method does not inherently accommodate the
exploration of branching questions that may arise from initial answers. As a result, critical aspects of the
problem may remain hidden, as problems are skipped over, leading to an incomplete understanding of the issue
</li>
<li>The 5 Whys can often stop short of a comprehensive analysis, as stopping at the fifth "why" may
not always reveal the true root cause. Even though you don’t need to stop at the fifth why, the naming of
the method often constraints. Some problems may require more or fewer "whys" to reach the
underlying cause (Dekker, S. (2006). The Field Guide to Understanding Human Error. CRC Press).</li>
<li>Limitations due to simplistic questioning: The 5 Whys technique relies on asking the simple question
"why," which may not always be sufficient to explore complex problems. The technique may require
clarification or additional probing questions to yield meaningful insights (Kepner, C. H., & Tregoe, B.
B. (1965). The rational manager: A systematic approach to problem solving and decision making. New York:
McGraw-Hill).
</li>
</ul>
<a class="marker" href="#section-4" id="section-4"><span>4</span></a>
<h2 id="proposed-solution">Proposed solution</h2>
<p>This paper introduces the "Many Whys" approach, a evolutionary RCA method developed through consulting
practices. This approach enhances the traditional "Five Whys" method by incorporating additional
questions into the process.</p>
<p>The "Many Whys" approach allows for a more comprehensive exploration of problem branches and ensures
clarity within the team. The process includes asking "Why?" to attempt to identify the root cause.
However, the addition of additional questions uncovers potentially undiscovered answers, enabling multiple
avenues of investigation. </p>
<p>
Evidence from the application of this approach suggests that it facilitates a more profound and broader
understanding of problems, especially those with multiple causes. It also promotes team engagement and
understanding, thus enhancing the overall effectiveness of the problem-solving process.
</p>
<a class="marker" href="#section-4.1" id="section-4.1"><span>4.1</span></a>
<h2 id="how-it-works">How it works</h2>
<h3 id="the-process">The process</h3>
<p>1) Ask “why?” - General why</p>
<p>2) Ask “why does {cause} create {effect}?” (a why chain) - to chain the whys in a cause an effect chain</p>
<p>3) Ask “what else?” zero or more times - to branch the solution</p>
<a class="marker" href="#section-4.1.1" id="section-4.1.1"><span>4.1.1</span></a>
<p><strong>The why chain</strong> </p>
\begin{equation}Cause + Effect = \text{Why Question}\end{equation}
<p>
The why chain, directly links cause and effect together. It asks why was the cause created in reference to the
previous cause.
e.g. Our code base keeps getting rewritten (Cp) → People keep leaving the team (C)
why does “People leaving the team” cause “Our code base to keep getting rewritten”?</p>
<pre class="mermaid l-screen" style="text-align: center;">
graph TB
AP[Apparent Problem]
P1[Problem 1]
P1_1[Problem 1.1]
P1_2[Problem 1.2]
P1_2_1[Problem 1.2.1]
P2[Problem 2]
P2_1[Problem 2.1]
P2_2[Problem 2.2]
P2_1_1[Problem 2.1.1]
RC[Root cause]
P2_3[Problem 2.3]
P3[Problem 3]
P3_1[Problem 3.1]
P3_2[Problem 3.2]
AP-->|"Question: Why?"|P1
P1-->|"Question: Why?"|P1_1
P1-->|"Question: Why does problem 1 cause apparent problem?"|P1_2
P1_2-->|"Question: Why does problem 1 cause problem 1.2?"|P1_2_1
AP-->|"Question: What else?"|P2
P2-->|"Question: Why?"|P2_1
P2-->|"Question: Why does problem 2 cause apparent problem?"|P2_2
P2_2-->|"Question: Why?"|P2_1_1
P2_2-->|"Question: Why does problem 2.2 cause problem 2?"|RC
P2-->|"Question: What else?"|P2_3
AP-->|"Question: What else?"|P3
P3-->|"Question: Why?"|P3_1
P3-->|"Question: Why does problem 3 cause apparent problem?"|P3_2
</pre>
</p>
<a class="marker" href="#section-5" id="section-5"><span>5</span></a>
<h2 id="vodel">Vodel</h2>
<p>Visual model of the Many Whys process + domain</p>
</d-article>
<iframe width="90%"
style="height: 100vh; margin: 0 auto; display: block; border:5px solid red; border-bottom:0; border-top:0;"
src="https://miro.com/app/live-embed/uXjVMIo9CiU=/?moveToViewport=-3861,-4838,7052,2834&embedId=237601126513"
frameborder="0" scrolling="no" allow="fullscreen; clipboard-read; clipboard-write" allowfullscreen></iframe>
<mind-map></mind-map>
<d-appendix>
<h3>Contributors</h3>
<ul>
<li>Nicky Hannaway - Initial concept validation</li>
</ul>
<d-bibliography src="bibliography.bib"></d-bibliography>
</d-appendix>
<script src="./index.js"></script>