{"id":1161,"date":"2016-10-15T16:14:52","date_gmt":"2016-10-15T23:14:52","guid":{"rendered":"http:\/\/www.larrylawhead.com\/articles\/?p=1161"},"modified":"2018-05-30T21:46:25","modified_gmt":"2018-05-31T04:46:25","slug":"telling-a-good-story","status":"publish","type":"post","link":"https:\/\/www.larrylawhead.com\/articles\/2016\/10\/telling-a-good-story\/","title":{"rendered":"Discovering the Narrative Behind Failure"},"content":{"rendered":"<h3>Surprised by Failure?<\/h3>\n<p>When your amazing idea results in unexpected outrage, do two things. Observe the Japanese proverb, <i>When something goes wrong fix the process, not the blame.<\/i>\u00a0Then, discover the narrative.<\/p>\n<h3>Tell the Story<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-full wp-image-1164\" src=\"https:\/\/www.larrylawhead.com\/articles\/wp-content\/uploads\/2016\/10\/cave_painting.jpeg\" alt=\"cave_painting\" width=\"278\" height=\"181\" \/>With 40,000 years under our belts, we Homosapiens have become excellent storytellers. From cave paintings to 3D movies the journey has been impressive. Leverage this strength to discover the root cause of failure. It leads to a powerful understanding of what went wrong. This in turn, exposes recovery plans that work.<\/p>\n<p>For this reason I like the A3 Root Cause Analysis. The first thing this analysis requires is to describe the problem. Describing the problem in the form of a narrative, opens the mind, providing a clear overview from several perspectives. At times, I encourage participants to begin their description of the problem using, <i>Once upon a time\u2026 <\/i>This will produce\u00a0more than enough information to understand the background and current\u00a0condition\u00a0of the\u00a0failed process.<\/p>\n<h3>Summarize the Narrative &#8211; Background &amp; Current Condition<\/h3>\n<p>After the stories are told highlight commonalities from each version in bulleted lists describing the background and current condition. Then quantify the impact of the problem by creating a numerical picture. Expressing the impact numerically offers a baseline against which improvements can be measured. Example: <i>This event caused a 24% increase in service desk calls over a period of two days<\/i>.<\/p>\n<h3>Set Goals \/ Target Conditions<\/h3>\n<p>Now that the problem is well understood, an improvement plan is usually not hard to develop. This plan should initially be broken into clearly defined goals\u00a0(target conditions) accompanied by an unambiguous understanding of the expected impact. Example:<\/p>\n<ul>\n<li>30% decrease in support\u00a0calls.<\/li>\n<li>40% decrease in bugs found in production.<\/li>\n<li>20% increase in throughput.<\/li>\n<\/ul>\n<h3>Discover Why<\/h3>\n<p>After background and current conditions are understood\u00a0and goals are set, we are ready to ask why. Discovering why, is done by asking why five times. This method is so popular it requires no explanation. However we must be perfectly clear, yielding to the temptation to ask why before understanding what happened and the expected\u00a0improvement goals may lead to addressing the wrong problem.<\/p>\n<h3>Experiment\u00a0&amp; Confirm\u00a0Results<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-1165\" src=\"https:\/\/www.larrylawhead.com\/articles\/wp-content\/uploads\/2016\/10\/working_together.jpeg\" alt=\"working_together\" width=\"275\" height=\"183\" \/>The goals you set earlier, help develop\u00a0countermeasures (experiments) which are easily decomposed into\u00a0Epics. These are in turn broken into stories and placed into the team\u2019s backlog. The impact of the countermeasures\u00a0will be evident as soon as the first stories are completed\u00a0and presented to the customer. This impact must be confirmed by measuring the results against your goals and baseline. If a\u00a0countermeasure fails, try another. Follow the <a href=\"http:\/\/www.lean.org\/WhatsLean\/\" target=\"_blank\" rel=\"noopener\">Lean<\/a> Startup mantra, <em>fail early, fail often.<\/em> Small incremental improvements are much more impressive than a partially implemented all encompassing plan. Developing a policy to keep an event from ever happening again does not work. The only purpose of this effort is to threaten people, not improve quality.<\/p>\n<h3>Follow-Up &#8211; Improve the Improvements<\/h3>\n<p>The A3 Analysis does not let us off lightly. Putting successful countermeasures in place and eliminating those which fail is only the beginning. We are expected define follow-up steps and continuously keep our eyes on the countermeasures looking for additional experiments. The A3 process is brilliant. Not only does a team shore up their weaknesses through discovering effective countermeasures, but works to improve the improvements!<\/p>\n<p>Here is an example of a basic\u00a0A3 Root Cause template. Try it out. I\u2019m confident doing so will enable mistakes to evolve into long term sustainable change.<\/p>\n<div id=\"attachment_1169\" style=\"width: 690px\" class=\"wp-caption alignleft\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-1169\" class=\"wp-image-1169 size-full\" src=\"https:\/\/www.larrylawhead.com\/articles\/wp-content\/uploads\/2016\/10\/A3-Root-Cause-Analysis-Template.png\" alt=\"A3 Root Cause Analysis Template\" width=\"680\" height=\"492\" srcset=\"https:\/\/www.larrylawhead.com\/articles\/wp-content\/uploads\/2016\/10\/A3-Root-Cause-Analysis-Template.png 680w, https:\/\/www.larrylawhead.com\/articles\/wp-content\/uploads\/2016\/10\/A3-Root-Cause-Analysis-Template-300x217.png 300w\" sizes=\"auto, (max-width: 680px) 100vw, 680px\" \/><p id=\"caption-attachment-1169\" class=\"wp-caption-text\">A3 Root Cause Analysis Template<\/p><\/div>\n<h3>Additional Information<\/h3>\n<ul>\n<li><a href=\"https:\/\/www.youtube.com\/watch?v=p6E8jpFasR0\" target=\"_blank\" rel=\"noopener\">A Whiteboard History of Storytelling<\/a><\/li>\n<li><a href=\"https:\/\/www.scruminc.com\/a3-root-cause-analysis\/\" target=\"_blank\" rel=\"noopener\">A3 Root Cause Analysis &#8211; ScrumLab<\/a><\/li>\n<li><a href=\"https:\/\/www.scruminc.com\/scrum-and-a3-process-game-over-for\/\" target=\"_blank\" rel=\"noopener\">Scrum and the A3 Process: Game Over for Waterfall Companies<\/a><\/li>\n<li><a href=\"http:\/\/sloanreview.mit.edu\/article\/toyotas-secret-the-a3-report\/\" target=\"_blank\" rel=\"noopener\">Toyota\u2019s Secret: The A3 Report<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Surprised by Failure? When your amazing idea results in unexpected outrage, do two things. Observe the Japanese proverb, When something goes wrong fix the process, not the blame.\u00a0Then, discover the narrative. Tell the Story With 40,000 years under our belts, we Homosapiens have become excellent storytellers. From cave paintings to 3D movies the journey has<\/p>\n<p class=\"more-link\"><a href=\"https:\/\/www.larrylawhead.com\/articles\/2016\/10\/telling-a-good-story\/\" class=\"themebutton2\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[4,28,119],"tags":[108,92,107,19,120],"class_list":["post-1161","post","type-post","status-publish","format-standard","hentry","category-product-owner","category-recent_posts","category-scrum-master","tag-a3-root-cause-analysis","tag-agile-scrum","tag-kaizen","tag-larry-lawhead","tag-lean"],"_links":{"self":[{"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/posts\/1161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/comments?post=1161"}],"version-history":[{"count":16,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/posts\/1161\/revisions"}],"predecessor-version":[{"id":1412,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/posts\/1161\/revisions\/1412"}],"wp:attachment":[{"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/media?parent=1161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/categories?post=1161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.larrylawhead.com\/articles\/wp-json\/wp\/v2\/tags?post=1161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}