The presentation went well. That is the problem.

The slides were clear, the logic was sound, and everyone in the room nodded at the right moments. Ninety days later, ask three managers what the strategy is and you will hear three different answers. Ask what changed in their week because of it, and you will hear a pause.

This is not a failure of ambition. Most leadership teams do not lack ideas. They lack a strategy that survives an ordinary Tuesday, when the inbox is full and the old way of working is faster than the new one. A plan that only lives in a deck is not a strategy. It is a souvenir of a good meeting.

A real strategy is a decision your team can repeat without you in the room.

A strategy nobody can repeat is not a strategy

Try this test before your next planning session. Write your strategy in one sentence, without jargon, in words a new manager could act on. Then ask two people on your team to do the same. If their sentences do not match yours, you do not yet have a shared strategy. You have a document that each person is interpreting in their own favor, which is how good teams drift apart while believing they are aligned.

Clarity is not about shorter slides. It is about fewer, harder choices. A strategy that tries to be everything and fix every weakness at once gives no one permission to say no, and a strategy that never says no is not guiding decisions. It is decorating them.

Ask the uncomfortable questions early. What will we stop doing, even though it feels safe? Which customer will we serve first when two good customers need us at the same time? What result, in plain numbers, will tell us in six months whether this is working? If those answers are vague, the execution will be vague too.

From document to operating rhythm

Strategies fail in the gap between the annual plan and the weekly calendar. Closing that gap takes a rhythm, not another retreat.

1. Translate the strategy into three priorities, and no more. Three priorities can be remembered, discussed, and defended under pressure. Ten cannot. For each priority, name one owner, one first action, and one date. Ownership that is shared by a committee is ownership held by no one.

2. Make every priority visible in the work people already do. If the strategy only appears in a quarterly review, it will lose to everything that appears every day. Bring it into the meeting you already hold: one question, asked weekly, about what moved each priority forward and what blocked it. Small, regular attention beats grand, occasional attention.

3. Measure decisions, not just dashboards. This is where business intelligence earns its keep, and where it most often misleads. A dashboard can show you everything and change nothing. The useful question is not "What does the data say?" but "What decision will this number change, and who will make it?" Choose a small set of measures tied to your three priorities, agree in advance what action each one triggers, and review them often enough to act while action still matters.

4. Review, and be willing to revise. A strategy review is not a ceremony for confirming the plan was right. It is a working session with three questions: What did we learn? What is no longer true? What will we do differently next month? Leaders who revise openly teach their teams to bring the truth early, when it is still useful.

Performance problems are rarely only performance problems

When results stall, the first instinct is often to push harder. Sometimes that is the answer. Often it is not. A team can work very hard inside a process that leaks, a structure that creates the same conflict every quarter, or incentives that reward the old behavior while the strategy asks for a new one.

Before you conclude that performance is the problem, check the system around it. Is the process clear? Is the decision authority clear? Does the way you measure success match the behavior you say you want? Fixing the system first does not excuse poor performance. It lets you see clearly where coaching, training, or a difficult conversation is genuinely needed.

That distinction, between a person to develop and a system to redesign, is one of the most valuable judgments a senior leader makes. Get it wrong and you pay twice: once in the wrong intervention, and again in the problem that is still there next quarter.

A question for your next planning conversation