The Problem Is Clear. The Decision Isn't.

Sales had stalled for two quarters. The leadership team had already run the diagnosis. Pipeline was thin. Win rates were soft in a couple of segments. The sales leader was under pressure, and everyone in the room could name the problem in the same words.

That is not a small thing. Shared problem clarity is genuinely hard to build.

So they did what capable teams do. They rebuilt the comp plan. They tightened the forecast process. They added two reps and cut a slow-moving deal stage. Several weeks of real work, all of it pointed at a problem everyone agreed on.

And numbers moved a little. Then they settled back down.

The question worth asking in that room had nothing to do with pipeline. It was which customers the company was actually trying to win. Not in theory. In terms of where the sales motion, the roadmap, and the support model were actually pointed.

Why the Clear Problem Was Misleading

When a leadership team defines a problem sharply, the sharpness itself becomes the trap.

Once everyone agrees on what is wrong, the work feels obvious. The problem gets fixed, measured, and reported on. That sequence feels like progress.

Naming the problem and naming the decision are separate acts, and teams regularly do only the first one.

This team had done the first act well. Their pipeline really was thin. That was true, and their execution work was not wasted. What remained unresolved was a different question entirely: who the company was built to serve, and which customers it was willing to stop chasing in order to serve the right ones well.

They were chasing three kinds of buyers at once. A high-volume, low-margin segment that kept the reps busy. A mid-market group that fit the product. And a handful of large accounts that demanded custom work the company kept saying yes to.

Every one of those buyers pulled the roadmap, the sales motion, and the support model in a different direction. Improving pipeline discipline could address the immediate sales problem. It could not tell the company which of those customers it actually intended to build around.

A comp plan does not resolve that. That is a choice, and nobody had made it.

The Decision Underneath the Surface

The useful question in that room was not how to improve sales. It was this:

What decision would still be unresolved even if we fixed the problem in front of us?

If they had clean execution tomorrow, closed every winnable deal, and hit the number, the underlying question would still be sitting there untouched. Which customers do we serve, and which revenue do we let go of on purpose.

Fixing execution would have helped. It would not have resolved that question.

Reps were making reasonable calls on individual deals. Teams were optimizing for their own slice of the customer mix. None of that was wrong in isolation. But the question of which customer the company was actually building around had never been put to a decision, so every part of the organization was quietly answering it on its own.

The consequential question was sitting underneath the operational one. Both were real. Only one had been named.

Not Every Problem Hides a Decision

This framing needs a boundary, because it is easy to overrun.

Not every operating problem is a strategic decision in disguise. Some sales slumps are just a rough quarter. Some execution gaps are exactly that, and the right response is better management, clearer communication, or plain patience.

Treating every problem as a fork is its own failure. It paralyzes a team, dresses up ordinary work as existential choice, and burns judgment on things that only needed follow-through.

Good leadership includes knowing when not to make a problem bigger than it is.

The discipline is telling the two apart. Most operating problems are exactly what they appear to be and deserve a direct operational response. A smaller number sit on top of a decision nobody has named. The mistake is assuming which one you are looking at.

What Leaders Actually Experience Next

When a team acts on the visible problem and leaves the decision underneath unnamed, the pattern that follows is familiar.

The same conversation keeps coming back. The sales problem gets addressed in Q1 and returns in Q3 wearing slightly different clothes. Now it is a product problem. Or a support problem. Or a hiring problem.

Coordination slows down without anyone being able to say why. Teams start protecting different outcomes because they are each optimizing for a different customer the company never officially chose.

The organization looks productive. Meetings are full. Dashboards move. And the direction quietly weakens underneath all of it, because the choice that would settle the matter has never been put on the table.

The cost is rarely confusion. It is committed effort aimed slightly beside the thing that actually needed deciding. That is harder to catch, because everyone is working hard and genuinely believes they are working on the right thing.

Before the Work Begins

Determining what genuinely requires a decision, before committing to execute against a visible problem, is quiet work. It rarely feels urgent. It almost never shows up on a dashboard. And it tends to happen, when it happens at all, before the visible work starts.

Leadership teams that do this well are not slower to act. They are more precise about what they are actually acting on. The sales problem gets addressed. The customer question gets named. Both receive the right kind of attention rather than one absorbing all of it.

Clarity about the problem is not the same as clarity about the decision. A leadership team can diagnose accurately, act intelligently, and still leave the consequential choice sitting underneath the work, unnamed and unresolved. The problem clarity itself is often what makes it so easy to miss.

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.