D07 - Decision Rights Clarity
Definition
Whether everyone in your operations team knows what they can decide alone, what they need to notify about, and what they must escalate or whether decisions get made by whoever happened to be in the room.
Why It Matters
Informal coordination works at a small scale because the founder or leader is in proximity to everything.
It silently stops working as the company grows, and the failure is invisible until two teams have already duplicated six weeks of work on the same problem, or a key decision was made three different ways by three different people who each believed they were following standard practice.
The Diagnostic Question
Pick one decision that is made regularly in your operations function — a vendor communication, a customer exception, or a process deviation. Ask two team members independently: "Who decides this?"
If their answers differ, you have confirmed a D07 gap. In a team with clear decision rights, two people asked the same question give the same answer, every time.
What This Dimension Looks Like When It's Working
- Every operational role has a written Zone 1/2/3 authority map: what each person decides independently (Zone 1), decides and notifies about (Zone 2), and must escalate before acting on (Zone 3).
- A decision log captures every decision that affects more than one team, commits meaningful resources, or sets a precedent — including who made it, when, and what alternatives were considered.
- Escalation protocols specify the exact conditions that convert a Zone 2 situation to a Zone 3 one: who to contact, through what channel, and within what timeframe, removing improvisation from high-stakes moments.
- The authority map is updated whenever a promotion, team restructure, or major initiative changes the operational landscape, not only when a conflict makes the gap visible.
The Most Common False Positive
Verbal alignment is not decision rights clarity.
"Everyone knows what they're supposed to do" is the precursor statement to discovering that two people have been deciding the same category of decision in opposite directions for months.
At Anchor Growth Partners, 11 new hires developed 11 different working models of their decision authority from observation and inference. None believed they were operating incorrectly. All were, and none of this was visible from any organizational chart.
The Failure It Prevents
Knight Capital Group's trading halt took approximately 45 minutes from the first alert because no documented protocol specified who had authority to initiate the halt and under what observable conditions.
The halt decision required real-time diagnosis under escalating financial pressure — conditions under which critical decisions are not made quickly.
A pre-documented protocol with trigger conditions, named authority, and a practiced execution sequence would have produced a halt in minutes. At the rate positions were accumulating, the difference between five minutes and 45 minutes was hundreds of millions of dollars.
What This Dimension Requires And Enables
D07 requires D04 — Decision rights cannot be allocated without first defining the team structure within which they operate. Authority assignments are only meaningful when the roles they attach to are clearly defined.
D07 enables D08 — Meetings produce faster decisions when participants arrive knowing what they are authorized to decide vs. what requires escalation.
D07 enables D09 — New hires who receive a Zone 1/2/3 map on Day 1 integrate into the decision architecture immediately rather than spending their first 90 days developing their own working model through trial and escalation.
Terms
Issues
Operational Failure Archive
Industry Articles
Apply
- The Decision Log Blank Template
- The Decision Boundary Map Checklist
- From IC to Manager - The Complete Promotion Guide
Take the HQ Score assessment to see where your decision rights gaps are creating escalation load and duplicated work →