The decision that never gets made

Most execution failures are not caused by the wrong decision. They are caused by the decision that was discussed in every meeting, assigned to every agenda, and never actually made, because making it required someone to accept accountability for what came next.

There is a particular kind of silence that settles over a leadership team when a difficult decision appears on the agenda. It is not the silence of people thinking. It is the silence of people waiting — waiting for someone else to say the thing that everyone already knows, to absorb the weight of whatever comes next. The item gets a respectful amount of airtime. Someone asks a clarifying question. Someone else suggests they need more data. A third person recommends they revisit it next quarter. The meeting ends. The decision remains unmade. And two weeks later, it surfaces again — same agenda, same table, same silence.

This is not a failure of analysis. It is not a failure of intelligence or even of intent. It is something more precise, and far more expensive: it is the architecture of avoidance, disguised as process.

What We Call It When We Should Call It Something Else

Most organizations have a vocabulary for execution failure that centers on strategy. The wrong market, the wrong product, the wrong timing. These explanations are comfortable because they point outward — toward conditions, toward competitors, toward the complexity of the environment. They rarely point toward the room where the decision was not made.

Bain's 2024 analysis found that 88 percent of business transformations fail to achieve their original ambitions. Research from McKinsey shows that senior executives spend, on average, 37 percent of their working time on decision-making, and that 58 percent of that time is used ineffectively. The math is striking: organizations are not suffering from a shortage of meetings about decisions. They are suffering from a shortage of decisions that actually get made.

The pattern shows up across industries in remarkably consistent form. A technology company I worked with had spent the better part of a year discussing whether to sunset a product line that three different internal analyses had flagged as unsustainable. Every leadership review touched it. No one contested the data. And yet, quarter after quarter, the product continued to consume engineering capacity, budget, and goodwill — not because anyone believed in it, but because no one had formally agreed to end it. The absence of a decision had become a decision of its own, and it was extracting the same cost as any deliberate choice would, without the clarity that a deliberate choice would have produced.

The Psychology Underneath The Pause

Understanding why this happens requires looking at what occurs in the mind of a capable leader the moment a genuinely consequential decision arrives at the table.

Research published in Frontiers in Psychology found something counterintuitive: individuals in positions of greater organizational power were actually more likely to make avoidant choices when facing high-uncertainty decisions — not less. Power, it turns out, does not reliably produce decisiveness. When the stakes are real and accountability is visible, elevated authority can trigger what the researchers describe as a shift from approach goals toward avoidant goals: from "what do we do?" toward "how do I protect myself from what comes next?"

This connects to one of the most durable findings in behavioral economics. Kahneman and Tversky's work on loss aversion established that people feel the pain of a bad outcome from action more acutely than the pain of an equivalent bad outcome from inaction. Samuelson and Zeckhauser's landmark study formalized this as status quo bias — the tendency to prefer the current state not because it is better, but because any departure from it introduces new surface area for blame. Doing nothing, when it is the default, feels neutral. Making a call that goes wrong feels personal.

People feel greater regret for bad outcomes that result from action than for bad consequences that are the result of inaction.

In a room full of senior leaders, this calculus compounds. Darley and Latané's foundational research on bystander behavior — and the substantial organizational research it has since generated — demonstrates that as group size increases, individual felt responsibility decreases. Each person in that room perceives that the decision belongs slightly less to them than to the person beside them. The result is what researchers call a "circle of blame" — not malicious, not deliberate, but structural: an artifact of how accountability diffuses when it is shared broadly and assigned to no one specifically.

The meeting is not failing despite having the right people in the room. It is failing, in part, because of it.

The Agenda As Performance

There is a useful distinction between meetings that discuss decisions and meetings that make them. In practice, most executive meeting cultures collapse this distinction, and the collapse is not accidental.

Michael Mankins, writing in Harvard Business Review, identified the pattern clearly: strategic conversations in most organizations are "vague and unstructured," and delayed or distorted strategic decisions lead directly to overlooked waste, missed opportunity, and poor long-term investment. The meetings are happening. The discussions are occurring. The slides are thorough. And yet nothing that requires someone to own an outcome actually gets resolved.

Part of what sustains this dynamic is that a meeting with a decision on the agenda looks indistinguishable, from the outside, from a meeting that made one. The item appears. People speak about it. Time is allocated. And then the session ends, and everyone returns to the same positions they held when they walked in, with a date now set for the next conversation. The agenda item has been managed. The question has not been answered.

What this costs is difficult to fully quantify, but not difficult to estimate. Research places the annual cost of unproductive meetings in U.S. organizations at more than $375 billion. That number captures attention, but it understates the real damage — which is not the cost of the meeting itself, but the cost of the decision that came out of it incomplete, delayed, or dissolved into collective ambiguity. Teams wait. Work stalls. Trust erodes quietly, in the way that only shared awareness of a problem that no one is naming can erode it.

What Accountability Actually Asks

There is a moment in any significant organizational decision that functions as a hinge point — the moment when someone in the room is asked, explicitly and not rhetorically, to own what comes next.

This is not the same as being asked to agree. Agreement is cheap in groups; it requires nothing beyond presence and a willingness to nod. Ownership is different. It asks the person to accept that they will be associated with the outcome, that they will be the one who explains the result, that they cannot later say "I was not sure" or "the team decided" or "it came from above." Accountability requires a name attached to a consequence, and that attachment is precisely what the architecture of avoidance is designed to prevent.

Clarity is not about what you know. It is about who is willing to say what needs to be said and stand behind it.

The CLARITY framework I use in my coaching work treats clarity not as a communication style but as an organizational operating condition. When a team lacks clarity, it is almost never because the facts are unclear. It is because the decision that would resolve the ambiguity has not been made — and the decision has not been made because no one has accepted the exposure that comes with making it.

This is why the question "who owns this decision?" is so frequently met with a long pause — not because the answer is unknown, since most of the time everyone in the room already knows, but because saying the name out loud makes diffusion impossible. It assigns the weight. It makes the avoidance visible in a way that shared discussion never does.

I worked with a CFO once who had spent six months waiting for her CEO to formally decide on a restructuring of the finance org that both of them had privately agreed was necessary. The conversations had happened. The logic was sound. But the CEO had never said the words that would have made it official. When I asked the CFO what she thought was holding things up, she said: "He knows what needs to happen. He just does not want to be the one who decided it." That sentence contains almost everything important about how organizations stall.

What Breaking The Pattern Requires

Organizations that navigate this well have developed the same discipline at the structural level: they separate the work of analysis from the work of deciding, and they treat each as a distinct and named event.

Analysis meetings end with options. Decision meetings end with a name, a direction, and an agreed date for review. The person named is not someone who was consulted; they are someone who was selected — consciously, explicitly, with the understanding that being selected means being responsible for the answer and accountable for the outcome. The selection is not punitive. It is structural. It exists because without it, the meeting is theater.

This requires something at the cultural level that no process can fully substitute for: an environment where being wrong on a reasonable call is tolerable, where the person who made a defensible decision under uncertainty is not punished for the uncertainty, and where the team's shared commitment is to forward motion rather than collective protection from blame. McKinsey's organizational research confirms what most experienced leaders already suspect: that accountability and transparency, reinforced together at the system level, are what enable decentralized decision-making to actually work. Neither alone is sufficient.

One leader I worked with described the shift in terms I still find precise: "We stopped trying to make the right decision and started making the decision right." The first posture waits for certainty. The second accepts that certainty does not arrive before the call is made; it is built by the quality of the execution that follows.

Active listening, in this environment, is not a soft skill. It is how a leader identifies which decision is actually being avoided — because the one on the agenda is rarely the real one. Underneath the stated item there is almost always a different conversation: an unspoken risk, an unnamed concern, a quiet fear of a specific outcome. Surfacing that conversation is the work that precedes the decision, not a distraction from it. When people feel genuinely heard, the willingness to commit increases. When they sense they are being managed toward an outcome, it contracts.

The Cost Of Continuing

Every organization I have worked with has at least one decision it has been circling for longer than it can comfortably admit. In most cases, the people in the room already know what the answer is. They have known for some time. What they have not done is agree to be associated with it.

The operating cost of that non-decision is real: in talent that waits for direction, in resources allocated to work that has not been formally prioritized, in the slow erosion of trust that accumulates when a team watches the same item reappear on the agenda and understands, correctly, that the organization is not yet willing to do what it knows it needs to do. Over time, capable people develop a read for this pattern. And capable people, when they conclude that the organization cannot or will not decide, have a way of quietly making their own decisions — about how much energy to invest, about how much to trust the stated direction, about whether this is the right place to do their best work.

Clarity creates capacity. Not certainty — nothing does that. But when a decision has been made, named, and owned, the energy that was spent circling it becomes available for execution.

The team stops waiting. The work begins. And what had appeared to be a strategic problem reveals itself to have been, all along, a structural one: the absence of someone willing to say — this one is mine.

That moment of claiming — a single person in a specific meeting saying the words that attach their name to what comes next — is not a small thing. It is often the thing that everything else was waiting for.