Stop Solving Problems You Haven't Diagnosed

Businesses are very good at producing solutions.

Pipeline is light? Hire more sellers. Growth slowed? Increase marketing. Forecast is unreliable? Add another inspection call. A team is struggling? Change the leader. Customers are churning? Build a customer success program.

Sometimes those are exactly the right moves.

But there is a dangerous assumption underneath them: that the problem we can see is the problem we actually need to solve.

Often, it isn't.

The fastest route to wasted effort is prescribing the solution before understanding the constraint.

Symptoms are loud. Causes are usually quieter.

Revenue misses are obvious. A weak quarter is obvious. A seller missing quota is obvious. A product that isn't growing is obvious.

Those are useful signals. They tell us where to look.

They do not automatically tell us what to change.

A pipeline problem could be a demand problem. It could also be an ICP problem, a positioning problem, a seller-capacity problem, a qualification problem or a product problem that makes the market less responsive than the plan assumes.

A conversion problem could be sales execution. It could also be pricing, competitive pressure, weak urgency, a missing capability or a buying process that changed while the company kept operating from old assumptions.

Same symptom. Very different prescription.

Organizations tend to diagnose from where they sit.

Sales sees a product problem. Product sees a sales problem. Marketing sees a follow-up problem. Finance sees a productivity problem. Leadership sees an accountability problem.

That doesn't mean anyone is being dishonest.

People naturally interpret a problem through the part of the system they understand best.

The commercial leader's job is to get above the functions long enough to see the whole system.

Market. Product. Positioning. Demand. Sales. Customer experience. Talent. Leadership. Incentives. Process. Time.

Where does the gap actually begin?

That question matters because the place where a problem becomes visible is not always the place where it originated.

Start with what would have to be true.

One of the most useful questions in a growth plan is simple:

What would have to be true for this plan to work?

Maybe the plan assumes 25 new opportunities a month. A 30% win rate. A nine-month sales cycle. A certain amount of expansion. A certain number of productive sellers.

Write those assumptions down.

Then compare them with what the business is actually demonstrating.

Are we creating enough opportunity? Is it qualified? Is conversion holding? Is cycle time changing? Are enough sellers productive? Are customers expanding the way the model assumes?

Now the conversation gets more useful.

Instead of saying, “We need more revenue,” we can say, “The plan requires this input, and the business is currently producing that input.”

That is a diagnosable gap.

Ask why one more time.

Even after finding the gap, resist the first answer.

If pipeline creation is below plan, why?

Not enough activity?

Maybe.

But why is activity low? Is capacity wrong? Are territories poorly designed? Is the target market too broad? Are messages failing to earn attention? Are sellers spending time on work that should live somewhere else?

The goal isn't to turn every problem into an endless root-cause exercise.

The goal is to get deep enough that the action you take has a reasonable chance of changing the outcome.

Diagnosis should change what you do next.

A good diagnosis creates focus.

If the constraint is seller execution, coach and inspect execution.

If the constraint is weak positioning, don't hide it behind an activity target.

If the constraint is unrealistic capacity math, don't call it an accountability issue.

If the constraint is leadership, don't reorganize the frontline and pretend the system changed.

If the constraint is time, don't abandon a sound decision because the result hasn't appeared quickly enough.

Different problems deserve different interventions.

That sounds simple. It is surprisingly uncommon when a business is under pressure, because pressure rewards visible action. Diagnosis can feel slower.

But doing the wrong thing quickly is not speed.

There is a difference between action and progress.

I've seen organizations respond to underperformance with enormous amounts of activity.

New dashboards. New meetings. New targets. New messaging. New territories. New leaders. New compensation plans.

Everyone is busy. Everyone can point to what changed.

And six months later the same underlying problem is still there.

Change is not evidence of progress.

Progress means the constraint moved.

That is the test.

Leaders don't need perfect information.

Diagnosis does not mean waiting until every variable is known.

Businesses rarely give us that luxury.

Leadership still requires judgment. At some point you have to form a view, make a decision and move.

But there is a meaningful difference between making a decision with incomplete information and making one without doing the work to understand the problem.

The first is leadership.

The second is guessing with authority.

Start with the problem.

This is one of the principles behind how I think about R/CO.

Don't start with the service. Don't start with the org chart. Don't start with the answer we happen to know how to sell.

Start with the problem.

What is happening? What should be happening? Where does the gap begin? What evidence do we have? What are we assuming? What is the business telling us that the plan may not be?

Then determine the role. Then determine the intervention.

Diagnose before you prescribe.

Because the goal isn't to create more activity around the problem.

It's to solve the right one.