Most leadership teams believe they have a strategy. Few actually do. What they have is a plan — a detailed, well-intentioned, thoroughly reviewed plan that looks and feels like strategy but lacks the one quality that makes strategy valuable: the ability to guide decisions when circumstances change.
The difference matters. Planning organizes work. Strategy organizes thinking. A plan tells you what to do next. A strategy tells you how to decide what to do next — even when the plan no longer applies.
Here is a simple test to find out which one you have.
1. Can Teams Make Hard Tradeoffs Without You?
The first and most important test. Give your team a realistic scenario where two good options compete for the same limited resource. Ask them which one they would choose and why.
If they can answer confidently and their reasoning aligns with your strategic priorities, you have a strategy. The strategy has been internalized. It is guiding decisions without requiring your involvement at every turn.
If they cannot answer, or if they escalate the decision back to you, you do not have a strategy. You have a plan. The team knows what the plan says, but they do not know the logic behind it. Without the logic, they cannot adapt the plan when reality diverges from it.
Strategy scales judgment. Plans scale approvals. If your team needs your signoff on every nontrivial tradeoff, the headroom you thought you had from having a “strategy” does not exist. The strategy has not been communicated deeply enough to function as a decision-making tool.
What works better: Test this explicitly and regularly. In your next team meeting, present a scenario the roadmap does not cover and ask each lead what they would do. The answers will tell you whether the strategy is a document or a capability.
2. Can You Explain the Strategy Without Dates or Features?
The second test is for the leader who owns the strategy. Sit down with a blank page and explain your strategy in a single paragraph — no dates, no features, no spreadsheets, no Gantt charts. Just the logic: what you are trying to achieve, why it matters, and what you are choosing not to do.
If you can write that paragraph and it makes sense to someone who has never seen your roadmap, you have a strategy. It is clear enough to be communicated, remembered, and applied.
If you need a spreadsheet to explain it, you have a complex plan. Complexity is not depth. A strategy that requires a slide deck to understand is a strategy that will not survive first contact with reality. It is too brittle to be internalized by the team and too detailed to be adapted when things change.
What works better: Write the one-paragraph version of your strategy and share it with someone outside your immediate team. Ask them to repeat it back to you in their own words. If they cannot, the strategy is not simple enough. Keep simplifying until it fits in a paragraph without losing meaning.
3. Does the Strategy Survive Bad News?
The third test is the most revealing. Every strategy eventually encounters bad news — a missed deadline, a competitive threat, a budget cut, a key departure. The question is not whether the strategy survives intact, but whether it provides useful guidance in response.
A strategy that adapts to bad news is a real strategy. It bends. It helps the team decide what to protect, what to deprioritize, and what to stop altogether. The strategic logic remains valid even when the plan must change.
A strategy that breaks when one assumption fails is not a strategy — it is a brittle plan. If missing a single milestone causes the entire direction to collapse, the direction was never robust enough to guide real decision-making.
What works better: Stress-test your strategy against the worst news you can imagine. “What if we lose 20% of our budget next quarter? What if our main competitor ships the feature we were planning? What if the timeline gets cut in half?” If the strategy provides clear guidance in each scenario, it is durable. If it leaves you starting from scratch, it needs to be rebuilt.
4. Do Teams Know What to Stop When Capacity Tightens?
The fourth test is about constraints. Every team eventually faces a situation where capacity does not match demand. The question is whether the strategy tells them what to do about it.
When capacity tightens, a team with a real strategy knows what to sacrifice. The strategy has already established what matters most and what matters least. The team can drop the lower-priority work without needing permission because the strategic framework tells them which items are expendable.
A team without a real strategy tries to save everything. They scope creep. They work overtime. They ask for more resources. They do everything they can to avoid making the tradeoff because no framework exists to guide which tradeoff is correct.
What works better: Be explicit about the sacrifice order. In your strategic plan, include a ranked list: “If we need to reduce scope, here is the order in which items get cut.” This removes the ambiguity when constraints hit. The team does not need to guess what the leader would want — the leader has already told them.
5. Does the Strategy Guide Decisions Between Reviews?
The fifth test is about cadence. A real strategy lives daily. It shows up in hallway conversations, in Slack threads, in the way a team lead prioritizes their sprint. It does not wait for the quarterly review to be relevant.
A strategy that only matters during planning cycles is not a strategy — it is a ritual. It exists in a document that gets pulled out four times a year and ignored the rest of the time. Teams make decisions between reviews based on instinct, momentum, or whoever argued most recently. The strategy does not guide those decisions because it is not present in the day-to-day.
What works better: Create a forcing function for daily strategy reference. A simple one: every team’s sprint review includes a question about strategic alignment. “Which of our strategic priorities does this sprint’s work serve?” The question keeps the strategy present between planning cycles. When the strategy is referenced weekly, it becomes a living tool. When it is referenced quarterly, it is a report.
What I’ve Learned
Five things that separate real strategy from elaborate planning:
If the team cannot make tradeoffs without you, you have a plan, not a strategy. The entire purpose of strategy is to scale decision-making. If every hard choice still lands on your desk, the strategy has not been internalized.
A strategy you cannot explain in one paragraph is too complex to be useful. Simplicity is not a compromise — it is a feature. The simpler the strategy, the more likely it is to be remembered, applied, and adapted.
Bad news is the ultimate strategy test. A strategy that breaks under pressure was never a strategy. It was a set of assumptions that happened to hold until they didn’t. Build strategies that bend.
The sacrifice order reveals what you actually value. Every leader can name their priorities when resources are abundant. The ones who can name what they would cut first are the ones who have actually made strategic choices.
If the strategy only matters during planning, it does not matter. Strategy must live in the daily rhythm of decisions, not in the quarterly document. Find a way to make it present every week, not every quarter.
Planning organizes work. Strategy organizes thinking. If your roadmap vanished tomorrow, would your teams still know how to decide? That answer tells you everything.