Decision Rights Ambiguity Diagnosis¶

Why It Matters¶

Organizations function through decisions. When decision rights are clear, decisions happen efficiently even if imperfectly. When decision rights are ambiguous, several predictable pathologies occur: multiple people make conflicting decisions creating chaos; everyone defers to everyone else creating paralysis; people spend more time negotiating who decides than making decisions; and actual decisions get made by whoever acts first or loudest rather than whoever is appropriate. This ambiguity often arises from matrix structures, cross-functional initiatives, cultural norms of consensus, or legacy practices that outlive organizational changes. Making decision rights explicit eliminates friction and clarifies accountability.

The Key Move¶

For any decision that's creating conflict or delay, explicitly ask: "Who has the authority to make this decision? Who believes they have authority? Who has veto power? Who must be consulted versus informed?" Map what each party believes the decision rights are. If there's disagreement or uncertainty, you've found decision rights ambiguity. Resolution requires explicit allocation: use frameworks like RACI (Responsible, Accountable, Consulted, Informed) or simpler "one person decides after consulting these people." Make the allocation visible and binding.

Classic Application¶

Product feature prioritization conflicts. Engineering believes they decide technical feasibility and implementation approach. Product management believes they decide customer priority and roadmap sequence. Design believes they decide user experience and interface choices. Sales believes their customer commitments determine priorities. Each has legitimate partial authority, but boundaries are unclear. Result: features get built that don't match designs, designs ignore technical constraints, roadmaps commit to impossible timelines, and everyone blames everyone else. Resolution requires explicit decision rights: PM decides what problem to solve and success criteria; Design decides how users interact; Engineering decides implementation approach within constraints; Sales has input but no decision authority. Conflicts escalate to a designated arbiter.

Surprising Application¶

Household division of labor disputes. Couples experience recurring conflict over tasks like cleaning, cooking, or childcare. The conflict isn't about whether tasks should happen—both agree they should—but about who has authority to decide when, how, and to what standard they happen. One partner believes they get to decide cleaning standards since they "care more about it"; the other believes equal partnership means equal decision authority. The ambiguity creates resentment: tasks undone because each expects the other to decide, or tasks done differently than one partner wants because they didn't realize they lacked authority to set standards. Explicit decision rights allocation ("you decide cooking, I decide cleaning, we both meet minimum standards for shared spaces") eliminates ambiguity.

Failure Modes¶

Over-specifying decision rights creating bureaucracy—some ambiguity enables flexibility and adaptation. Allocating decision rights without corresponding information or expertise—authority without knowledge creates bad decisions. Ignoring informal power that overrides formal decision rights—making formal allocations that informal organization contradicts. Creating decision rights that don't align with incentives—giving authority to people who aren't affected by outcomes. Assuming decision rights allocation solves all conflict—sometimes disagreement is substantive, not procedural.

Go Deeper¶

Bossidy & Charan, Execution: The Discipline of Getting Things Done (2002), Chapter 6; Rogers & Blenko, "Who Has the D? How Clear Decision Roles Enhance Organizational Performance," Harvard Business Review 84(1), 2006.

Friction - Military Strategy & Strategic Thinking: A Map of the Territory