Components in this architecture diagram
- Incident resolved
- Severity SEV1 or SEV2, or customer impact?
- Short incident summary in ticket
- Assign postmortem owner within 24h
- Collect timeline from Slack, PagerDuty & dashboards
- Quantify impact: users, duration, revenue, SLO budget
- Analyse contributing factors with 5 whys
- Draft blameless postmortem doc
- Postmortem review meeting
- Root cause & actions agreed?
- Create action items in Jira with owners & due dates
- Customer-facing communication needed?
- Publish public RCA on status page
- Publish internally
- Track actions weekly
- All actions closed?
- Close postmortem & share learnings
- Done
How to use this architecture diagram template
- Click Open in the editor. The architecture diagram opens on a new page in FlowDiagram — nothing is uploaded and there is no sign-up.
- Rename, add or delete shapes and drag them where you want; connectors stay attached as things move.
- Drop in vendor logos from the library — 1,160 of them, including every AWS, Azure and Google Cloud service icon — or restyle it with the colour and theme controls.
- Prefer text? Edit the Mermaid source below and paste it in through ☰ → Import diagram (see the Mermaid editor); it imports as an editable diagram.
- Export to PNG, SVG or PDF, or press Ctrl+L for a link that carries the whole diagram.
Mermaid source
The whole template is the text below. Paste it into FlowDiagram, keep it in Git next to the code it describes, or hand it to an AI assistant to extend.
flowchart TD
A((Incident resolved)) --> B{Severity SEV1 or SEV2, or customer impact?}
B -->|No| C[Short incident summary in ticket]
B -->|Yes| D[Assign postmortem owner within 24h]
D --> E[Collect timeline from Slack, PagerDuty & dashboards]
E --> F[Quantify impact: users, duration, revenue, SLO budget]
F --> G[Analyse contributing factors with 5 whys]
G --> H[Draft blameless postmortem doc]
H --> I[Postmortem review meeting]
I --> J{Root cause & actions agreed?}
J -->|No| G
J -->|Yes| K[Create action items in Jira with owners & due dates]
K --> L{Customer-facing communication needed?}
L -->|Yes| M[Publish public RCA on status page]
L -->|No| N[Publish internally]
M --> N
N --> O[Track actions weekly]
O --> P{All actions closed?}
P -->|No| O
P -->|Yes| Q[Close postmortem & share learnings]
C --> R((Done))
Q --> R
Related: System architecture diagram tool · Mermaid editor · All software engineering & state machines templates · All 521 templates