ModulesModule 8
Make the Authority Agreement Hold
Chapter 8: Ownership Without Theater. This module deepens the Ownership line of the record. Module 1 asked you to stop holding decisions that belong to others. This module is about what happens after you hand them over: authority can be pulled back from above, withheld from the side, or never granted at all.
The book is out in early 2027. The lesson below carries the chapter, so you can start now.
- 1ReadThe lesson, about 9 minutes.
- 2UseThe 4 tools, on one real situation.
- 3MeetA 60-minute working session with your team.
- 4Mark it heldThe module is done when the session happens.
In short
Module 8 of the free Heroes Don't Scale course, by Russ Reeder, turns Chapter 8, Ownership Without Theater, into work. By the end of this module you will have compared the owner's and the sponsor's description of the same authority against the five elements of the grant, using one blocked dependency or contested decision.
Objectives
- By the end of this module you will have compared the owner's and the sponsor's description of the same authority against the five elements of the grant, using one blocked dependency or contested decision.
- You will have bound one dependency with a commitment, a date, and an acceptance condition.
- And you will have logged any material override, so the next mandate conversation runs on evidence.
Lesson
About 9 minutes to readThe scene
At Netrix, we were presenting the strategic plan when the controlling shareholder's lead partner started rewriting it in front of us. He had already agreed to the strategy we were executing. Now he went through everyone's plan line by line and changed it on the fly, without working through the people, countries, and budget constraints that had produced it. I watched their faces fall. They had signed up to bring six companies together into one division. The plan was changing in front of them without a matching discussion of what would have to move. He had the power to issue the instructions. They still had to deliver the result. The target stayed. The decisions moved out of their hands.
When that happens, people can start trying less. They may build a plan underneath the plan, nod in the meeting, and then go back to what they intended to do. Or they stop moving until they get another instruction. Neither response solves the problem. The change needs to be made explicit, with its consequences and its owner.
The mechanism
Authority can be withheld from the side as well as pulled back from above. At XTIUM, the CFO was not in all the board meetings where the numbers she was responsible for were reviewed and decided. Financial planning and analysis did not report to her. It reported to the Corporate Development president. The title said she owned the number. The structure said someone else did. And she had stopped raising it. I call it familiar pain. A problem becomes so familiar that people stop raising it, even though it still costs them. It is like a bad back: after years of discomfort, you may stop mentioning it. Familiar does not mean resolved.
She knew the system cold. Replacing her would not close the gap between her title and her authority. So I asked her directly: "Do you want the CFO job? Because I'm going to give you the authority you never had." She did not hesitate. Then I moved to align financial planning and analysis under her, and the board pushed back. Over about a year, the meetings, the information, and the decisions I could move came under her authority. The forecasting function was the piece I could not move. I had promised her authority that turned out not to be mine alone to grant. That is the lesson I carry: put authority in writing before accepting accountability whenever you can, and when you inherit a gap, make it explicit as soon as you find it.
Authority can also never be granted at all. By March 2014, according to GAO, CMS had obligated $840 million across 62 contracts and task orders for Healthcare.gov and its supporting systems. That was a contracting footprint, not a completed operating system. On launch day, October 1, 2013, the administration reported 4.7 million unique visitors in the first twenty four hours. The service launched before it could reliably handle enrollment. GAO found that CMS was unclear about who could approve additional work and launched without verification that the site met performance requirements. Module 7 asked who tests the whole. Here the question is who held the authority to make the separate contractors deliver one working service before launch. Contracts do not become an operating system by themselves. The rescue established a central command and twice daily war room meetings, and by December 1, 2013, CMS reported an error rate below 1 percent.
The tool
The Authority Grant: one page, five elements. Before holding someone accountable, ask them to explain the decisions they can make without further permission, and compare their answer with the sponsor's. A gap between the two answers is a finding about the grant, not about the owner. The Required Voice Matrix, the Integration Owner Charter, and the Override Log build on the same roles.
From your seat
If the authority is yours to grant, write it down for one owner and announce it where the affected teams can see it. Then stop rescuing through override. When the owner stays inside the agreed boundary, coach rather than replace the decision. If you carry a number decided in rooms you are not in, write what your current authority lets you deliver and what it prevents, and take that to whoever can close the gap. If everyone asks you and nobody includes you, notice what you have stopped raising because the arrangement became normal. That silence is the finding.
The line
Ownership without authority is theater.
Tools
Module 8: Make the Authority Agreement Hold. From the free course toolkit for Heroes Don't Scale.
Authority Grant
WorksheetBefore holding someone accountable, ask them to explain the decisions they can make without further permission, and compare their answer with the sponsor's using one blocked dependency or contested choice. Close any gap in writing and confirm it with affected teams. The grant has five elements: the decisions delegated, budget and staffing authority, tradeoff authority over competing priorities, standards and constraints, and an escalation path with a response deadline. If the sponsor lacks the authority, name who can grant it and the decision deadline. If that authority will not be granted, record what the current arrangement can and cannot deliver. One owner does not mean one person does all the work. It means someone can coordinate dependencies and obtain a binding decision when authority runs out.
- Outcome and accountable owner
- Decisions delegated, and decisions reserved for others
- Budget and staffing authority, including the information and meeting access the owner needs and the contributors whose work is required
- Tradeoff authority over competing priorities
- Standards and constraints
- Escalation path with a response deadline: who hears it and how fast they must answer
- Backing: sponsor who announces and backs the grant, where affected teams can see it, review date
The grant for a unit. The same grant serves a local business, division, or region. Write it for the unit as you would for one owner: the local outcome, the decisions it keeps without central approval, the shared obligations it must meet, its resource boundaries, its dependencies on the parent, the escalation path, and the conditions for revisiting the arrangement. The Backbone and Autonomy Matrix in Module 10 holds what must be common; this grant holds what stays local. Keep the two in one record.
Initiative: ________________________ Owner: ________________________ Date: ____________
Required Voice Matrix
WorksheetUse it to identify whose knowledge the decision needs. Include the teams receiving the work and people who understand its risks. Distinguish input, approval, and ownership. If the Decision Rights Record from Module 3 already names these roles, add only the input dates and the response to objections here. Silence is not consent when the person never received the information or a fair opportunity to respond. A person who must be heard does not automatically hold a veto.
- Decision
- Expertise or affected group
- Person providing input
- Input due date
- Required approval, if any
- Owner's response to a material objection
Initiative: ________________________ Owner: ________________________ Date: ____________
Integration Owner Charter
WorksheetFor work crossing functions, give the owner a defined outcome, authority over shared priorities, access to the right people and information, and a sponsor who can resolve reserved decisions. Name dependency owners and their commitments. Calling someone the integrator does not grant them control over another executive's budget. A collection of contracts is not a substitute for this operating structure. Before the war room stops meeting, decide which decisions belong in normal operations and who will own them.
- Shared outcome
- Integration owner
- Dependency and owner
- Required handoff and date
- Acceptance test
- Tradeoff authority
- Reserved decision
- Sponsor and resolution deadline
Initiative: ________________________ Owner: ________________________ Date: ____________
Override Log
WorksheetRecord material overrides. Material means the change moved the target, the date, the resources, or the risk. The question is whether an intervention teaches the system or quietly replaces it. Review recurring overrides with the sponsor, or with the person the overriding leader answers to when the sponsor is the one overriding. When the person overriding is the sponsor, the board, or a controlling shareholder, the log becomes the evidence for the mandate conversation: keep the agreed plan, change the target and resources, or accept a different risk, with the decision recorded. Protected concerns stay in the Truth Route from Module 3.
- Original decision
- Overriding authority
- New evidence or reason
- Revised decision
- Effect on commitments
- Owner informed
- Coaching or system change required
Initiative: ________________________ Owner: ________________________ Date: ____________
Working Session
60 minutesTest whether the person carrying the outcome can obtain information, resources, and binding decisions across functions. A signed grant is useful only if the organization honors it.
- People
- The accountable owner, the sponsor with authority over the relevant boundary, dependency owners, and the people whose information or risk challenge is required.
- Bring
- The VOOCS Operating Record, delegation and budget limits, one blocked dependency or recent override, and the information each participant can access.
- 10
Do owner and sponsor describe the same authority?
Have each explain one contested decision. Compare the answers against the five elements of the Authority Grant: decisions delegated, budget and staffing authority, tradeoff authority over competing priorities, standards and constraints, and the escalation path with its response deadline. A gap between the two answers is a finding about the grant, not about the owner.
- 10
Which dependency sits outside that grant?
Name who can commit the people, money, or handoff. Record the commitment, its date, and its acceptance condition in the dependency and handoff fields of the Integration Owner Charter.
- 15
What information and voice does the decision require?
Use the Required Voice Matrix to distinguish advice, approval, and ownership. Confirm access and a fair response period. Accountability needs a seat where your number is decided, clear decision rights, and support to use them.
- 15
Who resolves a conflict, and by when?
For cross-functional work, use the Integration Owner Charter. Respect board and other reserved decisions; route them to the actual authority.
- 10
What changes when a senior leader overrides?
In the Override Log, record the reason, the authority, the owner notification, and the effect on targets, dates, resources, and risk. Update the grant if the boundary has changed. If the means of delivering a commitment have moved, reopen its date; the original owner should not quietly carry an unchanged date.
- Leave with
- An agreed Authority Grant and binding dependency commitments in the VOOCS Operating Record. Record information access, response deadlines, sponsor backing, and any material Override Log entry.
- Next check
- Use the next real boundary decision or handoff. Verify that the information arrived, the authorized person responded, and affected teams followed the decision. Escalate a broken agreement with its business consequence.
- If the work still stalls
- The sponsor cannot grant the authority, silence becomes approval, or another leader changes the plan while leaving the target untouched. Record what the current arrangement can and cannot deliver, then renegotiate the mandate, change the role, or leave it, rather than leaving the owner accountable for a result they cannot steer. Keep protected concerns and individual performance matters in their confidential routes.
Session kit: tools from other modules
Session 8 uses this tool from other modules. It is here so you can run the session from this page. Print worksheet prints it with the session.
From Module 5: Build the Operating Loop and Transfer Judgment
VOOCS Operating Record
WorksheetCopy this record for one initiative. Use role titles while designing the plan, then name the actual people before making a live commitment. Link to detail only where it supports a decision. Leave irrelevant fields out. If an answer is unknown, or the owner and sponsor give different answers, name who will resolve it and by when. Start with one recurring problem so the team can test the whole arrangement before expanding it; the book's illustrative locked-accounts record in Chapter 5 shows one filled in.
Header fields:
- Initiative
- Outcome owner
- Sponsor
- Date and next review
- Facilitator and recorder
Vision: What result are we building toward, and who benefits? Why does it matter now? Which priority does it serve? What are we choosing not to do?
Outcomes: What is the baseline, target, and due date? Which quality or risk conditions must hold? What evidence will show the result, and who will verify it?
Ownership: Who owns the outcome? Which decisions and resources can they control? What do dependency owners commit to deliver, and who resolves it when their other priorities compete with this work? What is reserved for someone else, and how quickly must that person respond?
Cadence: When will we review the evidence? Who will do what next, by when? Which decision must close before the work can proceed? Where will we record the decision and its result? If a commitment slipped, what condition changes before the new date?
Systems: What repeatable workflow, standards, and controls support the work? Where is the shared source of truth? Who has the access, training, and practice to provide backup? What evidence shows they can carry the work and recognize an exception without waiting for the original hero?
Decision check. Before closing, confirm: decision and reason; authorized owner; next commitment; due date; evidence and receiving person. If a gap remains, record its exact question, decider, evidence owner, and return date.
Module 7 deepens the Outcomes line and Module 8 the Ownership line. Every other tool writes into this same record, and the 90-Day Install follows it.
Initiative: ________________________ Owner: ________________________ Date: ____________
The Hero Test for this chapter
THE HERO TEST: Who holds the authority?
For the person at the top
Can someone you hold accountable name, without notes, the decisions they can make without you? Do your lists match?
For the manager in the middle
Are you in the room when your number is decided? When the plan changes above you, does the target change too?
For the person the company waits on
If everyone asks you and nobody includes you, what have you stopped raising because the arrangement became normal?
One action
If the authority is yours to grant, write it down for one owner: the decisions, budget, people, tradeoffs, standards, and escalation deadline. If it is not, write what your current authority lets you deliver and what it prevents, and take that to whoever can close the gap. Apply the same test to the support example. The support manager can assign work and approve training time. The security owner controls the named exceptions. If the backup loses access or the training time is reassigned, record who changed the condition and what that does to Friday’s commitment. The original owner should not quietly carry an unchanged date after the means of delivering it have moved.
Evidence of Completion
- One Authority Grant is agreed between owner and sponsor, with all five elements filled, the information and meeting access named, and the sponsor's backing and review date recorded where affected teams can see it.
- One dependency outside the grant is bound: who commits it, by what date, against what acceptance condition.
- Where the work crosses functions, an Integration Owner Charter names the dependency owners, the tradeoff authority, and the sponsor's resolution deadline.
- Any material override since the last review is in the Override Log, with the owner informed and the grant revised if the boundary changed.
- Where the authority cannot be granted, the record states what the current arrangement can and cannot deliver, who can grant it, and the decision deadline.
- The next real boundary decision or handoff is chosen as the next check.