The Problem You're Solving May Not Be the Decision You Need to Make

Most leadership teams are good at solving problems. Give them a slowing pipeline, a missed quarter, a stalled product launch, and within a week there is a plan, an owner, and a set of actions on a slide.

That competence is real. It is also where the trouble starts. The problem placed in front of the leadership team is legitimate, the response is energetic, and the decision underneath was never actually examined. The team solved something. The organization is still stuck.

A real problem can point you toward the wrong decision.

That distinction sounds small. In practice it separates the companies that resolve issues once from the companies that keep resolving the same issue.

How a Problem Quietly Becomes a Decision Nobody Made

Growth slows. Within one meeting, the conversation turns to sales performance. Pipeline discipline, rep productivity, a possible change in sales leadership. The problem arrived carrying its own answer, and the team started debating the answer instead of the question.

Slowing growth raises questions about market focus, about which customer segments the company serves well, about where the company is willing to compete at all. Those are consequential choices with real tradeoffs. The sales performance conversation touched none of them.

The same move happens with execution problems. Deadlines slip, coordination slows, the same topics return meeting after meeting. Leadership reads this as an accountability issue and reaches for a personnel intervention or a new operating cadence.

Leadership adds dashboards, alignment sessions, and weekly reviews to an apparent execution problem, only to discover the underlying tradeoff was never resolved. The organization was being asked to execute a choice leadership had not finished making. The people were fine. The decision was missing.

Budget pressure follows the same script. Costs need to come down, so the response is a percentage cut across every function. That feels decisive and fair. The more consequential decision, which priorities the company will stop funding entirely, never gets made. Everything survives at a slightly smaller size, and the pressure returns next year.

In each case, the visible problem is real. The response contains a hidden assumption about what the situation requires. When that assumption goes unexamined, a legitimate problem installs a decision no one deliberately made.

The Gap Between Seeing and Committing

The load-bearing act of leadership judgment happens in a narrow space: between recognizing a real condition and committing to a response.

That space tends to close quickly. Pressure rewards speed, boards want plans, and a confident response to a named problem looks like leadership. Sitting with the gap looks like indecision, so almost nobody does it.

What lives in that gap is a set of assumptions. Slowing growth becomes a sales problem only if you assume the market, the segment, and the offer are sound. Execution failure becomes an accountability problem only if you assume the priorities were clear and the tradeoffs were settled. Budget pressure becomes a cost problem only if you assume everything currently funded deserves to exist.

Those assumptions deserve examination before commitment, because commitment is expensive. Once the organization mobilizes around a response, reversing it costs credibility, time, and momentum. Leaders know this, which is why wrong decisions tend to persist long after the evidence turns against them.

A useful test: take the proposed fix and assume it works perfectly. Then ask whether the situation genuinely changes. If a flawless sales performance program still leaves you competing in the wrong segment, the sales program was never the decision. An unclear answer to that test is itself a signal. It usually means something unresolved sits underneath the response.

Not Every Problem Deserves a Decision

Some problems require better execution of a decision already made. Some require clearer communication of a choice the team settled months ago and never explained down the line. Some require more information, and some require patience while an earlier decision plays out.

Manufacturing a consequential decision where none exists causes its own damage. It reopens settled questions, teaches the organization that commitments are provisional, and trains people to relitigate rather than execute. The discipline is in the sorting: determining what the situation actually requires before reaching for a response. Sometimes that answer is a hard choice between real alternatives. Sometimes it is a straightforward operating correction and the judgment to leave the strategy alone. Getting that sorting right, more than any individual decision, is what the role demands.

Finding the Decision Underneath the Problem

When the sorting says a consequential decision exists, the work is to surface it before the presenting problem defines it for you.

Start by asking whether the team can state the actual choice. A consequential decision requires naming what is being chosen between, with concrete alternatives on both sides. Fixing sales execution is a task. Deciding to concentrate on mid-market accounts and exit the low end is a decision. If the team cannot get that specific, it has a topic, not a decision. From there, name the cost. Every real decision gives something up. If the proposed course carries no visible sacrifice, it is a preference, not a decision. Getting specific about what is being traded away is often the moment the room discovers there is more disagreement than the earlier conversation suggested.

Then surface the assumptions underneath the choice. Every proposed decision rests on things the team believes to be true. The question worth asking is what evidence would tell you those beliefs are wrong. Decisions made without that check tend to become permanent by default, because no one established what would constitute a signal to revisit them. Ownership matters for the same reason. One person carries the decision and its consequences. When accountability is distributed across a leadership team, the decision quietly reopens the first time results disappoint, and that reopening rarely gets called what it is.

Trace what the decision forces downstream. Which initiatives stop. Which teams reorganize. Which customers the company will disappoint on purpose. A decision that forces nothing downstream probably was not a consequential decision.

Work the presenting problem through those questions and the real decision tends to surface. Slowing growth resolves into a market focus choice. The execution problem resolves into an unfinished priority tradeoff. The budget crisis resolves into a portfolio decision about what the company will stop doing.

What Happens When the Decision Stays Buried

Organizations that solve the presenting problem while leaving the real decision unmade develop a recognizable texture. The same conversations recur with new vocabulary. Coordination costs climb because teams protect different outcomes, each reasonably so, because leadership never chose between them. Activity stays high while direction weakens underneath it.

The meetings worth paying attention to are often the productive ones. Full agendas, clear action items, visible progress on the visible problem. That level of organized activity around a recurring issue usually means a choice was deferred rather than made, and the busyness is absorbing the energy the decision should have taken.

Then, months later, the original issue returns wearing different clothes.

Defining the Decision Is the Work

Leadership teams are measured on solving problems, so they get very good at it. Defining the decision correctly matters just as much, and it is far less visible, which is exactly why it gets skipped under pressure.

The problem in front of you is probably real. Take it seriously. Then, before you commit to the response it seems to demand, spend one honest hour on the choice hiding inside it. Some of the most consequential decisions a company makes were never made deliberately. They arrived attached to a problem, and leadership was too busy solving to notice.

David Cote is the founder of TrueNorth Strategic Advisory, an independent executive advisory firm working with CEOs, founders, and leadership teams when important issues require clear judgment and consequential decisions. After three decades in technology leadership roles across the security, cloud, and managed services sectors, he now works with leaders to recognize what deserves attention, determine what actually requires a decision, and bring independent judgment to the choices involved. When a consequential decision is required, Decision Governance provides the discipline for making it clear, owned, executable, and durable.