The job of this console
Link the incident, record causes, spawn actions, write a lesson if required. Keep people-sensitive data out.
Projects · Knowledge
Root Cause Analysis
Structured cause analysis on delivery failures — hangs off project/incident context, with masked people-sensitive notes.
Scroll to Flowcharts. Scenario: Complete an RCA after an incident.
Why it failed
Cause analysis, then real actions
RCA structures why a delivery failure happened. Fixes still live on issues or tickets with owners.
Projects → Root cause analysis
Route
/project/rca
Org flag rcaEnabled
Manager · Project Manager · Executive · Admin
Seat at the table
PMs, executives, admins. Not a substitute for HR performance files.
The working rhythm
Open after an incident, write, assign actions, close RCA when causes are agreed.
Moments that bring you here
Sev incident. Repeat defect. Customer escalation. Audit of a miss.
ⓘ
Analysis, not the action log
Owners and due dates belong on issues/tickets. Mask snippets for AI and graph.
Flowcharts
1 — Analyze then act
Write causes, spawn actions, optionally a lesson.
flowchart TD
A[Open RCA] --> B[Link project / issue]
B --> C[Causes]
C --> D[Actions]
D --> E[Lesson if required]
- 1OpenProjects → Root cause analysis.
- 2LinkProject and issue/incident.
- 3CausesStructured why.
- 4ActionsOwners on issues/tickets.
Overview
RCA is analysis. Issues/tickets carry the fix work. Lessons capture reuse. AI knowledge assists with masking.
How to use
1. Not a review of a person
Performance module is separate.
2. Actions must exist
RCA text is not the tracker.
3. Mask
No medical or salary in the write-up.