Body of Knowledge · Glossary
Incident command
A single defined role, assigned before the incident, that owns coordination and communication so that responders can focus on the fix. A commander who starts debugging has left the role.
Where the standard develops it
- DE-3Reliability, incident response, and operational ownershipOn-call, SLOs, postmortems, learning from failure.
Related terms
- Blameless postmortem
- An incident review that asks how the system allowed the failure and what to change, rather than who to blame.
- DORA metrics
- The four research-validated delivery measures (deployment frequency, lead time for changes, change failure rate, time to restore service).
- Error budget
- The tolerable shortfall against a service-level objective, treated as a resource to spend that gates risk-taking.
- Ownership map
- The written record of every system, capability and decision and who owns each, checked before and after any structural change.
- Service ownership
- Every service has a named owner responsible for its operation, its interface stability, its documentation and its future.
- Service-level objective
- An explicit reliability target for a service, from which the error budget is derived.
Cite this definition
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Incident command. In Engineering Management Academy Body of Knowledge (Version 3.1, GLO.incident-command). https://www.engineeringmanagement.academy/body-of-knowledge/glossary/incident-command