#56GOVERNANCEGOVERN
Status Communication
User-facing status updates
Easy
Overview
Public status page showing system health and incident updates.
Why It Matters
Users know you're aware. Reduces support load during incidents.
The Risk
Without status communication, users assume you're unaware. Support gets flooded. Customer frustration amplifies. Social media fills the communication vacuum.
Implementation Components
A complete implementation of this capability includes:
- Public status page
- Component-level status (not just 'up/down')
- Incident update workflow
- Email/SMS subscription options
- Historical uptime display
- Integration with monitoring for automated updates
Implementation Pattern
- 1Set up status page
- 2Define components
- 3Automate status updates
- 4Subscribe users
Pipeline Coverage
This continuous capability monitors and applies to the following pipeline phases:
RELEASE
Tool Examples
These are examples, not endorsements. Choose what fits your context.
Dependencies
This capability stands independently.
Same Layer
Other capabilities in this continuous layer
- •#54 Severity Definition
- •#55 Incident Timeline
- •#57 Post-Incident Review
- •#58 Change Ledger
- •#59 Recovery Runbooks
+6 more