Building a Case for Change
A framework for using change management techniques in Root Cause Analysis (RCA) and systems analysis, emphasizing alignment of goal, problem, practical steps, roles, and rewards.
THE IDEA
Whatever role you are in, and whatever your level of competence in RCA, making progress in RCA and systems analysis will entail utilising appropriate change management techniques:
- First, have a ‘good enough goal, vision or direction of travel’, so stakeholders understand how these fit into organisational plans and priorities.
- Second, consider how your work will link to a recognised problem area so there is a ‘burning platform’ for action.
- Third, determine practical first steps to take, whether that is communicating with others and/or carrying out a pilot exercise.
- Fourth, clarify roles and responsibilities and consider the skills and resources that must be mobilised, for example, to deliver training or for a pilot exercise. This may include getting support from those who must free up time, staff and budgets.
- Fifth, determine the likely reward that those involved will receive; this could be as simple as giving recognition for problems they have worked to better understand. Also, how will you demonstrate the impact of your efforts and assess whether they are worth continuing?
Diagram B.1 sets out the key ingredients in a tabular format. The diagram itself is not included here. The point is to align these elements so that people have a reason, a plan, and the resources to proceed.
When to use it
Planning a root cause analysis project to ensure organizational support and resources.
Convincing leadership to invest in a new process improvement initiative by demonstrating a clear direction, urgency, and payoff.
Managing a team through a transition by defining roles and responsibilities and aligning incentives.
Designing a pilot program for a change and scaling it up based on demonstrated impact.
FROM THEORY TO EVERYDAY LIFE
In practice
Implementing a new safety protocol in a manufacturing plant
A safety team uses the framework to gain support: they define the goal (reduce accidents by 20%), link to the high accident rate (burning platform), conduct a pilot in one shift, assign roles (trainers, supervisors), and recognize staff participation with public acknowledgment.
Adopting a new software system in a company
An IT department applies the five steps to roll out a new project management tool: set a vision of improved efficiency, highlight current delays (burning platform), pilot with one team, clarify IT support roles, and reward early adopters with positive feedback.
A MOMENT TO REFLECT
Put it to work.
Think of a current change initiative you are involved in. How well have you clarified the 'good enough goal' to stakeholders?
What is the 'burning platform' that justifies the need for change in your organization? How can you articulate it concretely?
What tangible or intangible rewards could encourage participation, and how would you check whether people remain committed?
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)