Root Cause Analysis Handbook

Many organisations spend enormous amounts of time solving problems that continue to reappear.

A customer complaint is addressed, yet similar complaints return. A new policy is introduced, yet performance issues remain. Additional training is provided, yet mistakes continue. In many cases, the issue is not the quality of the solution.

The issue is that the wrong problem is being solved.

Root Cause Analysis (RCA) helps innovators move beyond visible symptoms to identify the underlying factors that create them. Rather than focusing only on what is happening, RCA explores why it is happening.

Within the Evaluate stage of the 5E Design Thinking Framework, Root Cause Analysis helps teams uncover deeper insights, challenge assumptions and define opportunities for meaningful intervention.

The goal is not to fix symptoms.

The goal is to understand causes.

Root Cause Analysis is a structured process used to identify the underlying causes of a problem.

Rather than addressing immediate effects, RCA helps explore:

• Why the problem occurred
• What conditions enabled it
• Which factors contributed
• What systemic influences exist
• How recurrence can be prevented

Root causes are the underlying conditions that create symptoms.

Effective innovation depends on understanding these conditions.

Without RCA, organisations often become trapped in cycles of repeated problem-solving.

Examples include:

Symptom

High employee turnover.

Common Solution

Increase recruitment efforts.

Potential Root Causes

• Workplace culture
• Leadership practices
• Workload pressures
• Career development limitations

Recruitment may temporarily fill vacancies, but turnover continues unless underlying causes are addressed.

One of the most important distinctions in innovation is the difference between symptoms and causes.

Symptom

Students fail assessments.

Possible Cause

Assessment expectations are unclear.

Possible Cause

Feedback is insufficient.

Possible Cause

Learning activities do not adequately prepare students.

The symptom is visible.

The cause requires investigation.

Symptoms attract attention because they are immediate.

People often respond to:

• Complaints
• Failures
• Delays
• Errors
• Conflicts

These events are visible and urgent.

Root causes, however, may be:

• Hidden
• Complex
• Systemic
• Historical

Root Cause Analysis encourages deeper thinking.

True root causes typically:

Influence Multiple Outcomes

The same cause may generate several symptoms.

Persist Over Time

Problems repeatedly emerge.

Exist Beneath the Surface

Not immediately visible.

Influence System Behaviour

They shape patterns rather than isolated events.

One of the simplest RCA techniques is the 5 Whys.

The process involves repeatedly asking:

Why?

until a deeper understanding emerges.

Example

Problem

Students submit assignments late.

Why?

They start too late.

Why?

They underestimate workload.

Why?

Assessment requirements are unclear.

Why?

Instructions are difficult to interpret.

Why?

Assignment documentation is overly complex.

This process reveals opportunities beyond simply reminding students to submit work on time.

The 5 Whys:

• Simple to use
• Encourages deeper thinking
• Exposes assumptions
• Supports group discussion

However, the technique should not be applied rigidly.

Some problems require more extensive analysis.

Fishbone Diagrams, also called Cause-and-Effect Diagrams, help explore multiple contributing factors.

The problem is placed at the head of the fish.

Potential causes are organised into categories.

Common Categories

People

Skills, knowledge, behaviours.

Processes

Workflows and procedures.

Technology

Tools and systems.

Environment

Physical or organisational context.

Policies

Rules and governance structures.

Resources

Time, funding, staffing.

This approach encourages broader thinking.

Cause mapping creates visual representations of cause-and-effect relationships.

Instead of identifying a single cause, teams explore:

• Multiple contributing factors
• Relationships
• Dependencies
• Interactions

This often reveals complexity not visible through linear analysis.

Fault Tree Analysis begins with a problem and works backwards through contributing factors.

Questions include:

• What caused this event?
• What enabled it?
• What conditions existed?

The result resembles an inverted tree.

This technique is particularly useful in safety-critical environments.

Many problems involve human behaviour.

Potential causes include:

• Miscommunication
• Training gaps
• Workload pressures
• Role ambiguity
• Motivation issues

Avoid assuming people are the cause.

Often systems create conditions that shape behaviour.

Problems may originate within organisational systems.

Examples include:

Incentives

People respond to what is rewarded.

Culture

Shared norms influence behaviour.

Leadership

Decisions shape organisational outcomes.

Structure

Reporting relationships influence communication.

Organisational causes often remain hidden unless examined deliberately.

Root Cause Analysis benefits significantly from systems thinking.

Complex problems rarely have single causes.

Instead, multiple factors interact.

Examples:

• Policies influence behaviour.
• Behaviour influences performance.
• Performance influences outcomes.
• Outcomes influence future decisions.

Understanding these relationships improves innovation.

When conducting RCA, examine three levels.

Events

What happened?

Example:

Student satisfaction declined.

Patterns

What keeps happening?

Student satisfaction has declined for three consecutive years.

Causes

What structures and conditions influence the pattern?

Examples:

• Curriculum design
• Communication
• Support services
• Assessment practices

Addressing causes often creates the greatest impact.

Educational challenges often involve deeper causes than initially assumed.

Example:

Symptom

Students disengage.

Potential Causes

• Lack of relevance
• Poor feedback
• Limited interaction
• Excessive workload
• Weak sense of belonging

Discovering these causes creates richer opportunities for innovation.

Organisations frequently use RCA to explore:

• Customer complaints
• Quality issues
• Operational inefficiencies
• Staff turnover
• Innovation failures

The objective is continuous improvement rather than blame.

Design thinking emphasises understanding before solution development.

RCA supports this goal by helping innovators identify:

• Hidden needs
• Structural barriers
• Opportunity areas

Deeper understanding produces better solutions.

Stopping Too Early

The first explanation is rarely the complete answer.

Seeking a Single Cause

Complex challenges often involve multiple causes.

Blaming Individuals

People operate within systems.

Ignoring Context

Environmental factors matter.

Assuming Rather Than Investigating

Evidence should guide analysis.

Step 1

Define the problem clearly.

Step 2

Gather available evidence.

Step 3

Identify possible causes.

Step 4

Use the 5 Whys or Fishbone Diagram.

Step 5

Prioritise significant root causes.

Step 6

Develop opportunities for intervention.

Dig Deeper

Objective

Move beyond symptoms.

Instructions

• Identify a challenge.
• Write the visible symptom.
• Conduct a 5 Whys exercise.
• Create a Fishbone Diagram.
• Compare findings.

Expected Outcome

A clearer understanding of underlying causes.

Estimated Time

45–60 minutes.

Select a recurring problem within:

• Your workplace
• Your course
• Your organisation
• Your community

Identify:

• Three symptoms
• Five possible causes
• Two root causes
• One leverage point for improvement

• Are you solving symptoms or causes?
• What assumptions influence your analysis?
• Which factors remain unexplored?
• What evidence supports your conclusions?
• How might systems thinking strengthen your understanding?

• Symptoms and causes are different.
• Root causes shape recurring problems.
• The 5 Whys provides a simple starting point.
• Fishbone Diagrams support broader analysis.
• Systems thinking strengthens RCA.
• Root causes are often interconnected.
• Effective innovation requires deeper understanding.
• Better diagnosis leads to better solutions.

Identify a recurring challenge you face and conduct a 5 Whys analysis this week. Focus on evidence rather than assumptions and resist the temptation to stop at the first plausible explanation.