v5

Author: wojciech11

05_slides/README.md

@@ -8,6 +8,14 @@
 
 ## Incident Management
 
+```mermaid
+flowchart
+ I(Incident) -. Well defined process .->l
+ l(Incident\nCommander) --> H(Communication\n Manager)
+ l --> D(Direct\nContributor)
+ l --> C(Communication\nChannel)
+```
+
 Roles:
 
 - Incident Commander (IC) - "the commander holds all positions that they have not delegated. If appropriate, they can remove roadblocks that prevent Ops from working most effectively" ([sre book](https://www.atlassian.com/incident-management/incident-response/incident-commander#3-duties-of-an-incident-commander)).
@@ -18,8 +26,8 @@ Roles:
 
 Procedure:
 
-1. Alert -> OnCaller or person on duty become a IC 
-2. IC creates a channel to coordinate the incident
+1. Alert -> OnCaller or person on duty become a IC
+2. IC creates a channel to coordinate the incident (a call, slack channel, etc.)
 3. IC names CM and DCs
 4. CM handles the external communication and stackholder management
 5. DCs works on the solution, ICs use his super powers to ensure we can resolve the indicent.
@@ -28,7 +36,7 @@ After:
 
 1. IC schedule a postmortem meeting and find a facilitator
 2. (optional) DCs with ICs check which clients were affected
-3. CM with IC publish a result of postmortem to clients if needed 
+3. CM with IC publish a result of postmortem to clients if needed
 
 Best Practices: