A Plan Is Not a Strategy. Does Your Board Know the Difference?

Most Companies Have a Plan. Very Few Have a Strategy. Which One Do You Have?

A plan says what we will do.

A strategy says what we will do, what we will not do, why those choices hold under pressure, what would have to be true for them to succeed, what we’re watching to know when conditions are changing, and what we do when they break.

That’s not a semantic difference. It’s the difference between a document that guides decisions and a document that describes intentions. Most organizations have the second. They call it strategy. Their boards approve it. And nobody in the room notices the gap until the plan meets the market.

A plan answers: what will we do? A strategy answers: what will we do, what won’t we do, and why does the logic hold when things go wrong?

WHAT PLANS DO WELL

Plans are useful. Don’t mistake this for an argument against planning.

A good plan sequences actions, allocates resources, assigns accountability, and sets timelines. It makes execution visible. Without a plan, strategy is aspiration with no mechanism. The initiative stays on the whiteboard. The insight never becomes behavior.

The problem isn’t planning. It’s treating a plan as if it were a strategy. When that happens, the organization has actions without logic. Initiatives without choices. Progress toward objectives that were never tested against reality.

And when something changes, which it always does, the team has no framework for deciding what to hold and what to adjust. They go back to the plan. They manage the plan. They protect the plan. Meanwhile, the conditions the plan was built on have shifted underneath it.

WHAT STRATEGY ADDS

Strategy adds four things a plan doesn’t contain.

Explicit choices. Not just what we’ll pursue but what we’re specifically declining. A strategy that doesn’t foreclose options isn’t a strategy. It’s a list of good ideas. Real choices have costs, and those costs should be visible.

Tested logic. The conditions that must hold for the strategy to succeed, named rather than assumed. This is the WWHTBT work we covered in the spring. A plan assumes things will work. A strategy names what has to be true and distinguishes what’s been validated from what’s still open.

Signposts. Leading indicators that tell the team when conditions are shifting before the results show it. A plan tracks outcomes. A strategy watches signals. The difference determines whether you adjust while you still have room to move or after the window has closed.

A response logic. What the organization does when a key assumption fails. Not a contingency plan for every scenario, but a clear picture of what’s most likely to break and what the response would be. Teams that have thought through this in advance move faster when it happens.

None of those four things show up in a typical strategic plan. Which is why most strategic plans fail, not because the initiatives were wrong but because nobody built the logic underneath them.

WHERE BOARDS GET STUCK

Boards are trained to evaluate plans. They review the objectives, assess the financials, probe the assumptions at a high level, and approve or redirect. That’s legitimate governance work.

But most boards can’t tell whether what they’re looking at is a strategy or a well-organized list of things management intends to do. The presentation looks the same. The language sounds similar. The slide that says ‘strategic priorities’ could be describing actual strategic choices or it could be describing a collection of departmental wish lists assembled into a coherent-looking document.

The test is simple and almost never applied: can the board articulate what the organization has decided not to do?

A strategy has costs. It excludes things. It says no to markets, customers, capabilities, and initiatives that might otherwise be worth pursuing. If the board can’t name what’s been excluded, the choices haven’t been made. The document is a plan.

Ask any board member to describe what the organization has decided not to do. The answer tells you whether the board is overseeing a strategy or approving a wish list.

A STORY WORTH TELLING

A $30M DMV nonprofit went through a formal strategic planning process. Seven months of work, an external consultant, board retreats, and leadership team offsite. The output: a 34-page strategic plan with six priorities, each with its own initiatives, timelines, and success metrics.

Simple question to the board chair: Which of these six priorities would the organization drop if resources constraints could fund only four?

No good answer. Not because he wasn’t thoughtful. Because the plan hadn’t forced that choice. All six priorities had survived the process because the process optimized for consensus rather than decision. Every constituency got its priority preserved. Nobody had to say no to anything. This is human pressure to protect turf and understandable.

That’s a plan. A well-researched, professionally facilitated, beautifully formatted plan. And when the federal funding environment shifted the following year and the organization did have to make hard choices, they were making them for the first time under pressure, without the shared logic they would have had if the choices had been made explicitly during the planning process.

The cost of that gap showed up eighteen months later. It was entirely avoidable.

THE ONE-PAGE TEST

In the May 5 Snapshot issue, we covered the one-page CEO Summary, SPRINT’s final deliverable. The constraint of one page forces the choices to be explicit. You can’t fit everything. Deciding what makes the page and what doesn’t is the strategy work.

The same logic applies to board presentations. A strategy that requires sixty slides to explain is probably a plan. A strategy that can be explained clearly in five minutes, with the choices and the logic visible, is closer to the real thing.

The board’s job is to engage with the logic, not the volume. Directors who ask ‘why did you choose this over that?’ are doing governance. Directors who ask ‘how confident are you in this projection?’ are reviewing a plan.

Both questions matter. But only one of them tells you whether the organization has a strategy.

YOUR MOVE THIS WEEK

Take your current strategic plan and apply three questions.

First: what has the organization specifically decided not to do? Not things you can’t afford. Things you’ve chosen not to pursue. If the list is empty or vague, the choices haven’t been made.

Second: what are the two or three conditions that most need to hold for the strategy to succeed, and what’s your current confidence level in each?

Third: what would the first visible signal be that one of those conditions is starting to fail?

If the plan answers the first question clearly and the second and third don’t exist anywhere in the document, you have a plan. Building the second and third is what turns it into a strategy.

That work isn’t done in the planning process. It’s done in the strategy process. They’re different disciplines, and the distinction is worth making before the market makes it for you.

Next week: The Alignment Illusion. Why leadership teams that agree in the meeting execute in opposite directions, and what real alignment actually requires.

ABOUT THE AUTHOR

Mark Haas is a strategy advisor to CEOs and boards of mid-market companies, with more than 30 years of experience across healthcare, defense, finance, social services, and biomedical research. He is the founder of Haas Strategy Solutions, a Certified Management Consultant, former Chair and CEO of the Institute of Management Consultants USA, and recipient of the IMC Lifetime Achievement Award. Mark also served as Ethics Officer for 20 years and holds degrees from Colgate and Harvard Universities.

Learn more about Mark | Connect on LinkedIn

Ready to build a living strategy that keeps pace with your market? Schedule a call.