How to Handle an Executive Override Without Losing the Room15 min read

The scoring is done and the top 5 are agreed. Then a VP moves number 11 to the top of the list.

What nobody in the room can answer:

• What actually triggered the change
• Who was entitled to make it, and whether that was agreed beforehand
• What evidence sat behind it
• Whether any of it gets written down

By the end of the meeting, 11 has a budget. The idea that ranked 2nd has moved to next quarter.

Expect overrides wherever ideas get scored and a hierarchy exists. What the room loses is the rule behind the call, not the ranking.

No scoring model removes them. Written in advance, an exception path is what lets you overrule the scoring and still keep the room.

What Counts as an Override

An override is a decision that reverses or bypasses what the agreed process produced, made by someone with the standing to do it.

That definition rules a lot of things out. 3 moves get called overrides when they’re something else, and the confusion gets expensive fast.

The distinction matters operationally. Call a tie-break an override and the room hears that the rubric failed.

Teams then start engineering the rubric to prevent a problem that never happened, which adds criteria, adds scoring time, and fixes nothing real.

The reverse error is the one to watch. A real override gets logged as a re-score, and the exception disappears into the process it bypassed.

Count them. As a rule of thumb, a year’s worth of genuine overrides should fit on 1 page.

Why the Missing Explanation Outlasts the Decision

A group can absorb a decision that goes against it. The part that lingers is a decision it can’t reconstruct.

Kim and Mauborgne’s fair process work names 3 principles:

1. Engagement, meaning people get to give input and to argue with each other’s reasoning
2. Explanation, so everyone affected understands why the final call went the way it did
3. Expectation clarity, meaning managers state the new rules clearly once the decision is made

Explanation is the one this problem turns on. The research on why sits next door, in the justice literature.

A 2001 meta-analysis of general organizational-justice research puts procedural justice and trust among the larger corrected correlations, at .61 across 24 studies and 4,522 people.

That’s pooled from lab and field studies across 25 years. It can’t show that adding a rationale creates trust.

Kim and Mauborgne put it in one line: “An explanation allows employees to trust managers’ intentions even if their own ideas have been rejected.”

Trust survives the rejection, provided the reasoning travels with it. The room gives up the outcome and gets the reasoning.

What the Room Learns From Silence

The cost doesn’t land in that meeting. Disengagement is quiet, so the signal shows up later.

Four accounts of what silence actually looks like:

1. In an exploratory study of employee silence, 85% of the 40 employees interviewed had felt unable to raise an important issue with a supervisor
2. Of those, 74% said colleagues who knew about the same issue were also uncomfortable raising it
3. Detert and Edmondson, discussing their research on employee voice: “No news is not good news, from the point of view of senior management”
4. PMI’s account of pet projects, on people who object: they “will either stop voicing their opinion or stop attending meetings altogether”

Discomfort spreads sideways, which is why the 2nd finding lands harder than the 1st. One quiet person is a mood, a quiet room is a norm.

None of that research studied overrides. What it describes is a room that has learned not to bother – that lesson only needs teaching once.

Expect the cost to surface in the next campaign’s submission numbers, not in the meeting where the override happened.

The Overrides That Are Actually Right

A ranked list carries the authority of a fact. It’s an output of choices somebody made about weights.

Cambridge’s Institute for Manufacturing is blunt about weighting and rating methods in its design guide: weightings and ratings are subjective and arbitrary, so the quantitative answer is too.

So scoring is still worth doing, because it forces the criteria into the open. It just doesn’t settle anything on its own.

A good override and a bad one can look identical from outside the room. What separates them is the evidence and the record.

Four Reasons That Hold Up

So a ranking hasn’t produced a fact. The question is which departures from it survive scrutiny:

• Information the group didn’t have when it scored
• A strategy change the rubric predates
• A constraint no score can express, such as a regulatory or contractual blocker
• A portfolio-shape argument, where the top five all turn out to be the same bet

MIT Sloan Management Review offers an analogy for the 1st one: unless a deal-breaker fact turns up, the final call should wait until all key attributes are scored.

The same piece argues that the accuracy of intuitive judgment improves when a global evaluation is delayed until the end of a structured process.

A legitimate override respects that discipline. It arrives after the scoring, carrying something the scoring couldn’t see.

Take a hypothetical case: the CFO knows about a supplier change that hasn’t been announced, and it makes the 2nd-ranked idea unbuildable.

The call holds up and the reasoning can’t be shared yet. That combination has a procedural answer, covered further down.

The Overrides That Don’t Hold Up

The weaker reasons share 1 shape: they protect a commitment the decider has already made. 2 versions show up here:

In a 1976 lab simulation with 240 undergraduate business students, 1 group allocated an average of $11.08 million to a division it had picked itself.

The group that hadn’t picked it allocated $8.89 million. The money was hypothetical and the subjects were students.

The pattern is still recognizable in a portfolio review. A 2000 survey of IS audit and control professionals suggests 30% to 40% of information-systems projects show some escalation.

Cooper’s practitioner analysis of innovation pipelines argues that gates often lack teeth and that the kill option is rarely exercised.

So an override that rescues a struggling project can be a kill decision in disguise. The gate didn’t make it, and the exception path took the weight.

The Tell Is Which Direction the Override Runs

There’s a useful diagnostic in the direction of travel.

Expect an override that promotes something new to arrive with an explanation, and the one quietly protecting something already funded to arrive with less.

That asymmetry is worth watching in your own portfolio. The promotion is visible, and the protection is the one that goes unlogged.

If your exception path only catches the first kind, it’s catching the easy half.

Design the Exception Path Before You Need It

An exception path written after the fact is an excuse. Written in advance, it’s governance. The path itself is short.

It names who can override at each stage, what has to be true before they do, and what gets recorded after.

Name the Decider in Advance

The RAPID framework, popularized by Bain, splits a decision into recommend, agree, perform, input and decide, and the D sits with a single named role.

Atlassian’s team playbook says the approver is one person. Contributors get a voice without a vote.

The same Bain material notes that a 2006 survey of more than 350 global organizations suggests only about 15% of companies practice effective decision making.

An override made by a named authority is a role doing its job. An override by whoever spoke loudest is a gap in the design.

Define What Makes an Override Admissible

A good exception path defines what has to be true for an override to be admissible, and stays silent on what the answer should be.

New evidence has to exist, a named authority has to sign it, a rationale has to be written down, and a notification window has to be honored.

Notice what those conditions leave out. It never says which way the decision goes.

That’s what keeps the path usable by an executive who genuinely disagrees with the scoring, and defensible to the people who did the scoring.

Scale the Rigor to Reversibility

Bezos framed decisions in Amazon’s 2015 shareholder letter as one-way or two-way doors. Irreversible calls get the slow, deliberate treatment.

He also warned that as organizations get larger, they drift into using the heavy Type 1 process on decisions that don’t need it.

The point of that table is proportionality. Identical paperwork at both ends invites skipping at the light end.

That’s the cost of writing this down: someone has to decide, in advance, which decisions deserve the heavy version.

Getting that split wrong in either direction hurts. Too heavy and people route around the path, too light and the record stops meaning anything.

In practice the split is easier to agree on when nobody has a live override sitting in front of them.

What the Override Record Has to Contain

A record is the cheapest part of this. It’s also the easiest part to skip.

No study quantifies what decision records do to trust, so treat this as governance practice and not an evidenced intervention.

Five fields answer the questions the opening meeting couldn’t, a year later:

1. What the process produced, with the ranking as it stood
2. What was decided instead
3. Who decided, by name and role
4. What information changed the picture
5. What would change it back, and when the call gets revisited

The last field is the one to protect, because it converts a verdict into a hypothesis with a review date.

A decision the group can revisit stays open to new information. And it puts a date in the calendar. On that date, the override gets tested against what actually happened.

Scoring software that already stores who scored what should make the record cheap to assemble, and AI assistance can condense the evidence behind a call into something readable.

It can’t supply the judgment for one. Someone still has to write the sentences that explain why.

Explaining a Call You Can’t Fully Explain

Sometimes the reason genuinely can’t be shared yet. Transparency advice tends to run out at exactly that point.

The way I see it, there are 2 kinds of transparency here (they get treated as one).

Procedural transparency is the deliverable, which sits close to Kim and Mauborgne’s expectation clarity. It covers 4 things:

1. The criteria the decision was scored against
2. Who made the call, by name and role
3. That an exception was used at all
4. A review date people can hold you to

Content transparency covers the confidential fact itself. You can withhold that one and still deliver all 4.

McKinsey makes the adjacent point that executives have to get comfortable living with imperfect data. A room can be asked for the same tolerance.

Bezos’s disagree and commit formulation is the honest version of this: “I know we disagree on this but will you gamble with me on it?”

That works when the disagreement is real and the commitment afterwards is sincere. It stops working when it becomes a way to end conversations.

McKinsey’s work on dissent in problem solving notes that leaders who invite challenge may feel defensive and question their own judgment when they get it.

What to Say in the Room

3 sentence shapes carry the load – none require disclosing the fact itself:

1. “The scoring stood, and I’m overriding it on information I can’t share yet.”
2. “Here’s who made the call.”
3. “We revisit this on the fifteenth, and here’s what would change it back.”

All 3 tell the room the process is still running. The confidential detail stays out of every one of them.

The cost is that you’re now committed to a date, in public, with people who will remember it. That’s a real obligation. Take it seriously or don’t offer the date.

Keep the Path Light Enough That People Use It

There’s a failure mode on the other side. A heavy exception path gets bypassed, and a bypassed path leaves no record.

Once the override is also a procedure violation, the incentive to write it down disappears.

McKinsey describes a specialty-chemicals firm that put every senior leader onto all six of its governance committees without ever naming who actually decided.

In a 2018 McKinsey survey of 1,259 managers across 91 countries, only 20% said their organizations excel at decision making.

The same survey reports that 61% say most of their decision-making time is used ineffectively. Your exception path has to work inside that reality.

In McKinsey’s write-up of that same survey, respondents who called their decision making fast were 1.98 times more likely to say decisions were also of high quality.

Speed and quality aren’t opposites in that data. The survey measured decision speed, and paperwork weight is a separate question.

Design it so a busy VP can complete it in the meeting, and the record survives contact with reality.

Write the Exception Path Before the Next Override

Nobody gets to abolish the override. What you get to decide is the path it travels down, and who sees it.

3 moves, in this order:

1. Name the decider for each stage of the funnel, in writing, before the next scoring round
2. Draft the override record template and put it where the scores live
3. Report the override count beside your funnel numbers

That 3rd one changes behavior more than it looks like it should, because a number that gets reported is a number that gets discussed.

Zero overrides in a year isn’t a clean record. The likelier reading is that exceptions went somewhere your record doesn’t reach.

Write the path this quarter, while nothing’s riding on it. The next override arrives with a name, a reason, and a review date, and the room stays with you.

Download our ebook on idea evaluation and governance. It covers structured pipelines, enrichment, scoring, and the governance around them.

Or book a demo to see how Accept Mission handles scoring, decision records, and audit trails.