When a Strategy Problem Gets Treated as a Planning Problem

There is a specific kind of meeting that happens in organizations every quarter. The agenda says strategy. The conversation is about execution. Everyone leaves with a longer to-do list and the same unresolved question they brought in. This is not a time management problem. It is a diagnostic one.

The plan is not the strategy

A plan answers: what will we do, in what order, by when. A strategy answers: why this, why not that, and what would change our mind. Both are necessary. The problem is that plans are easier to write, easier to present, and easier to measure. So organizations default to them.

The result is a roadmap that looks complete but cannot answer the question that matters most: if something changes, what do we do? A plan without a strategy is a list of commitments with no decision criteria behind them.

How to tell which problem you have

The diagnostic question is simple. Ask your leadership team: what would we give up if we had to? If the answer is immediate and specific, you have a strategy. If the answer is a long pause followed by 'we would have to discuss that,' you have a planning document dressed up as a strategy.

A second test: can your team describe what you have decided not to do? Inclusion is easy. Exclusion is where strategy lives. Companies that cannot name what they are declining to pursue have not made a strategic choice. They have made a list.

What to do about it

The fix is not a longer planning session. It is a shorter, harder conversation about trade-offs. What are you for? Who are you for? What will you decline even if it looks attractive? These questions are uncomfortable because they require commitment, and commitment means being wrong in a specific way rather than vague in a general one.

Most leadership teams need an outside structure to have this conversation productively. Left to their own devices, the conversation drifts back to execution because execution is safer. A facilitated session with a clear question and a written output changes the dynamic.

If your team can describe the roadmap but not the trade-offs behind it, that is the place to start. The articles on strategy and organization on this site go into related territory.