Ask five people in a twenty-person 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 find this test unpleasant. The answers rarely match. Somebody names a project. Somebody names a revenue number. Somebody names the thing that has been annoying them personally for six weeks. One person, usually the newest, says they are not entirely sure. This is not a sign of a bad team. It is the normal condition of a business that has a strategy in someone's head, or in a document, and no mechanism connecting that strategy to what people do on a Tuesday. The research on this is older and more consistent than most people realise. Donald Sull, Rebecca Homkes and Charles Sull, writing in Harvard Business Review in 2015 after surveying thousands of managers, found that only about half of middle managers could name even one of their company's top five priorities. Their work was in large organisations, but small businesses are not immune. They are just faster at pretending otherwise, because in a company of twenty everyone talks constantly and it feels like alignment. Talking constantly is not the same as being aligned. It is possible to have a daily standup, a busy Slack, an engaged team and still have three people quietly working on things that do not add up to the strategy.
The execution gap is a translation problem
The usual diagnosis is that people are not committed enough, or the plan was not communicated well enough. Both are usually wrong, and both lead to the wrong intervention, which is another all-hands presentation with the strategy on a slide. The actual failure is one of translation. A strategy is written at a level of abstraction that cannot be acted on. "Move upmarket" is a legitimate strategic choice. It is not a thing anyone can do on Wednesday. Somewhere between the choice and the Wednesday there has to be a chain: this is the choice, so these are the outcomes we need, so these are the measures that tell us if we are getting them, so these are the specific pieces of work, so this is who owns each one and when we will look at it again. Most small businesses have the first link and the last link. They have the choice, and they have a to-do list. What is missing is the middle, and without the middle there is no way to tell whether the to-do list is the right list. Everything on it looks reasonable in isolation. That is exactly the problem. The Sull research made a second point that gets less attention and matters more for small companies. When managers were asked what stopped execution, the top answers were failure to align and failure to coordinate across units, not lack of effort or unclear vision. In a twenty-person business, "coordination across units" means the two people who need to talk before something ships and who have never had a scheduled reason to.
Why the annual plan does not survive contact with the year
The other structural problem is cadence. Most small businesses plan annually, because that is what businesses do, and then review the plan when something goes wrong. An annual plan reviewed reactively has a predictable life. It is written in enthusiasm in January. It is broadly relevant in February. By April, three assumptions underneath it have changed and nobody has formally acknowledged this, so the plan and reality are now separate documents. By July the plan is a historical artefact that people are mildly embarrassed about. By October somebody suggests it is nearly time to plan next year. Nothing about this is a discipline failure. Twelve months is simply too long a feedback loop for a business whose circumstances change every few weeks. The plan was not wrong. It was just written before most of the information arrived. What replaces it is not a shorter plan. It is a shorter review cycle against a longer plan. Keep the annual direction, because direction should be stable, and shorten the interval at which you check whether the work still serves it. Quarterly for the priorities, fortnightly or monthly for the measures, weekly for the work in flight. The point of the shorter cycle is not more meetings. It is earlier detection. A priority that has drifted is cheap to fix in week three and expensive to fix in month five, and the only difference between the two is whether anyone looked.
What an operating rhythm actually looks like
The phrase "operating rhythm" gets used loosely, so here is a concrete version for a business between ten and fifty people. The specifics matter less than the fact that each layer has a different job and does not try to do the others' work. Annually, you set direction and make the small number of genuine choices: which market, which product bets, which things you are deliberately not doing. This is the layer where saying no belongs. A strategy that does not exclude anything is not a strategy, it is a wish list, and a wish list cannot help anyone prioritise later in the year. Quarterly, you translate direction into a short list of outcomes with owners and measures. Short means three to five for the whole business, not per person. This is the layer where most small businesses over-commit, and over-committing at this layer is what guarantees the drift you will be diagnosing in month two. If everything is a priority, the sequencing decision gets pushed down to whoever is busiest, and they will make it based on urgency rather than importance. Monthly, you look at the measures and ask one question: are these moving in the direction we expected. Not "are we busy", not "did we do the tasks", but is the number that represents the outcome moving. This is the layer that catches the situation where a team has completed every action on the plan and the result has not changed, which is far more common than anyone admits and far more informative than a missed deadline. Weekly, you look at the work in flight, unblock what is stuck, and confirm ownership for the next seven days. This meeting should be short and it should be boring. If the weekly meeting is where strategy gets debated, the quarterly layer is not doing its job. Each layer needs a different agenda and a different length. When they collapse into one meeting, which is the default state of most small businesses, the urgent items crowd out the important ones every single time. That is not a failure of willpower. It is what happens when a fire and a five-year decision are on the same agenda.
Measures that tell you something before it is too late
Most small businesses measure outcomes and nothing else. Revenue, churn, cash, headcount. These are necessary and they share one flaw: they tell you what already happened. A measure that helps you steer has to be something you can influence this month and that plausibly causes the outcome. If the quarterly outcome is to increase revenue from a new segment, the useful measures are the ones upstream: qualified conversations with that segment, proposals sent, conversion at each stage. Those move within weeks. Revenue from a new segment moves in a quarter or two, by which time the quarter is over. Getting this right requires an honest guess about causation, and the guess is often wrong. That is fine, and it is arguably the most valuable output of the whole exercise. If you chose "number of discovery calls" as your leading measure, hit the target comfortably, and revenue did not move, you have learned something real about your funnel that no amount of planning would have surfaced. Two practical rules keep this from turning into a reporting burden. Keep the number of measures small enough that one person can update them in under twenty minutes, because anything longer will not survive a busy month. And define each one precisely enough that two people would count it the same way, because a measure with an ambiguous definition will drift towards whichever interpretation looks best.
Accountability without the performance theatre
Accountability is the part small businesses find hardest, usually because it has been confused with blame or with a management style nobody in the room wants. Useful accountability is narrower than that. It means one named person is responsible for an outcome, everyone knows who it is, and there is a scheduled moment where they say where it stands. That is the whole mechanism. It works because the scheduled moment exists, not because of any consequence attached to it. Two things break it. The first is shared ownership. When two people own an outcome, nobody does, and the failure mode is polite: both assume the other is closer to it, and neither raises it until the deadline. Assign one owner even when the work is genuinely collaborative. The owner is not the only person doing the work, they are the person who knows the status. The second is the absence of a forum. If the only time anyone reports on a priority is when it has already failed, then reporting is inherently bad news and people will delay it. A regular, low-drama status conversation makes reporting routine, which is the only way you hear about a problem while it is still small. The tone of that meeting is set entirely by how the first piece of bad news in it is received. It also helps to separate the status question from the help question. "Where is this up to" and "what do you need" are different conversations, and teams that only ask the first one get accurate status reports and no requests for help until it is too late to give any.
The four failure patterns worth recognising early
Once you have run this for a couple of quarters, the same handful of problems show up. Knowing their shape in advance makes them much cheaper to fix. The first is the priority that never appears in a status conversation. Nobody reports on it, nobody asks about it, and at the end of the quarter it is quietly dropped. This almost always means it had no real owner, or the owner did not accept it. A priority assigned in a meeting where the owner said nothing is not owned, it is allocated, and there is a large practical difference between the two. The second is the priority that is always on track until the week it is due. Green, green, green, then a frank conversation about why it will not ship. This is a measurement problem rather than a reporting one. If the only measure is a completion date, the status is a guess right up until it is a fact. Break the outcome into something observable at the halfway mark and the pattern disappears. The third is drift by addition. Nobody removes anything, but over eight weeks four new pieces of urgent work attach themselves to the quarter, and the original priorities lose the capacity that was allocated to them. This is the most common failure of all and the hardest to see, because each individual addition was justifiable. The only defence is a standing question in the monthly review: what has been added since we set this, and what did it displace. The fourth is the measure that gets quietly redefined. A number that looked bad in month one starts looking better in month two, not because anything changed but because somebody adjusted what counts. This is rarely dishonest. It usually happens because the original definition was ambiguous and the person maintaining it made a reasonable call. Writing the definition down once, at the start, prevents almost all of it. What changes when the rhythm holds The benefit that owners tend to report first is not faster execution. It is fewer surprises. When there is a scheduled moment where each priority gets a status, problems surface weeks earlier than they used to. The projects that would have failed still sometimes fail, but they fail in month one when the cost is a conversation, rather than in month three when the cost is a quarter. The second change is in how decisions get made. A business with an explicit priority list has a ready answer when a new opportunity arrives mid-quarter: it either serves one of the current priorities or it goes on the list for next quarter. Without that list, every new opportunity is argued on its own merits, which the most enthusiastic person in the room usually wins. The third is less obvious and takes longer to appear. Teams that regularly see the connection between their weekly work and the company's direction make better independent decisions, because they understand what the work is for. That is the real return on the translation chain, and it is difficult to get any other way.
Making it visible
There is a mundane practical point underneath all of this. Most execution failures in small businesses are not decision failures, they are visibility failures. The information existed. It was in someone's inbox, someone's spreadsheet, someone's memory of a conversation in the kitchen. Whatever you use, the test is whether a person can answer three questions in under a minute without asking anyone: what are our current priorities, who owns each one, and is each one on track. If answering that requires opening four tools or interrupting the owner, the system is not doing its job, however well designed it looks. This is the problem Empiraa GPS is built for, connecting the strategy layer down through goals, measures and actions so the status is a byproduct of the work rather than a separate reporting exercise. But the tool is not the mechanism. A whiteboard that gets updated every Monday beats sophisticated software that nobody opens. What matters is that the chain from strategy to weekly work exists somewhere everyone can see, and that somebody looks at it on a schedule. It keeps goals, measures and actions in one place, so the operating rhythm remains visible between reviews. You can also review GPS pricing before setting it up.
Starting from where you actually are
If you are reading this from inside a business with no formal rhythm at all, the temptation is to design the whole system and launch it in January. Resist that. Systems introduced all at once tend to be abandoned all at once. A sequence that tends to hold: start with the quarterly priority list, because it is the layer with the highest return and it forces the hard conversation about what you are not doing. Get it to three to five outcomes with one owner each. Do nothing else for a month. Then add the weekly status conversation, fifteen minutes, same time, same three questions. Once that is habitual, add the monthly measures review. The annual layer can wait until you next need it. Expect the first quarter to be uncomfortable. The first honest priority list usually reveals that the business has been running six or seven priorities, and cutting to four means telling somebody their project is being paused. That conversation is the work. A prioritisation exercise that upsets nobody has not prioritised anything.
Frequently asked questions
What is the strategy execution gap?
The strategy execution gap is the difference between the strategy a business has decided on and the work its people actually do. It usually appears not because the strategy is wrong or the team is unwilling, but because there is no chain connecting the strategic choice to weekly activity. Research published in Harvard Business Review in 2015 by Sull, Homkes and Sull found that only around half of middle managers surveyed could name any of their company's top five priorities, which suggests the gap is a structural feature of how strategy is communicated rather than an unusual failure.
How many strategic priorities should a small business have at once?
Three to five for the whole business per quarter is a reasonable working limit for a company under fifty people. The constraint is not ambition, it is attention: each priority needs an owner who has genuine capacity to move it, plus a measure somebody maintains. Beyond five, the sequencing decision gets made informally by whoever is busiest, which means urgency quietly replaces importance.
How often should a small business review its strategic plan?
Keep the annual direction and review at shorter intervals against it. Quarterly for resetting priorities, monthly for checking whether the measures are moving, weekly for the work in flight. An annual plan reviewed only when something goes wrong has a feedback loop far too long for a business whose circumstances change every few weeks.
What is the difference between a leading and a lagging measure?
A lagging measure reports a result that has already happened, such as revenue, churn or cash collected. A leading measure tracks something you can influence this month that you believe causes the result, such as qualified conversations, proposals sent or onboarding completion rate. Both matter, but only leading measures let you correct course inside the quarter. If a leading measure hits its target and the lagging measure does not move, your assumption about causation was wrong, which is useful information rather than a failure.
Why do OKRs and similar frameworks fail in small companies?
Usually because the framework is adopted as a documentation exercise rather than a rhythm. Teams write objectives at the start of the quarter, file them, and look at them again twelve weeks later. The framework does no work in between. The mechanism that produces results is not the format of the objective, it is the scheduled conversation where somebody says where it stands and what is blocked. Any format works if that conversation happens, and no format works if it does not.
