Jekyll2017-11-30T22:32:41+00:00http://miketwo.net/blog/Per Scribo Ad AstraRandom thoughts. Some of them good.FlowBone Diagrams2017-06-29T13:38:00+00:002017-06-29T13:38:00+00:00http://miketwo.net/blog/2017/06/29/flowbone-diagrams<p>If you've ever spent any time around safety engineers, you'll know that they love their analyses. A good engineer can rattle off a dozen acronyms for the various ways of disecting information -- a PHA, FMEA, CCFA, PRA, etc... There are literally books with tables in them listing the plethora of options available.</p>
<a href="/img/2017-06-29-flowbone-early.png"><img src="/img/2017-06-29-types-of-analyses.png"/></a><span class="caption">You thought I was kidding.</span>
<p>But the problem I've always had is that these analyses are either:
<ul>
<li>too process heavy,</li>
<li>not visual enough, or</li>
<li>require special tools</li>
</ul></p>
<p>I'm a visual thinker and I don't like remembering a million steps or using specialized tools. I need something simple and effective. <strong>Enter the FlowBone Diagram</strong>.</p>
<h2 class="section-heading">What's a FlowBone?</h2>
<p>A FlowBone is a flowchart you draw to help you figure out the root cause of a problem. It's a a cross between <a href="https://en.wikipedia.org/wiki/5_Whys">"5 Why's"</a> and a classic <a href="https://en.wikipedia.org/wiki/Ishikawa_diagram">Fishbone Diagram</a>, but it's my favorite because it's easy to follow (like a fishbone), has space for including notes (like 5Y's), includes color as an additional dimension of information, and doesn't require anything special to create.</p>
<a href="/img/2017-06-29-full-blown-flowbone.png"><img src="/img/2017-06-29-full-blown-flowbone.png"/></a><span class="caption">A full-blown FlowBone</span>
<h2 class="section-heading">How does it work?</h2>
<p>To make a FlowBone, all you do is make a flowchart where everything is connected by "why". Start with the observed problem and work your way down. Add colors as you see fit. </p>
<p>There's no special software required -- anything that can make a flowchart can be used to make this. In my work I've used the Confluence plugin <a href="https://www.gliffy.com/products/confluence-plugin/">Gliffy</a>, but really anything will do.</p>
<h2 class="section-heading">Tips for a smooth FlowBone</h2>
<p>When you first start a root cause analysis, there's going to be way more questions than answers. So I suggest starting with 2 colors -- white and grey. White boxes are things you're certain of, Grey are things under investigation. </p>
<a href="/img/2017-06-29-flowbone-early.png"><img src="/img/2017-06-29-flowbone-early.png"/></a><span class="caption">Lots of work to do.</span>
<p>As you make progress in the investigation, certain paths may become ruled out. Keep them on the graph, but mark them as "cleared" and put notes explaining why. </p>
<a href="/img/2017-06-29-flowbone-medium.png"><img src="/img/2017-06-29-flowbone-medium.png"/></a><span class="caption">The X's are optional, but after hours investigating a dead-end you'll want the satisfaction of placing them.</span>
<p>Eventually you may reach a point where several items may point to a possible common cause. <strong>Focus your efforts here</strong>. This is the biggest advantage that a visual layout can give -- directing the investigation toward meaningful common-cause paths. </p>
<a href="/img/2017-06-29-flowbone-late.png"><img src="/img/2017-06-29-flowbone-late.png"/></a><span class="caption">Zeroing in.</span>
<p>When you've finally narrowed down the root cause, a little visual sugar can make it a great report. You can link boxes to work tickets, highlight the fault path(s), add labels, etc... Do whatever makes sense. The world is your oyster. </p>
<a href="/img/2017-06-29-full-blown-flowbone.png"><img src="/img/2017-06-29-full-blown-flowbone.png"/></a><span class="caption">This oyster cost us several days of downtime.</span>
<p>And that's the FlowBone.</p>
<p><em>If you found this article useful, please <a href="mailto:miketwo@gmail.com">drop me a line</a> and let me know.</em></p>Michael Ricks-AherneIf you've ever spent any time around safety engineers, you'll know that they love their analyses. A good engineer can rattle off a dozen acronyms for the various ways of disecting information -- a PHA, FMEA, CCFA, PRA, etc... There are literally books with tables in them listing the plethora of options available.Hello World2017-06-26T12:00:00+00:002017-06-26T12:00:00+00:00http://miketwo.net/blog/2017/06/26/hello-world<p>So I'm finally taking the plunge and starting a blog, after rejecting the idea for years.</p>
<h2 class="section-heading">Why now?</h2>
<p>The short version is that I want to reach a wider audience. I've always been writing down my thoughts, but to date they've been confined to company wiki's and private journals. And while those are nice, there have been numerous occasions where a colleague has suggested I make a post public. Each time I thought, <em>"Hey, yeah, that's a good idea."</em> Each time it's written on my todo list. And each time it slides down in priority, never to be seen again.</p>
<p><strong>Not anymore</strong>! Today is a new day. A new blog. A new recurring todo!</p>
<h2 class="section-heading">What to expect.</h2>
<p>A large variety of topics.</p>
<p>If all goes well, in the weeks to come you'll find this place filled with thoughts on Aerospace, on Machine Learning, on Education, on Continuous Integration, Visualization, Science, Life, the Universe and Everything. This blog will reflect my brain, as best I can capture it, with all the tangents and detours left intact. I hope that by mining myself continuously, I may eventually strike gold, and in doing so help us all move forward.</p>
<p>So let's get started.</p>Michael Ricks-AherneSo I'm finally taking the plunge and starting a blog, after rejecting the idea for years.