root-cause-analysis

name	root-cause-analysis
description	Diagnose root causes using 5 Whys, fishbone diagrams, fault trees, and Pareto analysis. Use when troubleshooting recurring problems or post-incident analysis.
domain	mindset
author	oyi77
license	Apache-2.0
subdomain	mindset
tags	["cause","mindset","personal-development","root","soft-skills"]
version	1.0.0

Root Cause Analysis

Overview

Mindset skill for root cause analysis. Builds capability through deliberate practice and structured frameworks.

Anti-Rationalization Table

Rationalization	Reality
"I'll figure it out as I go"	A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising.
"I already know this topic"	Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps.
"This doesn't apply to my situation"	The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold.
"One more tool will fix it"	Adding complexity rarely solves process gaps. Master the core workflow first.

When to Use

Trigger phrases:

• "root cause analysis"

• "Post-incident or post-mortem analysis"

• "Troubleshooting recurring problems"

• "Quality issues or defects"

• Post-incident or post-mortem analysis

• Troubleshooting recurring problems

• Quality issues or defects

• Process improvement initiatives

• When NOT to use: Emergencies requiring immediate fixes (fix first, analyze later), or when root cause is obvious

When NOT to Use

• When the situation requires professional counseling or therapy
• For high-stakes decisions that need expert judgment
• When the skill conflicts with cultural or personal values

Core Principles

• Start small — Begin with manageable root cause analysis practices and build incrementally
• Be consistent — Daily practice beats occasional intense effort
• Track progress — Measure improvement to maintain motivation
• Reflect regularly — Review what's working and adjust your approach

Daily Practice

1. Morning intention — Set a specific root cause analysis goal for the day
2. Active practice — Apply root cause analysis techniques during real situations
3. Evening reflection — Review the day's root cause analysis moments and lessons learned
4. Journal entry — Record insights, wins, and areas for improvement

Frameworks

• OODA Loop — Observe, Orient, Decide, Act — for rapid root cause analysis decision cycles
• PDCA Cycle — Plan, Do, Check, Act — for iterative root cause analysis improvement
• After-Action Review — What happened? Why? What to improve?
• Deliberate Practice — Focused effort on specific root cause analysis weaknesses

Common Pitfalls

• Perfectionism — Waiting for ideal conditions instead of starting now
• Inconsistency — Practicing sporadically instead of building a routine
• Isolation — Not seeking feedback or accountability partners
• Overwhelm — Trying to improve everything at once instead of focusing

Resources

• Keep a root cause analysis journal for tracking progress
• Find an accountability partner or mentor
• Set weekly root cause analysis challenges with measurable outcomes
• Review and adjust your approach monthly

# Daily Practice Template

## Morning (5 min)
- Set intention for the day
- Review top 3 priorities

## During the day
- Practice the skill in real situations
- Note moments of success and struggle

## Evening (5 min)
- Reflect: What worked? What did not?
- Log one lesson learned

Process

1. Prepare — Gather requirements, verify prerequisites, set up environment
2. Execute — Run root cause analysis workflow with configured parameters
3. Verify — Validate output meets requirements, document results

Verification

• All steps executed successfully
• Results validated against acceptance criteria
• Error handling tested with edge cases
• Documentation updated with findings