What Has to Change Before the Decision Does?

One of the hardest moments in a consequential decision comes months after it was made. The cost has arrived and the expected benefit hasn't materialized. The room that agreed on the original call is now considerably less certain, and someone is starting to ask whether the decision itself was wrong.

That question deserves a serious answer. Most of the time it doesn't get one, because the leadership team doesn't have a precise enough way to distinguish between three situations that feel nearly identical from the inside but require completely different responses.

I've spent more than three decades inside technology companies, across security, cloud, managed services, and growth businesses, sitting through strategic shifts, market turns, acquisition decisions, and the long uncomfortable stretch after a major call gets made.

What that time clarified for me is that the harder discipline, after any consequential decision, is knowing what would have to change before the decision does.

When Friction Becomes Evidence

Every consequential decision produces friction. Most leadership teams know that going in. A lost customer, a difficult quarter, internal resistance, an uncomfortable tradeoff: these things arrive on schedule after almost any hard call.

The challenge is that friction and evidence don't always announce themselves differently. Both arrive in the same meeting, with the same faces, carrying the same anxiety.

Friction tells you the decision is expensive. Evidence tells you the reasoning behind it was wrong. What makes this genuinely hard is that friction can eventually become evidence. A single lost deal may be the cost of the decision. A sustained pattern of lost deals, concentrated in the same segment, with the same objection, may be telling you something different: that one of the assumptions you built the decision on no longer holds.

The more useful question isn't which category a problem falls into immediately. It's whether what you're experiencing is starting to challenge one of the load-bearing assumptions behind the original call. That question keeps the conversation precise rather than reactive.

One pattern I've seen repeatedly: leadership teams either treat every setback as a referendum on the original call, or they wave away real signals by pointing to the original decision. Both failures come from the same place: no one separated the reasoning behind the decision from the cost of living with it, and no one asked whether the accumulating costs were starting to say something specific about whether the reasoning still held.

Every Decision Rests on Assumptions. Only Some of Them Are Load-Bearing.

When a leadership team makes a major decision, it makes that decision because certain things are believed to be true. The market will grow. Customers will accept the change. The team can execute it. The competitor will behave a certain way.

Some of those beliefs are expectations and forecasts. If they miss by a bit, the decision still stands.

Others are load-bearing. If one of them materially changes, the logic that supported the original decision no longer exists. You're now holding a conclusion whose reasoning has been removed.

This distinction is commonly overlooked, and it matters more than almost anything else in decision review. Because it gives you a precise question to ask when pressure arrives:

Has anything changed that invalidates the reasoning behind this decision?

That question sounds simple. It replaces a much weaker one that leadership teams actually ask, which is some version of "are we still comfortable with this?" Comfort measures the pressure in the room. The pressure in the room measures the cost of the decision. And the cost was always going to show up.

Three Situations That Feel the Same From the Inside

Over the years, I've come to see decision pressure sorting into three situations. They feel nearly identical while you're living through them. They demand completely different responses.

Conviction

The load-bearing assumptions still hold. Execution is hard, results are uneven, people are uncomfortable. Nothing fundamental has changed.

Here, the decision should hold, and holding it is a leadership act. Your team is watching whether commitments survive their first expensive quarter. If the answer is no, every future decision gets discounted before the ink dries.

Adaptation

Something material moved. A load-bearing assumption changed, and new information genuinely alters the logic behind the original call.

Reopening the decision in this situation is disciplined leadership, not a concession. What makes it hard is that reversing a major call can feel like admitting the original decision was a mistake. Often it wasn't. The original decision may have been entirely sound given what was known at the time. The reasoning changed. That is different, and the response should be different. Treating adaptation as failure is how leadership teams hold positions long after the logic supporting them has moved.

Drift

This is the one that worries me most, because no one decides anything.

An exception gets granted for one important customer. A sales leader keeps one old motion alive "temporarily." A disappointing result softens enforcement. A second exception follows the first, because the first one set the precedent. Each accommodation is individually reasonable.

At some point the organization operates under a different decision than the one leadership made. There is no meeting to point to. No one changed course. The course changed underneath everyone.

What makes drift particularly difficult to address is that it usually becomes visible only in retrospect. Leadership teams rarely realize it's happening because each individual accommodation seemed locally defensible. The commitment didn't end at any particular moment. It gradually stopped being enforced, and eventually stopped being real.

Name the Reopening Conditions Before the Pressure Arrives

The most practical move I know here happens at the moment of decision, while everyone is still thinking clearly.

When the decision is made, the leadership team also answers: what would have to become true for us to reopen this?

Write it down. Which assumptions are load-bearing. What kind of signal would count as a material change in one of them. And, just as important, which consequences are already priced in and will not justify revisiting the decision.

That last part carries more weight than it might appear. If leadership knowingly accepted a cost as part of the original decision, the later arrival of that cost is not new evidence. It is the tradeoff the team already accepted. Treating it as grounds for reopening conflates experiencing the decision with discovering that the reasoning behind it was wrong. Those are separate things, and confusing them is how drift gets rationalized as adaptation.

This changes the conversation later. When the difficult quarter arrives, you compare reality against conditions you defined under calm, instead of debating conviction under stress. The team examines whether a named assumption moved. If it did, you adapt deliberately. If it didn't, the discomfort is simply the bill for the decision you already made, and you pay it.

None of this requires a formal process. A handful of sentences, agreed at the moment of commitment, will materially change the conversation when pressure arrives later.

Who Gets to Put the Decision Back on the Table

One more piece deserves attention, because it fails quietly in a lot of companies.

Reopening a consequential decision should itself be a deliberate leadership act, with a clear owner. A lost deal reopens it in the sales team's mind. A board question reopens it in the CEO's mind. An operating difficulty reopens it in the COO's mind. If any of those automatically returns the decision to the table, the decision was never really settled. It was on probation.

A settled decision needs a defined path back. Someone with authority hears the signal, tests it against the reopening conditions, and decides whether the decision is actually open again. Until that happens, the organization executes.

This protects both sides of the discipline. It shields sound decisions from ambient anxiety, and it gives genuine new evidence a legitimate route to the top instead of leaving people to erode the decision through exceptions.

The Question Worth Sitting With

Take your three or four most consequential standing decisions and ask honestly:

Which ones are you holding because the reasoning still holds. Which ones are you reconsidering because a load-bearing assumption genuinely moved. And which ones has the organization already changed, one exception at a time, without anyone ever deciding to.

Decisions change. Sometimes they should. The question is whether leadership understood why the decision changed and whether that change was deliberate. That is the distinction between adaptation and drift.

David Cote is the founder of TrueNorth Strategic Advisory, an independent executive advisory firm working with CEOs, founders, and leadership teams on consequential decisions. After three decades in technology leadership roles across the security, cloud, and managed services sectors, he now advises leaders when strategic clarity, tradeoffs, ownership, and commitment are under pressure. Decision Governance is the discipline behind that work.