Skip to main content

> Term

Response Authority

The organizational power and capability explicitly granted to an engineer or team to act when a risk materializes into an incident.

Detailed Explanation

Detecting an incident is useless if the person who finds it lacks the authority to stop it. Response authority means an on-call engineer can pull the cord—reverting a deployment, taking a service offline, or blocking traffic—without waiting for three layers of management approval. It shifts power from bureaucratic hierarchies to the operational frontline.

Why It Matters

During a severe outage, the time spent finding an executive to authorize a rollback often causes more damage than the bug itself.

Common Failure Mode

A company heavily invests in monitoring and alerting, but mandates that any production change during an incident requires a VP's verbal approval.

Practical Example

A site reliability engineer observes a runaway database query and exercises their response authority to aggressively kill the connection, prioritizing overall system stability over one user's request.

Production Manifestation

An automated alert fires, and the junior on-call engineer immediately triggers a rollback pipeline without asking permission, successfully mitigating the outage in seconds.

Frequently Asked Questions

What is Response Authority in short?

The organizational power and capability explicitly granted to an engineer or team to act when a risk materializes into an incident.

What is the most common failure mode?

A company heavily invests in monitoring and alerting, but mandates that any production change during an incident requires a VP's verbal approval.

AI Summary

The organizational power and capability explicitly granted to an engineer or team to act when a risk materializes into an incident. During a severe outage, the time spent finding an executive to authorize a rollback often causes more damage than the bug itself.