Why This Matters
The #1 reason "Radical Autonomy" fails is ambiguity. When people don't know the boundaries of their power, they default to seeking permission. This clogs the founder's calendar and frustrates high performers. A Decision Rights Matrix doesn't take away power—it distributes it with extreme clarity, allowing the whole organization to move at the speed of the market.
The Core Framework: The A-R-P-A Model
Forget the complex RACI charts. For founders, we recommend the ARPA model for decision rights:
- A stands for AUTHOR (Owner): This person makes the final call. There is only ever ONE Author per decision. They don't need permission, only input.
- R stands for REVIEWER (Advice): These people *must* be consulted before the decision is made, but they do NOT have veto power. If the Author disagrees with them, the Author still moves forward.
- P stands for PRODUCER (Execution): These are the people who will carry out the decision once it's made. They need to be informed immediately.
- A(2) stands for APPROVER (Veto): This is usually reserved for the Founder or CHRO for "Type 1" (irreversible) decisions only. Most operational decisions should have NO Approver.
Pro-Tip: The "Veto Tax"
If you insist on being the "Approver" for a team's decision, you must pay the "Veto Tax": You are now 100% responsible for the outcome if your veto leads to a failure. This realization helps founders delegate more effectively.
Building Your Matrix: The 3-Step Implementation
Step 1: Categorize Your Decisions
List your top 20 recurring decisions. Group them into "Operational" (low risk, high frequency), "Tactical" (medium risk, monthly), and "Strategic" (high risk, rare). Operational decisions should be fully delegated to the teams with ZERO founder involvement.
Step 2: Assign the "Author" Rights
For each category, name one role as the Author. Crucially, move the Author right as close to the "Edge" of the company as possible. The person closest to the customer should be the Author of customer-facing decisions.
Step 3: Publish the "Invisible Rules"
Put your Decision Rights Matrix in a public place (Notion, Wiki, or a physical wall). When someone asks for your permission on something they are the "Author" of, your only response should be: "Check the Matrix. You have the right. What do you think?"
Common Delegation Pitfalls
The "Reviewer" Bloat
Adding too many Reviewers turns a decision into a consensus-seeking committee. Limit Reviewers to a maximum of 3 people who have unique, documented expertise.
The "Post-Game" Second-Guessing
If you give someone the right to decide, you must accept their decision even if it's not the one you would have made. Second-guessing after the fact destroys trust and makes the matrix useless.
Key Takeaways
- Clarity is the prerequisite for autonomy.
- The ARPA model simplifies complex authority structures.
- Founders should aim to be "Authors" of strategy, but "Reviewers" of operations.
- Decisions should be made by those closest to the information.