ModulesModule 3

Resolve an Execution Dispute

Chapter 3: Removing the Politics.

The book is out in early 2027. The lesson below carries the chapter, so you can start now.

Start the 9-minute lessonJump to the tools9 minute lesson, 60 minute session
  1. 1ReadThe lesson, about 9 minutes.
  2. 2UseThe 5 tools, on one real situation.
  3. 3MeetA 60-minute working session with your team.
  4. 4Mark it heldThe module is done when the session happens.

In short

Module 3 of the free Heroes Don't Scale course, by Russ Reeder, turns Chapter 3, Removing the Politics, into work. Return an execution dispute to the forum and the people who made the decision. New to VOOCS, HEAR, or the Authority Grant? The Course Glossary defines them.

Objectives

  • Return an execution dispute to the forum and the people who made the decision.
  • Make the hidden tradeoff visible against priorities the team has already agreed.
  • Write down who owns, advises, approves, resolves, and records a high-stakes decision.
  • Keep a separate, protected route for misconduct, retaliation, safety, or a concern about the assigned leader.

Lesson

About 9 minutes to read

The scene

I was in my Virginia office when a vice president at the private equity firm that owned Netrix called from New York, relaying feedback that had come through the former CEO, who still sat on the board. Our management team had agreed on the plan and the board had approved it. Now some of the original Netrix executives were challenging decisions they had already agreed to in the meeting and taking their complaints to their friend on the board. The work they had committed to wasn't getting done. I told the vice president that the back channel had to stop. It was like squeezing a tube of toothpaste with both ends open. A little came out the front as execution. Most came out the back as complaints.

The mechanism

The back channel had been the architecture of the company for years. The former CEO had built a valuable business as a technology division inside FGMK, the accounting firm it was spun out of, and made himself the center of it. Every call around the operating line reinforced the old structure. Cutting the politics had to start at the top. I asked the vice president to send execution disputes back through the operating line, to the peers and leaders who had made the decision, and to make the boundary clear to the former CEO. That could not mean closing the board's door to a concern about my own conduct. The behavior did not stop overnight, but once I had named it, each recurrence became easier to address. Disagreement continued, and we brought it into the meetings where decisions were made.

The second scene

Virtru, 2019. John Ackerly, the cofounder and CEO, brought me in at a fork: a successful email encryption business, a team building standalone document encryption for Word and Excel, and a possible larger move into government data protection. Each leader believed in the opportunity they were responsible for. Each leader made the case separately to John, and the more he listened to each argument alone, the more he became the only place where the three strategies came together. We took the executive team to the Four Seasons in Austin for three days. Each leader presented their view, challenged one another's assumptions, and worked through the tradeoffs together. The team voted. John confirmed it. The disagreement did not disappear. It became visible.

The third scene

Wells Fargo is where the same question had a different consequence. In the Community Bank, the group risk officer reported to the division's leader, Carrie Tolstedt, with only a dotted line to corporate risk. After a September 2012 regional meeting, two managers raised sales pressure with the chief risk officer, Michael Loughlin. Later, the board report says, Tolstedt told the regional executive who ran the meeting not to speak with Loughlin anymore. Between 2011 and 2016 the bank terminated more than 5,300 employees for customer-facing sales ethics violations, almost all at the branch level, while, the board report found, senior Community Bank leaders framed the problem as individual misconduct. Repair included moving 4,100 risk employees into Corporate Risk in 2016 and ending retail product sales goals. The people who could challenge the sales model needed a route the implicated business could not block.

The tool

Map one reopened decision with the Backchannel and Bypass Record. It holds what happened, not motive; the group examines the route, not the person. Put the reopened request against the agreed priorities with a Tradeoff Ranking. Write down who owns, advises, approves, resolves, and records in the Decision Rights Record. Separately, confirm the Truth Route for misconduct, retaliation, safety, or a concern about the assigned leader. Close the room on HEAR.

From your seat

If you lead the company, trace one reopened decision from the agreement to the private conversation that changed it, and name the forum it returns to. If the conversation ran through a board member or an owner, the board chair or the owners have to agree to the rule, because you cannot close that route alone. If you are in the middle and disagree with a decision, take an ordinary execution disagreement back to the people who made it; suspected misconduct, retaliation, or serious risk belongs on the protected route. If your own team is going around you, do not fight the channel alone: take the reopened decision, and the date it was agreed, to your boss, and agree on who closes the door. If people come to you privately, send execution disputes back to the room and misconduct to someone who can act. Privacy itself is not the problem. A person reporting misconduct may need it.

The line

Conflict is not politics. Going around the decision is.

Tools

Module 3: Resolve an Execution Dispute. From the free course toolkit for Heroes Don't Scale.

Backchannel and Bypass Record

Worksheet

Have the authorized decider confirm which decision stands, which commitments change, and who must be informed. If the later request came from an owner or board member, take the record to the board chair or the owners and ask them to reinforce the rule that returns execution disputes to the operating line.

  • Decision
  • Agreed forum and owner
  • Original decision and date
  • Later request or override
  • Who had authority to change it
  • Effect on commitments
  • Where the final decision is recorded

Initiative: ________________________ Owner: ________________________ Date: ____________

Tradeoff Ranking

Worksheet

When competing initiatives cannot all proceed, apply the Priority Stack from Module 2 to one contested choice: rank the outcomes against the company's stated priorities, show the scarce resource, and record which commitment changes. A person who must be heard does not automatically hold a veto. A required approval should have a reason and a deadline.

  • The contested choice
  • Outcomes, ranked against the company's stated priorities
  • The scarce resource
  • Commitment that changes
  • People who must be heard
  • Required approval, its reason, and its deadline

Initiative: ________________________ Owner: ________________________ Date: ____________

Decision Rights Record

Worksheet
  • Who owns the result
  • Who advises
  • Who approves and why
  • Who can resolve a dispute
  • What triggers escalation
  • Who records the decision
  • Where affected teams can find it

Initiative: ________________________ Owner: ________________________ Date: ____________

Truth Route

Worksheet

Do not record identifying details in a broadly shared tracker. Agree with the responsible legal, people, safety, or board function on confidentiality, access, response times, and authority to act.

  • Concern category
  • Protected reporting channel
  • Independent recipient
  • Acknowledgment and response expectations
  • Authority to pause unsafe or improper work
  • Evidence needed to resume
  • Protection against retaliation

Initiative: ________________________ Owner: ________________________ Date: ____________

HEAR

Ask four questions before closing the discussion. Honesty: what fact are we avoiding? Empathy: why does a peer believe in a different path? Accountability: who will act, by when? Respect: once we decide, how will we move forward together? Record the decision, next commitment, and check date.

Facilitator rule. If a protected concern surfaces during a session, stop the group discussion and route it. The session is not the place to investigate a live allegation.

Working Session

60 minutes

Return operating decisions to the people with context and authority while preserving an independent route for concerns that cannot safely go through the assigned leader.

People
The accountable owner, authorized decider, and affected contributors. The responsible protected-reporting function confirms its separate process without sharing identifying case details. The facilitator stops the group discussion and routes any protected concern that surfaces.
Bring
One original operating decision, later changes, relevant evidence, and affected commitments. Do not use the workshop to investigate a live allegation.
  1. 10min

    What changed after the original decision?

    Reconstruct the facts, dates, authority, and effect on work in the Backchannel and Bypass Record. Do not assign motives. When the later change came from someone who is not in the room, record what happened and who can address it instead of judging an absent person.

  2. 10min

    Was reopening justified?

    Test new evidence, changed constraints, and unclear authority. Legitimate new information is not politics.

  3. 15min

    Who owns, advises, approves, resolves?

    Name whose material view is missing. Distinguish a required approval from advice, and write who owns, advises, approves, resolves, and records in the Decision Rights Record.

  4. 15min

    Who can close this choice?

    Set the reopened request against the agreed priorities with the Tradeoff Ranking. Record the final decision or authorized escalation, its reason, the commitments that change, and who must be informed. If the change came from an owner or board member, the record goes to the board chair or the owners with the open question and a date.

  5. 10min

    Can both reporting routes work?

    Confirm how execution disputes return to the agreed forum. Separately confirm the independent recipient and fallback when a protected channel's usual recipient is implicated. Close the room on HEAR: check the facts, the pressure, the responsibility, and the respect before anyone leaves.

Leave with
One resolved or explicitly escalated execution decision with an owner and check date in the VOOCS Operating Record (the one-page record from Module 5 that every session writes into). Keep the Backchannel and Bypass Record and the Decision Rights Record together. Protected reports stay in the Truth Route, the restricted process.
Next check
Verify that receiving teams know the decision and can act. The responsible function checks the Truth Route through a controlled process, not a public discussion of allegations.
If the work still stalls
New evidence is dismissed as disloyalty, a decision changes privately again, or a protected concern must pass through the implicated leader. Silence is not proof the routes work.

Session kit: tools from other modules

Session 3 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

Worksheet

Copy 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: Where did the disagreement go?

Everyone answers all three, from their own seat. Compare the answers in the room.

New here? Take the one-minute Hero Test to name the dependency and its case first.

  1. Question 1

    Which decision made this quarter was reopened afterward in private, and what keeps that door open?

  2. Question 2

    When you disagreed with a decision, did you take it back to the people who made it, or around them?

  3. Question 3

    If people come to you privately, do you send disagreements back to the room and misconduct to someone who can act?

One action

If the decision is yours, trace one reopened decision from the agreement to the private conversation that changed it, and name the forum it returns to. If it is not, take an ordinary execution disagreement to the people responsible for the decision. Suspected misconduct, retaliation, or serious risk belongs on the protected route described in this chapter.

Evidence of Completion

  • One execution decision resolved or explicitly escalated in the VOOCS Operating Record, with its reason, the commitments that change, who must be informed, an owner, and a dated check.
  • The Backchannel and Bypass Record for that decision kept with the Decision Rights Record, naming the forum ordinary disputes return to.
  • If the private conversation ran through an owner or board member, the record sent to the board chair or the owners with the open question and a date.
  • The Truth Route confirmed with its independent recipient and the fallback when the usual recipient is implicated, with no identifying details in the shared record.

Was this module useful?