principleLeadership & teams

Decision Rights

An explicit allocation of who may decide, who contributes, and how unresolved product choices are escalated.

Download Markdown (.md)

01What it means

Decision rights specify where authority sits for a defined class of decisions. They distinguish the person who makes the call from people who provide expertise, execute the result, or must be informed. The aim is not to centralize control, but to place decisions with the people best positioned to make and own them.[1][2]

Authority separated from contribution and execution Name one final owner while preserving expertise, implementation, and visibility
Decision ownerMakes and owns the call
Has context, authority, and accountability
ContributorsProvide evidence and constraints
Expertise informs without obscuring final authority
ImplementersExecute the result
Need clear outcome, rationale, and interfaces
Informed partiesReceive consequential updates
Do not turn every audience into an approver

The recurring decision, scope, threshold, deadline, evidence, escalation route, and rationale record should be explicit.

02Why it matters

Ambiguous authority produces circular meetings, duplicate work, delayed commitments, and decisions that are quietly reopened. Clear rights let teams move faster while preserving necessary challenge. They also make accountability fairer because ownership is established before an outcome is known.

03When to use it

Clarify decision rights when several functions share a product, approval delays recur, executives frequently override teams, or high-impact choices need formal accountability. Define them for recurring decision types rather than inventing a new structure for every minor question.

04How it works

  1. Name the recurring decision precisely, including its scope and materiality threshold.
  2. Assign one final decision owner with sufficient context, authority, and accountability.
  3. Identify required contributors and the evidence or constraints they provide.
  4. Set a deadline, escalation route, and method for recording the rationale.
  5. Review whether decisions are timely, understood, implemented, and reopened only for new evidence.

05A practical example

Example

For pricing changes, a product director owns the final decision; finance supplies margin analysis, research provides customer evidence, legal identifies constraints, and regional teams execute. Changes above a revenue threshold escalate to the executive committee under a documented timetable.

06Where it breaks

A neat authority chart cannot compensate for missing expertise, unsafe incentives, or leaders who ignore boundaries. Some decisions are tightly coupled and require joint problem-solving before one owner decides. Rights should evolve as product risk, team capability, and organizational structure change.

Common mistakes

  • Assigning multiple final decision makers.
  • Confusing the most senior person with the best decision owner.
  • Defining roles without a deadline or escalation path.
  • Reopening decisions because someone dislikes the outcome rather than because evidence changed.

07Sources

  1. Decisions: Who Does What?Bain & Company · Management framework articleDecisions: Who Does What?
  2. Decision Rights ToolsBain & Company · Management tool overviewDecision Rights Tools
View saved topics

Start typing to search titles, definitions, categories, and frameworks.