By Donna Knapp and Michael Cardinal Even prior to the First Industrial Revolution, someone who made their living as a stagecoach driver couldn't possibly imagine that one day people would use an app to arrange an Uber that could take them to the airport where they could get on a plane and fly across the world in a matter of hours. All that history is understood in hindsight, as is the case with any industrial revolution. Fast forward to today. We are in the throes of the Fourth Industrial Revolution and there is massive speculation about the impact of advancements such as artificial intelligence (AI). It’s tempting to think that the problems and challenges that organizations and individuals are currently facing are unique. In reality, as we explore in ‘What Would Deming Do’ , the past provides valuable lessons that we can use to navigate the present and leverage as guidance for the future. What history teaches us is that industrial revolutions have a lot in commo

By Donna Knapp It’s interesting to see how members of different communities can view a practice so differently. That is currently the case with problem management, the practice of identifying, removing, or mitigating the cause or contributing factors to service disruptions. For the most part, the IT service management (ITSM) community recognizes the value of problem management. They may admittedly struggle to find the time or resources needed to perform the practice. Or they may find it difficult to justify the actions needed to introduce permanent solutions identified as a result of the practice. But they, for the most part, value the practice. Conversely, some members of the DevOps community view problem management, or more specifically, root cause analysis, as a complete waste of time. We’ve found that there are a few common reasons that on the surface make sense, but that have counterpoints worth considering. One reason for the pushback is that the practice of root cause analysis i