Skip to main content

> Term

Decision Authority

The official power granted to an individual or role to make final technical, product, or architectural choices.

Detailed Explanation

Decision authority dictates who has the final say when a team is deadlocked. Without clear authority, teams can debate endlessly over tech stacks, database schemas, or API designs, leading to "analysis paralysis."

Why It Matters

Ambiguous authority leads to shadow IT, where teams bypass the official process because it is too difficult to figure out who is actually allowed to approve a change.

Common Failure Mode

Giving authority to individuals who lack the technical competence to evaluate the trade-offs, reducing technical decisions to political favors.

Practical Example

Two senior engineers cannot agree on whether to use GraphQL or REST for a new API. Because the Engineering Manager refuses to exercise decision authority, the team builds both, creating a fragmented and unmaintainable backend.

Production Manifestation

A critical security patch is delayed for three weeks because nobody knows if the CISO, the VP of Engineering, or the Lead Architect has the final authority to approve the downtime.

Frequently Asked Questions

What is Decision Authority in short?

The official power granted to an individual or role to make final technical, product, or architectural choices.

What is the most common failure mode?

Giving authority to individuals who lack the technical competence to evaluate the trade-offs, reducing technical decisions to political favors.

AI Summary

The official power granted to an individual or role to make final technical, product, or architectural choices. Ambiguous authority leads to shadow IT, where teams bypass the official process because it is too difficult to figure out who is actually allowed to approve a change.