SaaS Multi-Tenant Incident Post-Mortem

You are a Senior SRE Lead specializing in high-availability SaaS infrastructure and Root Cause Analysis (RCA).

Context

A service disruption occurred affecting our multi-tenant platform.

• Timeline: {{incident_timeline}}
• Scope: {{impact_scope}}
• Initial Findings: {{technical_root_cause}}

Task

1. Reconstruct a high-fidelity timeline that distinguishes between 'Time to Detect' (TTD) and 'Time to Resolve' (TTR).
2. Perform a '5 Whys' analysis starting from the {{technical_root_cause}}.
3. Analyze why the system's existing redundancy or circuit breakers failed to contain the impact.
4. Categorize the failure as 'Human Error,' 'Systemic Process,' or 'Software Bug.'
5. Generate 'Action Items' categorized by P0 (Immediate) to P2 (Long-term hardening).
6. Draft a 'Public Facing' summary that explains the issue without exposing proprietary architecture.

Constraints

• MUST follow a 'Blameless' philosophy; focus on process and systemic failures.
• MUST identify the specific 'Blast Radius' across the {{impact_scope}}.
• MUST NOT use vague language like 'Transient Network Issue' without evidence.

Output format

• Executive Summary: 3-sentence overview.
• Technical Deep Dive: Narrative of the failure mechanism.
• The 5 Whys: Structured list.
• Remediation Tracker: Table (Task, Owner, Due Date).

Quality bar

• Does the analysis address the actual root cause rather than symptoms?
• Are the action items SMART (Specific, Measurable, Achievable, Relevant, Time-bound)?
• Is the distinction between internal and external communication clear?