Ask five people in your business to name the company's top three priorities for this quarter. Do it separately, without warning, and write down what they say.
Most owners who try this get five different answers. Some get five answers that do not include anything from the plan they presented in January. A few get blank looks.
This is not a sign that you hired badly. It is one of the most consistently replicated findings in management research, and it has a name. In their 2015 Harvard Business Review article "Why Strategy Execution Unravels", Donald Sull, Rebecca Homkes and Charles Sull reported that only about half of middle managers could name even one of their company's top five priorities. These were managers at large firms with communications teams and all-hands meetings and printed strategy decks.
The gap between what a business decides and what it actually does has been studied for decades. Kaplan and Norton's work on the balanced scorecard put the figure at around ninety per cent of organisations failing to execute their strategy successfully. McKinsey has separately found that the large majority of transformation programmes fail during execution rather than at the point the strategy was designed.
The plan is rarely the problem. The plan is usually fine. What fails is everything that happens in the eleven weeks after the planning session ends.
Why this hits small businesses hardest
There is a comforting assumption that the execution gap is a big-company disease, caused by layers of management and internal politics. Small businesses, the thinking goes, are close enough to the work that everyone naturally knows what matters.
In practice the opposite is often true, for three reasons that have nothing to do with size of headcount.
The first is that in a small business, the strategy usually lives in one person's head. The owner knows the plan intimately because they wrote it, and that intimacy creates a blind spot. When you have thought about something every day for three months, a single mention of it in a team meeting feels like heavy repetition. To everyone else it was one sentence in a forty-minute meeting eight weeks ago.
The second is that small businesses have no slack. In a company of two hundred, a strategic project can absorb someone for two days a week and the operational work still gets done by someone else. In a company of fifteen, the person who owns the strategic project is also the person doing the invoicing, and the invoicing has a deadline attached while the strategic project does not. Urgent work does not beat important work because people are foolish. It beats it because urgent work has a date and important work has a vibe.
The third is that small businesses rarely have a forum where progress on strategy is the actual agenda. There is a weekly meeting, but it is about this week. There is an annual planning day, but it is about next year. Nothing in between reliably asks whether the thing decided in January is any closer to being true in June.
Put those three together and the pattern is predictable. A good plan is made. Nobody disagrees with it. It is mentioned twice more. Operational work fills the calendar. Nine months later the plan is quietly rewritten because the world has moved on, and nobody says out loud that the previous version was never really attempted.
The four things that break it
If you look at where execution actually fails inside a small business, it tends to be one of four failures, usually in combination.
Priorities are not ranked, only listed
Most strategic plans contain between eight and fifteen initiatives. This feels responsible. Everything on the list is genuinely worth doing.
The problem is that an unranked list of twelve things is functionally identical to no list at all, because it delegates the ranking decision to whoever is doing the work, at the moment they are doing it, under time pressure. They will rank by what is easiest, or loudest, or most recently mentioned by you.
Guidance across OKR practice converges on three to five company-level priorities per quarter as the ceiling, and the reasoning is not arbitrary. Priority only means something in the presence of a trade-off. If you have twelve, you have not made a trade-off, you have made a wish list and pushed the hard decisions downward.
The uncomfortable version of this exercise is to take your current list and ask which items you would abandon entirely if the quarter went badly. If the answer is none of them, they are not ranked.
There is no owner, only a team
"Marketing will handle the website refresh" is not an owner. It is a description of a department.
Work with a group owner moves at the speed of the group's least available member, and it stalls without anyone feeling responsible for the stall. Every initiative needs one named person who would be the one to explain a delay. Others can do the work. One person answers for it.
This sounds obvious and is skipped constantly, usually out of politeness, because naming a single owner feels like assigning blame in advance.
Progress is invisible until it is too late
This is the most common failure and the most fixable.
Operational metrics get watched because they are attached to something that breaks loudly. Revenue, cash, deliveries, tickets. Strategic progress has no such alarm. A project that is eight weeks behind looks exactly like a project that is on track, right up until the quarter ends and someone asks.
Recent survey work in the strategy execution space keeps surfacing the same specific complaint: that leaders get no signal when a priority starts to drift, and that a clearly failing initiative often never gets formally resolved. It just stops being mentioned. These are practitioner surveys rather than academic studies, and the numbers vary between them, but the pattern matches what most owners will recognise from their own business.
Drift is not the real problem. Silent drift is. A project that is behind and known to be behind is a manageable situation. A project that is behind and invisible becomes a surprise, and surprises get handled badly.
Nothing gets formally killed
When a priority stops being a priority, most small businesses do not say so. The initiative simply fades. Nobody announces it, so nobody learns from it, and the person who was quietly still working on it keeps going for another two months.
The absence of a kill decision has a cost beyond the wasted effort. It teaches the team that priorities do not really mean anything, because they neither get finished nor get stopped. After two rounds of this, the next planning session gets treated as theatre, and it becomes theatre, and the cycle sustains itself.
The planning session is not where this gets fixed
There is a reflex, when execution has gone badly, to improve the planning. Better facilitation, a longer offsite, a more rigorous framework, an external consultant to run the session.
This almost never works, and the reason is worth sitting with. The planning session is the part of the process that already has everyone's attention. It has a date, a room, a facilitator and full attendance. It is the best-resourced hour in the entire strategic cycle. Improving it is improving the part that was never broken.
What has no resourcing at all is week six. Nobody has booked week six. There is no facilitator for week six. Week six is when the client escalation lands and the strategic work goes to the bottom of the list, and no amount of upstream rigour changes that.
A useful way to test where your own gap sits is to look at the last plan you abandoned and ask when it stopped moving. If you can identify the specific fortnight, and most people can, then ask what happened in that fortnight. It is almost always an operational shock that consumed the person who owned the work, and nothing in the system noticed.
That is a cadence failure, not a planning failure. The plan was correct until the moment nobody was watching it.
The corollary is that time spent designing the follow-through is worth more than time spent designing the plan. If you have a day to allocate, spending four hours on the priorities and four hours on the mechanism that will keep them alive is a better split than eight hours on the priorities alone.
What this looks like in a real business
An abstract description of the four failures is easy to agree with and hard to apply, so here is a composite that most owners will find familiar.
A services business of around twenty-five people finishes its planning day in January with nine initiatives. New service line. Website rebuild. Two hires. Pricing review. A CRM implementation. Improved onboarding. A partner programme. Better reporting. Everyone leaves energised, because the list genuinely captures everything holding the business back.
By March, three of the nine have visible movement, and they are the three with external deadlines attached: the two hires, because recruitment has a process that pulls it along, and the website, because an agency is invoicing against milestones. The other six have no external forcing function.
The pricing review is the interesting one. It is arguably the highest-value item on the list, because it affects every deal from the moment it lands. It is also owned by "the leadership team", which means it is owned by nobody, and it requires a difficult conversation about which clients are underpaying. It gets discussed at three consecutive meetings and progressed at none of them.
By June, the owner is frustrated and reads the situation as a commitment problem. It is not. It is that six items had no owner, no measure, no date and no forum, and were competing directly against billable client work that had all four.
The fix in that business was not motivational. It was cutting the list to four, giving the pricing review to one named person with authority to make the call, setting a date for the new rate card rather than for the next discussion, and putting thirty minutes in the calendar every second Tuesday. The pricing review completed in seven weeks after sitting untouched for five months.
Nothing about the strategy changed. Only the scaffolding around it did.
A cadence that closes the gap
None of this needs a new methodology. It needs three habits, and the third one is where most of the value sits.
Reduce to five, with a written trade-off. Take the quarterly list down to a maximum of five things at company level. For each one, write a single sentence describing what you are choosing not to do in order to make room. That sentence is the difference between a priority and an aspiration, and it is also the thing you will refer back to in week six when someone proposes a sixth priority.
Give each one an owner, a measure and a date. The owner is a person, not a team. The measure has to be something that can be observed by someone other than the owner, which rules out most self-reported percentages. "Website refresh is seventy per cent complete" is not a measure. "New pricing page is live" is. The date is the date it is done, not the date it is reviewed.
Run a fortnightly check that only asks two questions. This is the habit that does the work. Thirty minutes, every two weeks, with one agenda: for each priority, is it moving, and if not, what is the specific blocker. Not a status update. Not a discussion of the operational week. Two questions, five priorities, thirty minutes.
The value of the fortnightly rhythm is not the meeting. It is that a two-week horizon makes drift visible while it is still small. A quarterly review discovers that a project is eleven weeks behind. A fortnightly one discovers that it is nine days behind, which is a conversation rather than a crisis.
Kill things out loud. When something stops being a priority, say so in the meeting, record the decision, and tell whoever was working on it. Two minutes of mild awkwardness saves weeks of orphaned effort, and it is the single clearest way to demonstrate that the priority list is real.
Making it survive contact with the actual week
The honest objection to all of this is that the fortnightly meeting will be the first thing cancelled when a big client has a problem. That is what happens to most execution cadences, and it is worth designing against.
Three things help. Keep it short enough that cancelling it does not free up meaningful time, which in practice means thirty minutes rather than ninety. Keep the same slot rather than rescheduling, because a moved meeting is a cancelled meeting with extra steps. And separate it completely from the operational meeting, because when the two are combined the operational items always win the agenda. Every time. The strategic items get pushed to the end, the meeting runs over, and they get carried to next week, forever.
It also helps to write the priorities somewhere the whole team can see without asking. A plan that lives in a slide deck in someone's downloads folder is not visible. A plan that lives on a shared page people pass through weekly gradually becomes the thing people mean when they say "what we are working on".
This is the part of the problem Empiraa GPS was built for: keeping the plan, the owners, the measures and the check-in rhythm in one place so that progress is observable without anyone having to build a status report. The mechanism matters less than the habit, though. A shared document and a recurring calendar entry will beat expensive software that nobody opens.
What to do this week
If you want a fast diagnostic, run the question at the top of this article. Ask five people, separately, to name the top three priorities. Do not coach them.
If the answers are inconsistent, the issue is not that your team is disengaged. It is that the priorities were communicated once and then left to compete, unsupported, against work that has deadlines. That is a design problem, and design problems have fixes.
Cut the list to five. Name an owner for each. Put thirty minutes in the calendar every second Wednesday and ask the two questions. Then run the test again in ninety days.
Frequently asked questions
What is the strategy execution gap?
The strategy execution gap is the distance between what a business decides to do strategically and what it actually delivers. It shows up as plans that are agreed and then quietly abandoned, priorities that nobody can recall, and initiatives that end a quarter roughly where they started. Research going back decades, including Kaplan and Norton's balanced scorecard work and Harvard Business Review analysis by Sull, Homkes and Sull, has consistently found the failure sits in execution rather than in the quality of the strategy itself.
Why do most business strategies fail to get executed?
The common causes are having too many priorities to allow real trade-offs, assigning ownership to a team rather than a named person, having no way to see progress until the period ends, and never formally stopping initiatives that are no longer worth doing. Small businesses are especially exposed because operational work carries deadlines and strategic work usually does not, so urgent tasks reliably crowd out important ones.
How many strategic priorities should a small business have at once?
Three to five at company level per quarter is the range most practitioners settle on. The reasoning is that a priority only carries meaning when something else is being given up for it. A list of ten or twelve initiatives has not made that trade-off, it has passed the decision down to whoever is doing the work, who will then prioritise by urgency or convenience rather than by strategic importance.
How often should a team review progress against strategy?
Fortnightly works better than monthly or quarterly for most small businesses, because a two-week horizon catches drift while it is still small enough to correct. The review should be short, separate from the operational meeting, and limited to two questions per priority: is it moving, and what is blocking it. Combining it with the weekly operational meeting almost always results in the operational items consuming the agenda.
What is the difference between a strategic priority and a task?
A task is something a person does. A priority is an outcome the business is trying to reach, which usually requires many tasks and often spans several people. The practical test is whether it can be marked complete by one person in one sitting. If it can, it is a task. Confusing the two is why some quarterly plans read as a to-do list, with the result that the list gets worked through without the underlying outcome ever changing.
Does closing the execution gap require software?
No. The habits matter far more than the tooling. A shared page listing five priorities with named owners, plus a recurring thirty-minute check-in, will outperform any platform that the team does not open. Software becomes useful once the habit exists and the manual reporting starts to cost real time, particularly when several people need the same view of progress without someone having to assemble it each fortnight.
