Home › Blog

Distributed Decision Rights: Because Central Committees Don’t Ship (notes from a reformed

Distributed Decision Rights: Because Central Committees Don’t Ship
(notes from a reformed bottleneck thanks to "control freaks anonymous" for having me)

I love distributed decision rights because velocity isn’t a feeling—it’s a structure. When the people closest to the problem can decide, four things happen: speed, learning, morale, and accountability. When they can’t, you get status meetings and folklore.

What it gives you (when done right):

* Latency ↓ — decisions happen where the data lives, not three org charts away.
* Surface area of learning ↑ — more bets, smaller blast radius, faster feedback.
* Talent retention ↑ — ownership is the only real perk.
* Bottlenecks ↓ — the “OK from X” anti-pattern retires itself.

The model (simple, sharp, enforceable):

* Guardrails, then autonomy: clear constraints (budget, risk tier, customer impact). Inside the rails = decide locally.
* RACI with teeth: Responsible team ships; Accountable leader defends the why; Consulted experts time-box advice; Informed gets the memo.
* Decision memos, not meetings: 1-pager: context → options → chosen path → risks → rollback. Stored in a public repo.
* Escalation by exception, not habit: criteria are explicit (e.g., >£X, Tier-2 risk, cross-domain dependency).

Non-negotiables (or it turns to chaos):

* Budget caps that actually stop spend.
* Risk tiers with pre-approved playbooks.
* Rollbacks rehearsed, not imagined.
* Metrics published weekly (see below).
* Leadership protects local decisions even when they’d have chosen differently.

How I measure it (measurement is IS KING):

* Lead time to decision (request → commit).
* % decisions made at the edge (team level vs exec).
* Reversal rate (bad calls rolled back within SLA).
* Customer-visible cycle time (idea → value).
* Escalation rate (should trend down).

Common failure modes (and fixes):

* Shadow centralization: “just run it past us” = veto by calendar. → Fix: auto-approve after 48h silence.
* Ambiguous risk: everything becomes Tier-3. → Fix: crisp tier rubric with examples and dollar limits.
* Decision theater: meetings with no owner. → Fix: memo-first; no memo, no meeting.
* Local maxima: teams optimize for themselves, hurt the whole. → Fix: 3 company-level North Stars (SLO, cost/unit, NPS) everyone shares.

Playbook to start (30 days):

1. Write the rails: budgets, risk tiers, escalation criteria, rollback SLA.
2. Pick 3 pilot teams; grant decision rights within rails.
3. Introduce 1-page decision memos + public repo.
4. Publish the 5 metrics weekly; celebrate reversals that saved time/money.
5. Leaders practice the hardest skill: defend a decision you didn’t make.

Tattoo line: Centralize principles, decentralize decisions, standardize interfaces, measure outcomes.

Distributed decision rights aren’t anarchy. They’re speed with receipts. And receipts are how you win budgets—and keep your Saturdays.

— Scott G

#Leadership#ProductOps#DevOps#DecisionScience#OrgDesign#Autonomy#SpeedWithGuardrails
The Probably Fine Daily

Threat intelligence every morning — new victims, new groups, what matters, in plain English. Free, with receipts.

Subscribe to the Daily →

View the original on LinkedIn ↗

← All writing