Why your senior leadership team keeps re-litigating the same calls (and the protocol that fixes it)

Your SLT agreed on Monday. By Wednesday they've diverged. By Friday Engineering and Product are building two different things.

Both versions are consistent with what was said in the room. Neither is what was meant. Two weeks in, the CEO walks into a status review and finds out the call they thought was made three weeks ago is being made again. Different room, same people, slightly different framing, opposite outcome. Then it gets made a third time. Each round costs the SLT two hours and the org two weeks of misaligned shipping. The CEO ends up as the silent escalator who has to break ties on calls they thought were closed.

I've worked with senior leadership teams at NHS England Bookings & Referrals and the Department for Education's Teacher Services. I sat on the senior leadership team at HomeX through a $90M Series A. I've coached over 100 senior leaders, many of them inside SLTs going through this exact pattern. The pattern is the same in every team. The team is full of capable, well-intentioned people. They like each other. They want the company to win. And the calls keep coming back.

The reason is not personality. It's not communication style. It's not “we need a better team offsite.” The reason is alignment without protocol. When an SLT makes a decision in a room with five people, four of them walk out with a slightly different version of what was decided. Without a protocol that locks the call in writing, those four versions drift. Two weeks later the drift is a divergence. Three weeks later the divergence is a public re-debate.

This article covers why re-litigation happens, the 7-minute decision protocol I run with SLTs, and what changes after four to six weeks of using it. If your team has had the same call surface three times in a quarter, this is the fix.

The 3 reasons re-litigation keeps happening

Three things break before a decision starts coming back. They're different problems. Most SLTs have all three at once.

Decision rights weren't clear. When a call gets made in an SLT, every person in the room is in one of four roles for that specific call. Decide. Consult. Inform. Veto. Most rooms don't name the roles. So everyone behaves like they're in Decide mode, which means everyone thinks they're agreeing to a final answer when half of them are actually consulting. Two weeks later the people who thought they were consulting raise the call again, because in their head they were never the ones who made it. The room feels democratic. The output is ambiguous. This pattern is well documented in the RACI literature and most SLTs nod at it and skip the actual work of assigning roles per decision.

The trade-offs weren't named. A decision is a choice between options where each option costs something different. If the costs aren't named, the SLT agrees on an option without agreeing on what they're giving up. Two weeks later the cost shows up. Now half the team thinks “we never agreed to that” because they didn't see the trade. The Director of Engineering and the Director of Product both said yes to “we'll go with vendor B.” One was saying yes to the integration speed. The other was saying yes to the price. Neither saw the third trade-off, which was that vendor B locks you in for three years. When the lock-in becomes real, the call comes back.

The decision criterion wasn't owned. Every good decision has a criterion. The thing that, if it changed, would flip the call. Most SLT decisions don't have a named criterion. So when reality nudges the inputs (a customer churns, a competitor ships, a budget shifts), no one knows whether the call still holds. Without a named criterion the call is permanently soft. Anyone in the room can re-open it later by pointing at any change in the world and saying “circumstances are different now.” With a named criterion the call holds until the criterion actually flips. Most CEOs I work with have never named a decision criterion in their life. Their SLTs definitely haven't.

These three failures are stackable. Most teams have decision rights ambiguity plus unnamed trade-offs plus no criterion. The result is that 60 to 80 percent of SLT calls are soft. Soft calls come back. Hard calls stay made.

The 7-minute decision protocol

The protocol I run with SLTs takes seven minutes per decision. Yes, seven. Most SLTs spend 35 minutes debating a call and then 90 minutes a month later re-debating it. The protocol takes the 35 minutes down to 7 and the re-debate down to zero.

Here's the protocol. Print it. Put it on the wall. Run it on the next call.

Minute 0 to 1. Name the decision in one sentence. Not the topic. The decision. “Should we go with vendor A or vendor B for the customer data platform” is a decision. “Customer data platform” is a topic. Topics generate conversations. Decisions generate outcomes. If you can't write the decision in one sentence with two or three concrete options, you're not ready to decide. Stop and reframe.

Minute 1 to 2. List the trade-offs. 3 to 5 maximum. In writing. What does each option give up? Speed versus cost. Lock-in versus flexibility. Integration depth versus vendor risk. Write them down where everyone can see them. The act of writing forces the implicit costs into language. People who agreed in their heads to different versions of the call now see the same version. This step alone resolves about 30 percent of disagreements before they happen.

Minute 2 to 3. Assign Decide / Consult / Inform / Veto roles per stakeholder. For this specific decision, who decides? Usually one person, sometimes two. Who needs to be consulted because their context affects the call? Who needs to be informed because the outcome affects them? Who has a veto on the basis of risk, regulation, or strategy? Name the roles out loud. Write them down. The Director of Engineering is Consult. The CFO is Veto. The Head of Product is Inform. The CPO is Decide. Now everyone knows what their voice in the room costs and what it doesn't.

Minute 3 to 5. Surface the decision criterion. The thing that would flip the call. “We're choosing vendor B because integration time matters more than three-year cost.” That's the criterion. If integration time stops mattering (because the integration is done) or if three-year cost shifts dramatically (because the contract terms change), the call should re-open. Otherwise it stays made. Write the criterion next to the decision. This is the single most powerful step in the protocol because it converts the decision from a feeling into a falsifiable claim.

Minute 5 to 6. Name reversibility. Is this a one-way door or a two-way door? Jeff Bezos's two-way doors framing is the cleanest version. Two-way doors get decided fast and tested. One-way doors get decided slowly and thoroughly. Most SLT debates last too long because the team treats every call as a one-way door. About 70 percent of calls are two-way. Naming reversibility tells the team how much weight the decision actually carries.

Minute 6 to 7. Commit. Assign the artefact owner. One person owns the 1-pager that captures the decision, the trade-offs, the roles, the criterion, and the reversibility. That 1-pager travels. It goes in the SLT shared folder. It gets sent to anyone affected. It's the thing the team points at three weeks later when someone tries to re-open the call. The artefact owner is usually a Chief of Staff, a senior PM, or a senior EM. Whoever they are, they have 24 hours to ship the 1-pager.

Seven minutes. One artefact. One decision that stays made.

Why most SLTs skip the protocol

Most senior leadership teams I've worked with have heard of decision protocols. Most have rejected them. The reason is they feel slow. The reason they feel slow is the wrong frame.

Compare 7 minutes of protocol against 35 minutes of unstructured debate plus 90 minutes of re-debate three weeks later plus the cost of two weeks of misaligned shipping. The unstructured version is much, much slower. It just feels faster in the moment because the cost is hidden until later.

There's also a status thing. Senior leaders are expected to be decisive. Running a protocol feels like admitting you can't just decide. The opposite is true. The protocol is what makes you decisive. Without it, you're agreeing to ambiguity and calling it agreement. Marty Cagan's writing at SVPG makes the same point about product teams. The teams that ship the cleanest decisions are the ones with the most explicit decision discipline, not the ones with the most charismatic decision-makers.

The third reason teams skip it is that they think their team is “different.” Strong relationships, mutual trust, long history together. None of that helps. Trust accelerates conversation. It does not prevent decision drift. Drift is a structural failure, not a relationship failure. The best SLTs I've worked with use protocol precisely because they trust each other. Protocol is what trust uses to scale.

The protocol is not slow. Re-litigation is slow. The protocol is what stops re-litigation.

What changes after 4 to 6 weeks

When an SLT runs the protocol on every decision worth recording for four to six weeks, three things shift.

First, decisions stick. The Wednesday divergence stops. When someone tries to re-open a call, the artefact owner pulls the 1-pager and points at the criterion. The team checks whether the criterion actually flipped. Usually it didn't. Sometimes it did, and the call gets reopened cleanly with a new round of the protocol. Either way, the team is debating a known artefact instead of relitigating a vibe. The CEO stops being the silent escalator. The two-hour weekly cost of revisiting closed calls drops to near zero.

Second, the SLT room changes shape. People come in prepared. They bring three options and a recommended trade-off, not “let's discuss customer data platforms.” Meetings get shorter and sharper. Prep time gets longer because the meeting demands it. Total time spent on the decision goes down because the protocol forces clean inputs.

Third, the team's reputation in the rest of the org changes. People downstream of the SLT (engineering, product, design, customer success) stop describing the leadership as “always changing their minds.” Because the SLT is now changing its mind less, and when they do, they tell the org what changed in the criterion. The trust loop tightens. Roadmaps hold. Quarterly plans hold. The CEO's calendar opens up because the SLT is making the calls the SLT was hired to make.

This isn't subtle. SLTs that run the protocol consistently feel different in week six than they did in week one. The change is visible from the outside.

A specific case

An SLT I worked with was a six-person team at a Series B SaaS company. Smart, friendly, capable. They had the same problem most SLTs have. Decisions made in Monday's meeting kept resurfacing in the next Monday's meeting. Sometimes the third Monday's meeting too. They were burning roughly two hours a week on revisiting calls they thought were closed.

We ran the protocol on the next twelve decisions. The CEO ran the timer. Each decision got the seven minutes. The CFO and the Head of Product pushed back hard the first week. By week three they were the ones running it. The artefact owner role rotated. The 1-pagers piled up in a shared folder.

After three weeks the team measured. Of the twelve decisions, only two had been re-opened. Both had clean criterion flips that justified reopening. The other ten were holding. The two-hour weekly cost of re-litigation had dropped roughly 80 percent. The CEO got four hours back per week. The Head of Product told me later it was the single biggest change to her week of the year.

The protocol didn't change the team. It changed what they shipped.

What to do this week

Three actions. None of them need budget.

Pick the next decision your SLT is going to make this week. Not the big one. The third or fourth one. Something low-stakes enough that running a new protocol on it won't feel high-risk. Run the seven minutes. Time it. Use a stopwatch.

Write the trade-offs in writing during the meeting. On a whiteboard, in a doc, in the chat. Anywhere visible. The act of writing them is what does the work. Don't skip this step. It's the cheapest one and the most powerful.

Send the 1-pager to everyone in the meeting within 24 hours. The artefact is what makes the call stick. No artefact, no stick. The 1-pager doesn't need to be pretty. It needs to be specific.

Take the diagnostic if you want to see which of the four senior-leader archetypes you carry into the SLT room. Most re-litigation patterns trace back to two archetypes clashing without protocol. Knowing your blend helps a lot.

Read the article on decision throughput for the broader frame on why senior decision-making is the constraint in scaling teams right now. The protocol is what you do once you've named the throughput problem.

The call your SLT can't make alone

If you've recognised your team in this article, the next step is probably not buying SLT coaching. It's running the protocol on one call this week and seeing what changes.

If you want help installing it across the SLT, I run a 30-minute discovery call. You bring one decision your team has had to make twice. We work the protocol live. By the end you'll either have made the call cleanly or you'll know exactly which of the three drop-points your team has. No pitch. Book at /work-with-me.

The protocol is small. The compounding is not.