Skip to main content

> Term

Decision Accountability

The requirement for an individual or group to take responsibility for the outcome of a technical or business choice.

Detailed Explanation

True decision accountability means that the person who chooses a specific architecture, framework, or vendor is also the one who deals with the consequences if it fails, scales poorly, or exceeds budget.

Often, architects make decisions but engineers bear the accountability when things break in production.

Why It Matters

When accountability is separated from authority, reckless decisions are made because the decision-maker does not feel the pain of maintenance or operational overhead.

Common Failure Mode

"Seagull management"—flying in, dropping a massive architectural mandate, and flying away before the implementation begins.

Practical Example

A CTO dictates that all new services must use a complex event-sourcing pattern. The pattern proves too difficult for the junior team to maintain, leading to severe data corruption. The CTO blames the team's execution rather than owning the poor architectural choice.

Production Manifestation

An executive mandates a switch to a niche database technology they read about on a blog, but the on-call engineers are the ones losing sleep when it crashes every weekend.

Frequently Asked Questions

What is Decision Accountability in short?

The requirement for an individual or group to take responsibility for the outcome of a technical or business choice.

What is the most common failure mode?

"Seagull management"—flying in, dropping a massive architectural mandate, and flying away before the implementation begins.

AI Summary

The requirement for an individual or group to take responsibility for the outcome of a technical or business choice. When accountability is separated from authority, reckless decisions are made because the decision-maker does not feel the pain of maintenance or operational overhead.