2.2 Decision Rights and RACI: The Permission Matrix

Ambiguity in authority creates organizational paralysis. When multiple people believe they “own” a decision, the result is endless debate. When no one believes they own it, the result is inaction. Both of these outcomes hinder velocity.

To operate at the required speed, Decision Rights are treated like software permissions. Every major operational action possesses a defined “Owner” (Write Access) and a “Validator” (Read/Check Access).

The Golden Rule of Authority

Authority follows Responsibility

The individual formally responsible for the quantitative outcome (P&L, quality yield metric, shipping deadline) holds the definitive decision right on how to achieve it.

The Principle: When the process breaks and requires critical intervention at 2:00 AM, the person responsible for the outcome is the person who makes the decision.

The Decision Matrix

Operational authority is distributed by Risk Class. These rights are essential for speed and accountability and must not be bypassed without a formal, written exception from Executive Leadership.

Category	Decision Trigger	Decision Owner (The DRI)	Veto Authority
Financial	Department Expense < $1k	Team Lead	None
Financial	Expense > $10k / CapEx	Department Head + CFO	CEO
Hiring	Extending a Job Offer	Hiring Manager	Bar Raiser (Peer/HR)
Quality	Stop Shipment / Line Stop	Quality Engineer	None (Safety/Quality cannot be overridden)
Commercial	Non-Standard Contract Terms	Sales Director	Legal / COO
Engineering	System Architecture / Stack	CTO / Chief Engineer	None
Supply Chain	New Vendor Approval	Procurement Head	Quality (if the factory audit fails)

Critical Control: The Quality Veto

In electronics manufacturing, the Quality Department holds the final release authority.

The Rule: Operations owns the Schedule, but Quality owns the Release.
The Scenario: The Sales team urgently needs to ship a batch of units today. The Quality Engineer notices a 0.5% spike in the failure rate during Functional Testing (FCT).
The Outcome: The unit does not ship. The Quality Department has Veto power over Revenue the moment technical standards fall out of specification.

The RACI Model (Simplified for Speed)

The RACI framework is used to define roles for specific execution projects. Because complex RACI charts frequently fail, a streamlined definition is utilized:

R = Responsible (The Doer): The individual(s) executing the daily work (writing code, configuring machines, negotiating contracts). Multiple “R”s are allowed.
A = Accountable (The Owner): The single individual who owns the final outcome. They hold the “Yes/No” authority. The Rule: There can be only ONE “A”.
C = Consulted (The Expert): People required to provide technical input before the decision is finalized. They provide expertise but do not hold a veto.
I = Informed (The Broadcast): Personnel notified of the decision after it has been made.

Common RACI Failures:

Too many “A”s: When two people are Accountable, no one is Accountable.
Using “C” as a Veto: Consulted individuals exist to provide data. When the Accountable Owner disagrees with the Consultant, the Owner makes the decision and documents the accepted risk.

Escalation Logic: Breaking Deadlocks

Professional disagreement is healthy; operational gridlock is expensive. When two functional leaders cannot agree, the following escalation path must be navigated.

Level 1. The Data Review

The Action: Both parties present a summary of the data supporting their view.
The Rule: Data supersedes Opinion. When one side has hard metrics and the other relies on intuition, the data guides the decision.

Level 2. “Disagree and Commit”

The Action: When the data is truly inconclusive, the formally assigned “A” (Accountable Owner) makes the final call.
The Rule: The dissenting party must then fully support the execution of that decision. Passive resistance undermines the team and is unacceptable.

Level 3. The Executive Tie-Breaker

The Action: A formal Decision Memo (see below) must be submitted to the CEO or appropriate Executive.
The Rule: Using the CEO as a daily referee is a failure of management alignment. This should be a rare exception.

The Standard Artifact: The Decision Memo

A written pre-read document must be distributed prior to scheduling a meeting to present a complex decision. This template ensures clarity.

Format Constraint: 1 Page Maximum.

Header: [Decision Title] | [Date] | [Accountable Owner]

1. The Context:

What exactly is the business problem? (Maximum 2 sentences).

2. The Options:

Option A: (Description + Financial Cost + Operational Risk).
Option B: (Description + Financial Cost + Operational Risk).
Option C: (Do Nothing - Always include this as the baseline).

3. The Recommendation:

Option A is officially proposed for execution because [Data Point 1] and [Data Point 2].

4. The Documented Dissent:

Department X disagrees with this approach because [Specific Reason]. This risk has been mitigated by [Specific Action].

5. The Required Action:

[Approve / Reject / Discuss]

Recap: Permission Matrix for Hardware Manufacturing

Parameter	Requirement	Condition	Action
Decision Owner (A)	Single accountable owner per task.	Final “Yes/No” authority for outcome.	Assign one “A”.
Quality Veto	Quality owns product release.	Technical standards out of spec (e.g., FCT failure rate spike).	Stop shipment; cannot be overridden.
Financial Authority	Expense approval.	< $1k: Team Lead. > $10k/CapEx: Dept Head + CFO.	Owner approves; CEO holds veto for > $10k.
Escalation (Level 1)	Resolve professional disagreement.	Inconclusive data between two leaders.	Decision based on hard metrics, not opinion.
Escalation (Level 2)	Break operational gridlock.	Data remains inconclusive.	”A” makes final call; dissenters must commit and execute.