The Decision Is Made. Now What Are You Willing to Stop?
Updated: Aug 23
The meeting ends well. The slides are clean. The leadership team agrees the company is moving upmarket, or making AI a priority, or finally putting customer retention first. Everyone nods. Someone says it feels good to have clarity at last.
Then the weeks pass, and I watch for the one thing that tells me whether a decision actually happened.
I look at what stopped.
Usually, nothing did.
Sales keeps chasing the same deals it chased last quarter. The old investments stay funded. The leaders who held authority before still hold it. The new priority sits on top of everything that was already there. The organization has simply added another expectation without creating any capacity for it.
Agreement Is Not the Same as a Decision
Leadership teams often mistake the good feeling in the room for the decision itself. The conversation was hard, people worked through it, and reaching agreement felt like the finish line.
It was not the finish line. It was the easy part.
Agreement, by itself, costs very little. Everyone can support moving upmarket in the abstract, because in the abstract no current account gets dropped and no comfortable quota gets rewritten. The decision becomes real when someone has to give something up, and that moment rarely happens in the meeting where the decision was announced.
A decision exists at the point where the organization accepts a specific loss. Until then, you have an intention, not a decision.
Look at Where the Money and the Hours Actually Go
People below the leadership team do not read the announcement to learn what was decided. They read the allocation.
They watch where the budget settles. They watch which meetings the CEO keeps showing up to and which ones quietly drop off the calendar. They watch who gets the headcount, who keeps their authority, and which projects survive the next round of pressure.
The resource flow is the real record. Time, money, authority, and attention tell the truth regardless of what the strategy deck says.
So when a company declares AI a strategic priority and reduces nothing else, the organization draws the obvious conclusion. The new thing matters, but not enough to cost anything. People keep their effort where the real allocation points, and they are usually right to.
The Familiar Examples
The pattern shows up across very different companies, and it looks remarkably similar each time.
Moving upmarket while sales keeps pursuing the same small deals, because no one told the team which opportunities to walk away from.
Making AI a priority while every existing budget line stays fully funded, so the work happens on nights and weekends and never gets real weight.
Prioritizing retention while leadership attention stays fixed on new logos, because the review meetings and the incentives never moved.
Adopting a new operating model while the old authorities and old habits stay firmly in place, so the model exists on paper and nowhere else.
In each case the announcement was sincere. The leaders believed they had decided. What they had actually done was add an expectation to a system that already had no room for it.
What Happens Next Is Predictable
The decision does not fail loudly. It dissolves quietly.
For a few weeks there is energy. People try to make room for the new priority alongside everything else. Then ordinary pressure returns. A big customer escalates. A quarter runs short. A board member asks about the number that was always going to be asked about.
Under that pressure, the organization falls back to what it has always protected. Nobody calls a meeting to reverse the decision, because there is nothing formal to reverse. The reversal happens in where the hours go.
At the team level, the choice is rational. The old work still has deadlines, a sponsor, budget, and metrics attached to it. The new work has a name and a slide. So the team does the work that is actually resourced. Over time, the priority leadership believed it had decided becomes something the organization acknowledges in the right meetings and quietly sets aside everywhere else.
I have watched leadership teams that were genuinely convinced they decided something six months earlier and were genuinely confused about why nothing changed. The confusion is honest. They mistook the announcement for the act of deciding.
The cost is not only the failed initiative. It is what people learn. When employees repeatedly see a gap between announced priorities and actual allocation, they stop treating leadership announcements as operating signals. Over time, a new priority announcement is received as information about leadership's aspirations, not as direction about where effort should move.
The Tradeoff Conversation Is the Decision
Leadership teams often try to fund a new strategic priority without taking anything away from existing ones.
I have sat in rooms where a leadership team spent an hour discussing how to resource a new direction without touching anything currently funded. The conversation was earnest. The conclusion was always some version of finding efficiency, doing more with what we have, or absorbing it.
That is not a resource strategy. It is avoiding the tradeoff.
The tradeoff conversation is the decision. If it never happens, the decision never happened either.
When the Conversation Turns Serious
There is a recognizable moment when a tradeoff conversation shifts from general discussion to something real. It usually happens when someone in the room says the name of a specific thing.
Not a category. Not an investment area. A specific program, a specific account set, a specific initiative with an owner sitting three chairs away.
Before that moment, the conversation stays comfortable. Everyone agrees the new priority matters. Everyone agrees resources need to shift. The discussion moves around in the abstract, and nobody's budget is actually at risk. The room feels productive because everyone is still agreeing.
After that moment, the room changes.
The person who owns the thing being discussed gets quiet or gets specific. Someone asks whether leadership is really prepared to make the tradeoff. Someone else surfaces a dependency that hadn't come up before.
This is not resistance. This is the organization finally encountering the cost of the decision.
Leadership teams that work through that moment make a decision. Leadership teams that back away from it and return to language about balance, sequencing, or phased approaches have usually decided to keep everything and hope the new priority finds room on its own.
It will not.
The discomfort in that room is not a problem to be managed. It is evidence that the tradeoff is real.
Questions Worth Sitting With
Before treating your last big decision as settled, three questions are worth answering honestly.
What are we going to stop doing?
What will now receive less money, time, or leadership attention?
What can the organization now say no to that it could not say no to before?
If none of these has a concrete answer, the decision has not happened yet.
What Are You Willing to Stop?
A real decision leaves a mark. Something that used to get money now gets less. Something that used to fill the calendar now falls off it. Someone who used to own something hands it to someone else.
If nothing changes, the decision never became real. The company agreed to want more, and everyone below understood that immediately.
Most leadership teams already know what needs to come off the table. The difficulty is that the thing that needs to be reduced or stopped usually belongs to someone in the room.
Their budget. Their initiative. Their headcount. Their authority. Something they committed to and still believe matters.
That is why the conversation gets managed around the edges instead of through the center of it. A real decision requires someone to say clearly what will now receive less.
Less money. Less time. Less leadership attention.
It's not a decision until you're willing to give something up.
David Cote is the founder of TrueNorth Strategic Advisory, an independent executive advisory firm working with CEOs, founders, and leadership teams on consequential decisions. Drawing on more than three decades in technology leadership, he helps leaders clarify what actually needs to be decided, face the tradeoffs that come with it, and ensure the commitment holds as pressure returns. Decision Governance is the discipline behind that work.