The fastest way to tell a strategy problem from an execution problem is to ask one question and answer it honestly: if this plan were executed perfectly — right people, no delays, full effort, nothing dropped — would it produce the result you need? If the answer is yes, you have an execution problem. If the answer is no, or if you genuinely cannot tell, you have a strategy problem, and pushing harder will only get you to the wrong destination faster.
Most teams reach for the execution diagnosis by default. It is the more comfortable answer: it implies the plan was sound and someone simply needs to try harder, and it comes with obvious next actions — a new dashboard, a weekly check-in, a performance conversation. The strategy diagnosis is uncomfortable because it lands on whoever set the direction, and because its next action is usually to stop doing something the company has already invested in.
Why the distinction changes the fix
These two failure modes respond to opposite treatments, which is why misdiagnosis is so expensive.
Execution problems respond to pressure and structure. Clearer ownership, shorter feedback loops, a removed bottleneck, a rewritten handoff — all genuinely help, because the underlying approach already works and the loss is happening between intent and delivery.
Strategy problems get worse under the same treatment. Better execution of a plan that cannot reach the goal simply raises the rate at which you spend money, hours, and goodwill on a bet that does not pay, and you end up with a well-run version of the wrong thing. It also burns credibility: people who can see the approach is not landing are told to try harder at it, and they stop reporting what they see.
The diagnosis therefore decides whether the next ninety days go into tightening the machine or changing where it points.
The perfect-execution test
Run it in writing, not in conversation, because conversation lets everyone nod at a plan nobody could actually restate.
Step one: write the plan in one sentence containing a "because." A strategy is a claim about cause and effect — if we do X for customer group Y, they will choose us because Z. "Grow revenue 20%" is a target, not a strategy. "Win mid-size manufacturers in our state because we can quote custom work in two days and the national players take two weeks" is a strategy: it names who, what, and why it should work.
If nobody can write that sentence, stop here. You do not have an execution problem. You have no strategy to execute, and the team is improvising individually — which explains inconsistent results better than any accountability gap.
Step two: assume flawless delivery and do the arithmetic. Take your best performer's actual conversion rate, cycle time, or margin — the number a good day produces — and apply it across the whole team or the whole pipeline. Does the best-case math reach the target?
This is the step that settles most arguments. If a perfectly executed version of the current plan still falls short of what the business needs, no amount of management will close the gap. The constraint is in the approach: the offer, the segment, the price, the channel, or the capacity you have committed to serve. If the best-case math comfortably clears the target and reality does not, the gap is real execution loss, and it is worth finding where it leaks.
Read the variance before you read the effort
Variance across people doing the same job is the most reliable signal available to a small company, and it costs nothing to look at.
If some people hit the number and others do not, with comparable territories, accounts, or job types, the method demonstrably works. Something transferable exists, and the work is to find what the top performers do differently and make it the standard. That is an execution problem, and it is good news, because the proof of concept is already inside the building.
If nobody hits the number — including your best person, on their best month — the ceiling is in the approach, not the effort. You are looking at a strategy problem.
One caveat catches people out. Check what your top performer is actually doing before you conclude the plan works. If your best salesperson quietly sells to a different customer type, at a different price, or with a modified promise, they are not executing the plan well — they are running a better strategy without telling anyone. That looks like execution excellence and is really a strategy signal, and it is one of the more valuable things you will find this quarter.
Symptom, diagnosis, first move
| What you observe | Likely diagnosis | Sensible first move |
|---|---|---|
| Wide spread in results between people doing the same work | Execution | Document what the top performers do differently, then make it the default method |
| Best performer also misses the target | Strategy | Re-examine the offer, segment, or price before touching the team |
| Activity is high, output is high, results are flat | Strategy | Check that the activity is actually connected to the outcome — the "because" may be false |
| The plan works but is always late or partial | Execution | Find the bottleneck and the unowned handoff; capacity and sequencing, not motivation |
| Everyone states the goal, nobody states the trade-off | No strategy exists yet | Decide what you are choosing not to do, in writing |
| Each fix buys a few good weeks, then the problem returns | Either — look at the pattern | If the same category keeps returning, treat it as strategy |
The ordering logic is cost. Reading variance and restating the plan take a morning; re-segmenting a market or repricing an offer costs a quarter and some revenue on the way through. Do the cheap diagnostics first, so you only pay for the expensive move when the evidence actually points there.
When it is both — and which one goes first
In practice it is usually both, because weak strategy and weak execution feed each other. An unclear plan gives people no basis for prioritizing, so delivery gets sloppy; sloppy delivery makes results noisy, so nobody can tell whether the plan works.
The default sequence is strategy first. Execution improvements compound in whatever direction you are already pointed, so fixing the direction first means every improvement afterwards is worth more.
The exception matters, though. If execution is so inconsistent that you cannot get a clean read on whether the approach works, you have to raise delivery to a minimum reliable standard first — not to hit the target, but to generate a trustworthy signal. Run the plan properly for one defined period, with one owner and one measure, and then judge it. Otherwise you will keep re-litigating a strategy that has never actually been tested.
For a small company there is a further practical point: you rarely have the bench depth to fix both at once, and decent execution of a clearly right strategy beats excellent execution of an unclear one. Pick the order deliberately and say out loud which one you are working on, so nobody is measured against both standards at the same time. If the direction is the open question, settle it properly using a structured approach to setting strategy instead of reopening it in every weekly meeting.
Why capable teams keep getting this wrong
Three forces push the diagnosis toward execution even when the evidence points the other way.
The person who set the strategy usually runs the review. Asking whether the plan is wrong means the owner has to volunteer their own work as the suspect, so without deliberate effort the question never gets asked.
Effort is visible and direction is not. You can see people working late; you cannot see a market segment that was always too small. Blame flows to whatever is observable.
Sunk cost peaks exactly when the evidence arrives. By the time results are clearly disappointing, the hiring, the tooling, and the public commitment are already in place. Reframing helps: the question is not whether the past spend was a mistake, but whether the next quarter's spend earns its return given what you now know.
A neutral outside read is worth considering when a problem has survived two honest internal attempts, or when everyone in the room has a stake in one of the answers. The value is mostly in the diagnosis rather than the implementation — an outsider asks the plain question that stopped being askable internally years ago.
Frequently asked questions
What is the difference between a strategy problem and an execution problem?
A strategy problem means the plan itself cannot reach the goal even if carried out perfectly — the segment, offer, price, or channel is the constraint. An execution problem means the plan would work but is being delivered inconsistently, slowly, or partially. The test is the same either way: assume flawless delivery, do the arithmetic, and see whether the target is reachable.
Can a business have a strategy problem and an execution problem at the same time?
Almost always, and they reinforce each other. Unclear direction produces sloppy prioritization, and sloppy delivery makes results too noisy to evaluate the direction. The practical move is to name which one you are addressing first and hold the other steady, rather than launching two change programs at once with a team that can only absorb one.
How do you test a strategy without abandoning it?
Run it deliberately for one defined period with one owner, one written expectation, and one measure — instead of running it half-heartedly for a year. A short, properly resourced test gives you a real answer. A long, under-resourced one gives you an argument, because everyone can claim it was never truly tried.
Will more accountability fix a strategy problem?
No, and it usually makes things worse. Accountability converts a clear plan into consistent action; applied to a plan that cannot reach the goal, it converts good people's effort into faster losses and eventually into turnover. Tighten accountability once you are confident the direction is right.
Who should make the call on whether it is strategy or execution?
The owner or leader decides, but not alone and not from the top of the funnel. Gather the variance data and talk to the people who touch the work daily, because they see where the approach stops working before it shows up in a report. Wide input, single owner — that combination gets you an accurate picture and a decision that actually gets made.
Next step
Before you ask the team for another quarter of effort, spend an hour on the diagnosis: write the plan in one sentence with a "because," apply your best performer's numbers across the whole team, and see whether the best case even reaches the target. That hour decides whether the next ninety days are spent tightening delivery or changing direction. If the answer is contested and everyone in the room has a stake in it, get a neutral outside read from a vetted strategy consulting firm before you commit the quarter.
