Skip to main content

> Term

decision rights

The explicit authority granted to an individual or team to make choices about architecture, roadmap, or resolution.

Detailed Explanation

Decision rights clarify who gets to make the final call when consensus cannot be reached. In software engineering, this is crucial for preventing endless debates over technology stacks, system design, or incident mitigation strategies.

Ambiguous decision rights lead to 'design by committee', resulting in compromised architectures that try to please everyone but work for no one.

Why It Matters

It eliminates organizational paralysis and ensures that architectural choices are made swiftly and with clear accountability.

Common Failure Mode

A junior engineer makes a sweeping architectural change because no one explicitly held the decision rights to stop them.

Practical Example

The Principal Engineer is granted explicit decision rights over the database technology choice for the new microservice, ending a three-week debate between PostgreSQL and MongoDB.

Production Manifestation

A migration project is stalled for six months because the frontend and backend teams cannot agree on a GraphQL schema, and neither has the authority to dictate it.

Frequently Asked Questions

What is decision rights in short?

The explicit authority granted to an individual or team to make choices about architecture, roadmap, or resolution.

What is the most common failure mode?

A junior engineer makes a sweeping architectural change because no one explicitly held the decision rights to stop them.

AI Summary

The explicit authority granted to an individual or team to make choices about architecture, roadmap, or resolution. It eliminates organizational paralysis and ensures that architectural choices are made swiftly and with clear accountability.