Most Growth Problems Are Diagnosis Problems
The most expensive sentence in a strategy meeting is a confident one.
“We know what the problem is.”
Sales is down, so sales needs fixing. Traffic is flat, so marketing needs more reach. People are leaving, so culture needs work. The product isn’t growing, so it needs more features.
Sometimes that’s right. Often it just names the place where the pain showed up. It’s the symptom.
That difference matters, because most companies are good at brute force execution once they think they understand the problem. An initiative is created, teams form, and resources move over. Targets are set, and then there’s a relentless push.
A weak diagnosis doesn’t cause inaction. It causes fast, disciplined action in the wrong direction.
That’s far worse.
Pain tells you where it hurts, not what’s wrong
Most reporting is built to show symptoms. A dashboard says conversion fell from 8.2% to 6.9%. A forecast says the quarter will miss. A survey says manager confidence has dropped. A pipeline report shows one stage getting worse.
All useful. None of it explains itself.
The temptation is to treat the place where the problem appeared as the place where it started. Conversion fell on the landing page, so fix the landing page. The miss showed up in sales, so rebuild sales. People say they’re burned out, so add wellness benefits.
We do this because closeness feels like cause. It showed up here, so it must live here.
Companies don’t work that neatly.
A team can miss its number because the positioning stopped being relevant six months ago. Sales can slow down because a pricing change added someone new to the buying committee. Marketing can look wasteful because the way buyers find you changed, but the measurement didn’t. Burnout is often less about hours than about decisions that never get made, incentives that pull against each other, and the feeling that hard work never turns into progress.
The pain is real. The proper diagnosis is still open.
Good execution can hide poor diagnosis
This is why strong teams are the most exposed.
When execution is weak, the failure is obvious. Missed deadlines, unclear ownership, and sloppy work.
When execution is strong, a wrong idea can survive for a year.
The team works hard, the plan looks solid, and weekly meetings get tighter. Everyone can point to activity. There are some results, but not enough.
So the company does more of it. More campaigns, more training, more pressure. They get a new leader, a new agency, a new tool.
Eventually someone decides the strategy failed. But the strategy never got a fair test because it was answering the wrong question from the start.
The real cost isn’t the money. It’s that people stop believing the next plan is any different from the last one. They learn that when results disappoint, the company just turns up the volume.
That’s when execution starts to break for real.
Three things worth keeping separate
Most companies collapse these into one. They’re not the same, and each one needs a different kind of answer.
1. The problem isn’t what’s happening.
Revenue is under plan. Retention is falling. Deals stall. Customers are confused. Decisions take eleven weeks.
Describe it. Don’t explain it yet. If your sentence has the word because in it, you’ve already left this step.
It may feel like a waste of time, but it’s the cheapest step to get right.
2. The mechanism is what’s producing the problem.
Maybe customers don’t see the value fast enough. Maybe a handoff loses context. Maybe the buying process changed. Maybe managers can’t make the call at the level where the call needs to be made.
This is a claim about cause, which means it can be wrong. That’s the point. A claim you can test beats a confident label everyone nods at.
3. The condition is what keeps it alive.
A decision stays slow because four executives have to approve it. A bad customer experience stays bad because the two teams who own either side of it are paid on opposite numbers. An experiment program stays fake because being wrong hurts your career, so nobody runs a test that could fail.
Here’s the simplest way to keep the last two apart: Mechanisms are verbs. Conditions are nouns.
Context dies in the handoff. That’s a verb.
Two teams own the same customer and are measured against each other. That’s a noun.
You can interrupt a verb with a project. A noun sits there and grows the verb back.
Which explains a pattern you’ve probably seen: fix the problem, and you get relief. Change the mechanism, and you get relief. Change the conditions, and you have a shot at something that lasts.
Most initiatives that worked and then stopped working were verb-level fixes in a noun that was never addressed.
How to tell whether you actually have a diagnosis
It should do more than sound reasonable. It should predict something.
If this is really what’s causing it, we should also see this other thing.
That one sentence will improve a strategy conversation more than any framework.
If you think low conversion comes from weak messaging, then customer interviews should show confusion about value before anyone brings up price. If you think slow growth comes from bad leads, then win rates should be clearly better on the leads your team calls good. If you think burnout is about workload, then cutting workload should help even when the decision friction and unclear roles stay exactly the same.
The point isn’t to turn your leadership team into a lab. It’s to stop rewarding explanations that can’t lose.
An explanation that fits every possible outcome tells you nothing.
The other way this goes wrong
There’s a failure at the far end too, and it’s more subtle.
Once a team learns to look at conditions, “it’s structural” becomes the answer to everything. It sounds sophisticated. It can’t be disproven. And it lets everyone off the hook.
So don’t call a condition finished until you’ve answered two more questions:
Who could change this?
What would changing it cost them?
If nobody can change it and saying it costs nothing, it isn’t a diagnosis. It’s a complaint in better clothes. An excuse in disguise.
What AI changed
It made this more urgent, not less.
You can now produce analysis, plans, options, research, forecasts, and a full rollout deck in an afternoon. That’s real leverage.
It also means a weak diagnosis can become a polished operating system before anyone notices the premise is wrong.
When doing things gets cheap, choosing what deserves doing gets expensive. When answers are everywhere, scarcity isn’t in producing them. It’s learning to ask the right question. It’s judging the question, the evidence, and how much confidence the answer has earned.
The risk isn’t that AI makes us dumber. It’s that AI makes premature certainty look unusually professional.
Diagnosis is not the opposite of action
I want to be careful here, because this argument gets misused.
Diagnosis isn’t a reason to slow down. And it isn’t a substitute for doing the work. Without execution, a good diagnosis is worth nothing. Diagnosis exists for one reason: to aim the execution at something real. And done well, it becomes the most direct path to your goal, which means it actually is the fastest path.
They’re one sequence, incomplete without each other.
Which is why the useful next step is almost never a plan. It’s an experiment, or pilot. It’s the smallest thing you can run that would actually change your mind.
And it’s rarely one thing. Companies usually have several conditions holding them back at once. But an organization that tries to change five things changes none, because attention and political capital run out long before ideas do.
So the most honest version isn’t only one thing is wrong. It’s only one thing can be changed at a time with enough force to matter.
That’s a claim about sequence, not about there being a single culprit. You pull one lever while you prepare the next one. Conditions have lead times. Some take a quarter to set up and a week to execute. If you only work on them one at a time, back to back, you spend most of the year waiting.
Two better questions
Instead of asking: What should we do about this?
Start one step earlier: What would have to be true for our explanation to be right?
That question shifts the conversation from opinions to claims. It surfaces assumptions. It gives the skeptics something useful to argue with.
Then ask: What’s the least expensive (time, energy, resources) thing we could test that would make us meaningfully more sure?
Now you’re moving again. This time, the movement produces information instead of just activity.
Try it on something real
Take the problem your company is currently spending the most money on.
Write down the symptom without explaining it. Write your current explanation as a claim that could be wrong, with a confidence number next to it. Then write one thing you’d expect to see if that claim were true, and one thing you’d expect to see if it were false.
If you can’t fill in that last part, you don’t have a diagnosis yet.
The Growth Diagnosis Canvas walks you through the whole sequence: symptom, mechanism, condition, competing explanations, and the cheapest test that could settle it. It takes about an hour with the right people in the room, which is roughly one percent of what the wrong answer costs.
Better execution still matters. It’s significant.
But first, ask the right questions just long enough to find the right problem.
