The quarterly plan is usually fine. That is the uncomfortable part. Most teams that fail to hit their quarterly goals did not choose the wrong goals, they simply stopped touching them somewhere around week three and only remembered in week eleven. You can see the pattern in almost any growing business. Planning day is energetic. Objectives get written, owners get named, someone builds a tidy document. Then the first genuine emergency of the quarter arrives, the plan gets set aside for a fortnight, and it never quite gets picked back up. By the time anyone reviews it, half the objectives have drifted past the point where anything useful can be done about them. The research on this is consistent and fairly brutal. Sull, Homkes and Sull, writing in Harvard Business Review in 2015, found that two-thirds to three-quarters of large organisations struggle to execute their strategy. McKinsey's position is that around 70% of strategic transformations fail at the execution stage rather than the strategy stage. Whatever number you prefer, they all point the same direction. The bottleneck is not thinking. It is the twelve weeks after the thinking. This article is about what happens in those twelve weeks, and specifically about the three mechanical things that determine whether a quarterly plan survives contact with an ordinary week. The week three collapse There is a recognisable shape to how quarterly goals die. Week one is setup. People are still energised from planning and the first tasks get done because they are easy and obvious. Week two is when the real work of the quarter starts arriving. Customer issues, a hiring problem, an unexpected invoice, a competitor doing something irritating. Attention shifts. Week three is the fork. Either there is a scheduled moment where someone asks what happened to the plan, or there is not. If there is no such moment, the plan becomes a document rather than a set of commitments, and documents do not exert pressure on anyone's calendar. By week six the plan is effectively dormant. By week ten someone remembers it exists and there is a short, unpleasant scramble to produce something that can be reported. By week twelve everyone agrees the quarter was busy and the planning process needs improving next time, which it does not, because planning was never the problem. The reason week three matters is that it is the first point where the plan and reality meaningfully diverge. Before that, nothing has gone wrong yet. After that, the gap compounds. A plan reviewed in week three can be adjusted. A plan reviewed in week ten can only be explained.
Ownership is the first failure point
ClearPoint Strategy's data on this is the most useful diagnostic available, because it names the problem in a way you can check against your own plan in about five minutes. In their dataset roughly 77% of objectives have no owner, and only around 15% of initiatives finish. Those two numbers are not independent. An objective without an owner is a statement of intent that belongs to the room rather than to a person, and rooms do not do work. The failure is usually subtle rather than obvious. Very few teams write a goal with the owner field left blank. What happens instead is shared ownership. Marketing and sales jointly own the pipeline target. The leadership team owns the retention objective. Three people are listed against the product launch. This feels collaborative and it is functionally identical to having no owner, because when the objective slips there is no individual whose week it disrupts. Benchmark data from the 2026 OKR reporting supports this directly. Teams that assign a single accountable owner per objective or key result see around 26% higher completion rates than teams with shared or ambiguous accountability. The fix is unpopular and simple. One name per objective. Not one name who does all the work, one name who is answerable for the outcome and who has to speak to it when it is reviewed. Everybody else can contribute. Only one person reports. Where teams struggle with this is objectives that genuinely span functions. The instinct is to co-own them. The better move is to name the person for whom the failure of that objective is most consequential, and make the cross-functional dependency an explicit part of their remit rather than a reason to split accountability.
Focus is the second failure point
The second reliable killer is volume. Growing teams routinely carry eight, ten or twelve objectives into a quarter, on the reasonable-sounding basis that all of them matter. They do all matter. That is not the relevant question. The relevant question is how many things a team of nine people can genuinely move in twelve weeks while also running the business, and the answer is almost always three. The guidance for growing businesses has settled around one to three objectives per quarter, with roughly three outcome-focused goals being the practical ceiling. This is not an arbitrary preference for tidiness. It is a reflection of what fits in the available attention once normal operations are accounted for. A quarterly plan with ten objectives is really a list of everything the business would like to be true, sorted into a format. It provides no guidance when two priorities conflict, which is the only moment a plan is actually needed. If everything is a priority, the plan cannot help you decide what to drop when a week goes badly, and weeks go badly regularly. The test worth applying is this. Look at your objective list and ask which three you would protect if the quarter turned out to be difficult. Then ask whether the other seven are actually going to get worked on, or whether you are carrying them so that nobody has to have the conversation about deprioritising them. Usually it is the second. Cutting the list is a leadership act rather than an administrative one. It involves telling someone that the thing they care about is not happening this quarter, which is why it usually does not get done. Cadence is the third failure point Ownership and focus set up the plan. Cadence is what keeps it alive, and it is the piece most often missing. The 2026 benchmark data puts the effect size clearly. Teams that check in weekly complete around 43% more objectives than those reviewing monthly or on an ad hoc basis. That is a larger improvement than most teams get from changing their goal framework entirely, and it requires no new methodology. The mechanism is not mysterious. A weekly review creates a recurring moment where the plan and reality are forced into the same room. Drift gets caught while it is still small. Blockers get named before they calcify. And, less nobly but just as importantly, people do the work because they know they will have to talk about it on Tuesday. What makes a weekly rhythm work is repeatability rather than sophistication. Same day. Same time. Same agenda. Same scorecard. The EOS Level 10 structure is popular for exactly this reason, and whether or not you use that specific format, the underlying shape holds: review the numbers, confirm priorities, surface issues, solve the ones that matter, leave with owned actions. A good weekly review answers four questions. What changed since last week. What is blocked. What decision is needed. Who is accountable before the next one. Notice what is not on that list. Status updates that could have been read beforehand. Detailed problem solving that involves two of the eight people present. General discussion. The most common reason weekly meetings get abandoned is that they become status theatre, run long, and stop feeling worth the hour. The practice worth borrowing from teams running this well is async-first preparation. Scorecard data and short written issue summaries circulate before the meeting. Live time is reserved for decisions rather than information transfer. This takes discipline to establish and it roughly halves the meeting length once it sticks.
Making the three work together
Ownership, focus and cadence are not independent improvements. They reinforce each other, and fixing one without the others tends to produce disappointing results. A weekly cadence over ten objectives is unmanageable. You end up with sixty seconds per objective, which produces status updates rather than decisions, and the meeting gets cancelled within six weeks. Clear ownership without a cadence means one person privately knows they are behind and nobody else finds out until the quarter ends. Focus without ownership produces three objectives that everybody agrees are important and nobody is answerable for. The combination that works is three objectives, one owner each, reviewed weekly against a small set of numbers. That is a modest system. It is also roughly what separates the businesses that finish their quarters from the ones that explain them. A practical quarterly setup Here is a sequence that works for a business between five and fifty people. Before planning day, write down what actually happened last quarter against what was planned. Not a narrative, a comparison. This sets an honest baseline and quietly kills the tendency to plan optimistically. Choose three objectives. Write them as outcomes, not activities. "Reduce time to first value for new customers from 21 days to 10" is an outcome. "Improve onboarding" is a topic. Name one owner per objective. Say the name out loud in the room. Confirm the person agrees. Attach two or three measures to each objective, with a current value and a target. If you cannot state the current value, finding it is the first task. Book the weekly review for the whole quarter before leaving the room. Same slot, thirty to forty-five minutes, non-negotiable. Agree what is explicitly not happening this quarter, and write that list down too. The list of things you declined is more useful mid-quarter than the list of things you chose. Then run it. The first four weeks feel slightly bureaucratic and the value only becomes obvious somewhere around week six, when you catch something drifting early enough to fix it.
What to do when the quarter goes sideways
Plans encounter reality. The point of a cadence is not to prevent that, it is to let you respond to it deliberately rather than by abandonment. When an objective is clearly not going to be met, there are three honest options and one dishonest one. You can reduce the target, extend the timeline, or formally drop it and reallocate the effort. The dishonest option is to leave it on the plan, stop working on it, and say nothing until the quarter closes. That is what most teams do, and it is why the end of quarter review is so often a exercise in creative framing. Dropping an objective mid-quarter is not a failure of planning. It is the system working. What you want is for that decision to be made in week five with the reasoning written down, rather than discovered in week twelve. The same applies to adding things. Something genuinely urgent will come up. The question to ask is which of the three objectives it displaces, and the answer has to be one of them. A plan that can absorb unlimited additions without anything coming off is not constraining behaviour, which means it is not doing its job.
The two-system problem underneath all of this
There is a structural reason this is harder than it should be, and it is worth naming because it is fixable.
In most organisations the strategy and the work live in different places. The plan is a document or a deck. The work is in a task tool, a shared inbox, a spreadsheet and a handful of people's heads. When the two sit in separate systems, staying aligned depends on somebody maintaining the link by hand, every week, across teams, for a whole quarter. Almost nobody sustains that past the first busy month.
This is why plans drift even when everyone means well. It is not a motivation failure, it is a systems failure. Keeping the plan and the work connected becomes a chore that competes with actual work, and actual work wins every time.
Teams that execute well are rarely more disciplined than everyone else. They have usually just closed the distance between where the strategy lives and where the work happens, so staying aligned is the path of least resistance rather than an extra task on someone's Friday.
Why annual planning sets the trap
Part of the reason quarterly goals stall is baked into how the year is planned in the first place.
An annual cycle encourages one burst of intense thinking followed by eleven months of hoping it holds. A plan built to last a year with no mechanism to adjust it assumes the world will sit still, and it never does. By March a customer has churned, a competitor has moved, and the January plan is quietly out of date without anyone formally saying so.
That produces one of the great silent killers of execution: the plan everybody knows is wrong but nobody will officially change. It gets disregarded in practice while still technically being the plan. Morale drops, because people are being asked to nod along to goals they can see no longer make sense.
The fix is not to abandon the strategy whenever something feels hard. It is to treat the plan as a living thing. Set the strategy with a long horizon, then revisit the priorities underneath it on a shorter cycle, quarterly at the outer edge and weekly for the actions. A review that can formally retire or reshape a priority keeps the plan credible, and a credible plan is one people are willing to be held to.
This applies the same way whether you call them quarterly goals or OKRs. The label does not change the mechanics. Objectives set once and reviewed once stall at the same rate regardless of the framework they are written in.
Where the tooling fits
None of this requires software. Plenty of businesses run a solid quarterly rhythm on a spreadsheet and a recurring calendar invitation, and a spreadsheet with a genuine weekly review beats an expensive platform nobody opens. Where tooling earns its place is in removing the friction that causes the weekly review to be skipped. If preparing for the meeting means someone spends two hours assembling numbers from five places, the meeting will eventually be cancelled because the preparation cost exceeds the perceived value. The role of a system is to make the current state visible without anybody having to build it each week. That is the specific job Empiraa GPS is built for: goals, measures, owners and the weekly cadence in one place, so the review is a conversation about decisions rather than an exercise in collecting data. That gives the team goals, measures and owners in one view, while ANI helps connect the work to the wider operating context. Review GPS pricing before setting up the cadence. Whatever you use, the test is the same. Can any person in the business see, in under a minute, what the three objectives are, who owns each one, and whether they are on track. If the answer is no, the plan is a document.
Choosing measures that survive the quarter
One more failure mode deserves attention, because it sits underneath everything above. A weekly review only works if there is something concrete to review, and a surprising number of quarterly plans contain objectives that cannot be assessed until the quarter ends. An objective like "improve customer satisfaction" measured by an annual survey gives you nothing to talk about in week four. The owner can only report activity, the review becomes a status update, and within a month the meeting feels pointless. What you want are measures that move weekly. Not necessarily the outcome itself, but something that changes often enough to be discussed. If the objective is to reduce churn, the weekly measure might be the number of at-risk accounts contacted, or the number of onboarding sessions completed. The outcome measure sits behind it and moves slowly. The weekly measure is what keeps the conversation honest. There is a risk here worth naming. Weekly measures can drift into activity tracking, where the team reports effort rather than progress and everybody feels productive while the outcome does not move. The guard against this is keeping the outcome measure visible alongside the weekly one, and being willing to say in week six that the activity is happening and the outcome is not, which means the theory behind the objective is wrong. That is a genuinely useful thing to discover in week six. It is a painful thing to discover in week twelve, and it is the reason a plan with only annual measures is close to useless for steering. Transparency helps here too. In most functioning implementations, goals are visible to everyone rather than held by the leadership team. That visibility removes duplicated effort, exposes dependencies between people, and creates a mild social pressure that tends to improve completion. It also makes it much harder for an objective to quietly stop being worked on, because more than one person would have to not notice.
Frequently asked questions
How many quarterly objectives should a growing business set?
Three is the practical ceiling for most teams under fifty people, and one or two is perfectly reasonable if the objectives are substantial. The constraint is not ambition, it is the attention left over after normal operations. A list of eight or ten objectives usually means the prioritisation conversation was avoided rather than resolved.
Should objectives have more than one owner?
No. Assign a single accountable owner per objective, even when the work is genuinely cross-functional. Benchmark data shows teams with single ownership complete around 26% more of their objectives than teams with shared or vague accountability. Other people contribute, but one person reports and is answerable for the outcome.
How often should we review quarterly goals?
Weekly. Teams reviewing weekly complete roughly 43% more objectives than those reviewing monthly or ad hoc. The review can be short, thirty to forty-five minutes is usually enough, but it needs to be the same time every week and it needs to survive busy periods, because the weeks you most want to cancel it are the weeks it is most useful.
What should we do when an objective is clearly not going to be achieved?
Decide explicitly rather than letting it lapse. Reduce the target, extend the timeline, or drop it and reallocate the effort, and write down which you chose and why. The failure is not missing a goal, it is carrying a dead goal for eight weeks while pretending otherwise.
Do we need software to run quarterly goals properly?
No, but you need the current state to be visible without anyone assembling it by hand each week. A spreadsheet works if someone maintains it. The reason weekly reviews get abandoned is usually preparation cost, so whatever you use should reduce that cost rather than add to it.
What is the difference between an objective and a task?
An objective describes a change in the business stated as an outcome, with a starting value and a target. A task is a piece of work. "Reduce average response time from four hours to one hour" is an objective. "Set up a shared inbox" is a task that might contribute to it. Plans made entirely of tasks tend to get completed without anything changing.
Why do OKRs stall after the first quarter?
For the same three reasons any quarterly plan stalls: no single owner, too many objectives, and no review that survives a busy fortnight. The OKR framework does not protect against any of them. What tends to make it worse is that OKRs are often set in an annual planning burst and then treated as fixed, so when reality diverges in March there is no mechanism to reshape them and they get quietly disregarded instead.
The honest summary
Quarterly planning is not hard. Most teams are reasonably good at choosing sensible objectives. The difficulty is entirely in the twelve weeks that follow, and the three things that decide the outcome are boring: one owner per objective, no more than three objectives, and a review every week that actually happens. If you change one thing this quarter, make it the weekly review. It is the cheapest intervention available and the data on its effect is the strongest. Book it for all twelve weeks now, before the plan is written, and treat cancelling it as a bigger deal than missing a target.
Further reading: weekly check-ins versus quarterly reviews covers how to run the review itself in fifteen minutes, and the significance of regular strategy reviews sets out the four phases of the quarterly session that sits above it.
Also worth reading when the quarter has already gone: planning Q4 after a missed quarter on diagnosing the miss without rewriting the strategy, and most KPIs measure activity, not progress on choosing measures that move weekly rather than only at the quarter's end.
