Operational Excellence methodologies, IT Service Management best practices and business wisdom all agree that letting problems go unresolved in your organization can lead to inefficient use of resources, process inconsistencies and in some cases critical business impacting incidents.\u00a0 Many business leaders and managers interpret this to mean that all problems are bad and it is critical root causes be identified and fixed.\u00a0 While this perspective has merit, the situation is rarely as simple as black & white.<\/p>\n
Problems are like opportunities in that there will always be more of them than the organization can<\/em><\/strong> feasibly address. Problems are also like opportunities in that not all of them should<\/em><\/strong> be addressed. Sometimes, for reasons of cost, risk, benefits and other opportunities, it is necessary (or desirable) to leave the root causes of some problems unresolved to focus on other things.\u00a0 Here are 4 reasons why it may be better NOT to address the root cause of a problem:<\/p>\n 1.\u00a0The basic ROI just isn\u2019t there.<\/strong>\u00a0 It is sometimes costlier to fix a root-cause than to live with the problem.\u00a0 This may be because the problem isn\u2019t very impactful to begin with or the fix is quite expensive.\u00a0 It could also be because the underlying situation is expected to change in the future so the benefits to be gained from implementing the fix have a short lifespan.<\/p>\n 2.\u00a0It may not be a recurring issue.<\/strong>\u00a0 All problems have a risk profile which includes the likelihood that the problem will happen again and the impact if it does occur.\u00a0 The fact that an incident happened in the first place or a series of factors were present in the environment to create a situation where someone took notice is a strong indication that a problem indeed exists.\u00a0 Just because something happens once, does not mean it will happen again.\u00a0 Applying risk management techniques can help differentiate one-time-events from recurring problems that really are critical to address<\/p>\n 3.\u00a0The fix may cause unintended consequences<\/strong>.\u00a0 Problems don\u2019t exist in isolation \u2013 they are part of the broader environment and frequently involve a complex web of cause-and-effect relationships.\u00a0 Depending on the confidence in the root-cause that was identified and the organization\u2019s understanding of the whole environment, implementing a fix could cause bigger problems than the original one it intended to solve.<\/p>\n 4.\u00a0Opportunity cost is greater than the benefit<\/strong>. Organizations have limited time and resources and always have choices on how to best use them.\u00a0 The decision on whether to address a specific root-cause can\u2019t be taken in isolation \u2013 it must be treated as an investment and considered in the context of the greater portfolio of investment options.\u00a0 Once the low hanging fruit has been harvested, it may be better to leave some root causes unresolved and focus on other opportunities.<\/p>\n The guidance of best practices and business wisdom are correct that letting problems go unresolved can lead to future impacts, but so can fixing them.\u00a0 The key is to take a step back from the individual problem and look at the bigger picture of the situation to apply objective judgement to determining whether that specific problem should be fixed. By doing so, you will find that many root-causes are better left un-addressed and instead focus the organization\u2019s resources on opportunities with greater value potential.<\/p>\n Kepner-Tregoe has been helping companies improve their problem-management processes for over 60 years through a combination of training, process best-practices and consulting.\u00a0 The experts at KT understand that each problem is part of your company\u2019s bigger picture and can help you implement the skills, decision-making criteria and problem-solving processes to get the most value from your problem-management investments.<\/p>\n","protected":false},"excerpt":{"rendered":" Operational Excellence methodologies, IT Service Manage […]<\/p>\n","protected":false},"author":17,"featured_media":572,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"ppma_author":[],"class_list":["post-25148","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"yoast_head":"\n