Lead Change Blog

APRIL 6, 2018

They will help you do all of the above, and I’m going to give them to you right now: Positive Framing and Generative Questions. Leaders, anxious to do something about it, began a root cause analysis and did surveys to clarify the extent of the problem and solicit solutions. There are only two keys. Here’s an example.

Root Cause Analysis 298

Root Cause Analysis Uncertainty Quality Consultative 298

Mike Cardus

SEPTEMBER 24, 2013

The focus on what’s wanted (not what’s wrong), what’s going well (rather than what’s gone badly) and practical progress (rather than explanatory theory) leads to a positive and pragmatic way to work with organizations and individuals. From [link]. What is the Miracle Question? With yourself? michael cardus is create-learning.

TRIZ 146

TRIZ Team Root Cause Analysis Team Building 146

Harvard Business Review

NOVEMBER 1, 2018

Fortunately, virtually everyone can make a positive impact here. FAM can also point out which data attributes have the biggest error rates, suggesting where improvements can be made, using root cause analysis, described next. Over time, seek to make root cause analysis your standard for all important issues.

Root Cause Analysis 15

Root Cause Analysis Team Analysis Learning-by-Doing 15

Harvard Business Review

OCTOBER 3, 2014

Develop a robust root cause analysis capability. Once CoE is created, the pod teams should perform root cause analyses to support the performance management process. They are not left alone to develop root cause analysis insights in a vacuum. Make collaborative decisions.

Root Cause Analysis 9

Root Cause Analysis Metrics Analysis Information Technology 9

Harvard Business Review

OCTOBER 3, 2014

Develop a robust root cause analysis capability. Once CoE is created, the pod teams should perform root cause analyses to support the performance management process. They are not left alone to develop root cause analysis insights in a vacuum. Make collaborative decisions.

Root Cause Analysis 8

Root Cause Analysis Metrics Analysis Retail 8

Harvard Business Review

JULY 2, 2015

Many software development teams hold mini-debriefs every morning to review yesterday’s progress and today’s goals—and longer debriefs every month or two to understand larger project wins and challenges. What caused our results? This is the root-cause analysis and should go deeper than obvious, first-level answers.

Tools 8

Tools Root Cause Analysis Team Objective 8