TOOL T-26 | Analysis Tool | Module 7: Conflict Assessment & Mapping

Root Cause Analysis Worksheet

WHEN TO USE When a grievance recurs, persists without resolution, or reflects a systemic condition.

How to Use It

1. Identify the concern to be analyzed: be specific about the presenting issue.

2. Ask 'Why?' five times (or until you reach a root cause that cannot be answered with another 'Why'): Why did this concern arise? Why did that occur? Continue until you reach a root cause.

3. Identify whether the root cause is: a communication failure, a process gap, a coordination failure, a structural inequality, an unresolved prior grievance, or an external factor.

4. For each identified root cause, identify: whether it is within the project's control, what structural change would address it, and who is responsible.

5. Document the analysis and share with project management.

6. Track whether recommended structural changes are implemented.

Purpose

To identify the underlying drivers of a concern or conflict beyond its surface manifestation, enabling structural responses rather than case-by-case management. A concern about a specific land boundary may have a root cause in inadequate notification processes. A recurring noise complaint may have a root cause in contractor schedule misalignment.

Field Rationale

At multiple sites, the same types of concerns appeared repeatedly in different forms. Case-by-case responses closed individual instances but did not address the conditions producing them. Root cause analysis would have identified structural drivers and enabled responses that prevented recurrence.

Fillable Template: Root Cause Analysis

Connections
Linked Protocols

P-02: Signal Escalation Protocol

Guidance Notes

! Field Note — Root cause analysis is not about assigning blame, it is about identifying what needs to change for the concern to stop recurring. Keep the analysis focused on conditions and processes, not individuals.

Adaptation Guidance

For concerns with a long history or complex multi-party dynamics, root cause analysis may require input from community members, not just project staff. Their perspective is often more accurate than an internal analysis.

Connections
Related Skills

SK-05: Pattern Thinking

SK-17: Root Cause Analysis

Connections
Related Tools

T-24: Conflict Mapping Tool

T-23: Grievance Trend Analysis

T-35: Lesson Capture Template