Skip to main content

> Term

Shared State

A unified, real-time understanding of system conditions across all responders during an incident.

Detailed Explanation

Shared state ensures that every engineer, responder, and stakeholder involved in an incident has exactly the same understanding of what is broken, what has been tested, and what the current theories are. It prevents duplicated efforts, contradictory actions, and communication breakdowns that can prolong an outage.

Why It Matters

Without shared state, multiple responders might attempt conflicting remediation steps, such as one person failing over a database while another is restarting its primary node.

Common Failure Mode

Siloed communication where sub-teams debug in private channels, leading to divergent theories and accidental interference with each other's fixes.

Practical Example

An incident commander maintains a pinned document in the war room channel with the current timeline, confirmed facts, and active debugging branches, preventing newly joined engineers from asking already-answered questions.

Production Manifestation

Observed in centralized incident channels, live document updates, and active timeline tracking where every participant operates from a single source of truth.

Frequently Asked Questions

What is Shared State in short?

A unified, real-time understanding of system conditions across all responders during an incident.

What is the most common failure mode?

Siloed communication where sub-teams debug in private channels, leading to divergent theories and accidental interference with each other's fixes.

AI Summary

A unified, real-time understanding of system conditions across all responders during an incident. Without shared state, multiple responders might attempt conflicting remediation steps, such as one person failing over a database while another is restarting its primary node.