---
id: "claim-single-accountability"
type: "claim"
source_timestamps: ["§ How Decision-Rights Tools Are Meant to Work"]
tags: ["accountability", "efficiency"]
related: ["concept-arci-framework"]
confidence: "high"
testable: true
speakers: ["Lindy Greer", "Jennifer Jordan", "Maxim Sytch"]
sources: ["governance"]
sourceVaultSlug: "hbr-seg-governance"
originDay: 7
articleStem: "hbr-sig-48-decision-rights"
sourceUrl: "https://hbr.org/2026/07/what-companies-get-wrong-about-decision-rights"
sourceTitle: "What Companies Get Wrong About Decision Rights"
---
# Multiple Accountable Parties Cause Failure

**Only one person should ever hold the 'Accountable' role** for any given decision. Assigning multiple people to this right *inevitably* invites power struggles and causes execution delays. The Accountable person must be the singular final decision-maker and the leader of the decision team.

This claim anchors [[concept-arci-framework]] and motivates [[action-reorder-raci-to-arci]]; the contested-ownership tie-breaker is [[framework-raci-conflict-resolution]].

**Confidence: high · testable.** *Enrichment:* the 'single Accountable' norm is **strongly supported** across mainstream project-management guidance (CIO, Pipedrive, Monday.com, and Indeed all recommend exactly one 'A' per task). The causal language ('inevitably invites power struggles') is directionally supported but relies on qualitative cases, not quantified data. **Counter-perspective:** some practitioners argue **shared accountability** can work in highly interdependent settings (agile teams, joint ventures); the 'only one A ever' rule may be too rigid there, though it remains dominant best practice.


## Related across articles
- [[framework-ovis]]
- [[question-ai-accountability-d7]]
- [[concept-ai-fiduciary-duty]]