Ask most teams how often they review their goals and the honest answer is once a quarter, if that. The plan gets set in a workshop, written into a deck, and then left alone until the next planning cycle, when everyone rediscovers how much of it never happened. The gap between the strategy and the result is not usually a thinking problem. It is a cadence problem.
The evidence points the same way. Kaplan and Norton, whose work sits behind most modern strategy execution frameworks, found that in the great majority of companies fewer than one in ten employees understood their organisation's strategy well enough to act on it. If most of your people cannot state the plan, a quarterly check-in is not going to fix it. What fixes it is a rhythm frequent enough that the plan stays in view and slow drift gets caught while it is still small.
This piece makes the case for a weekly accountability cadence, explains why the quarterly review keeps failing, and lays out how to run a check-in that takes fifteen minutes and actually changes what happens next week.
The quarterly review is too slow to steer
A quarter is roughly thirteen weeks. If you only look at your goals every thirteen weeks, then by the time you notice something is off track, it has been off track for weeks and you have lost most of your room to correct it. You are not steering the plan. You are reading a post-mortem.
Think about how a car works. You do not glance at the road once every few minutes and hope for the best. You make constant small corrections because the feedback is continuous. Strategy execution is the same kind of control problem. The value of a check-in is not the meeting itself. It is the short feedback loop that lets you make a small correction now instead of a large, painful one later.
Quarterly reviews also arrive too late to be honest. When the gap has grown for three months, nobody wants to own it, so the review turns into a session of explaining why the number was always going to be hard, or quietly rewriting the target so the miss disappears. A weekly cadence removes the incentive to hide, because a one week slip is not embarrassing. It is just information. People will tell you the truth about a small gap far more readily than they will about a large one.
There is a compounding cost to slow feedback. A goal that slips a little each week, unnoticed, slips a lot over a quarter. Caught early, the correction is a conversation. Caught late, it is a rescue. The whole point of a frequent cadence is to keep corrections in the cheap, early zone.
What the research says about frequency
The link between review frequency and results is not a matter of opinion. Studies of goal and OKR programmes consistently find that teams reviewing their objectives weekly complete materially more of them than teams that check in only at the end of the quarter. Reported figures put weekly reviewers well ahead, with completion rates lifting by a large margin compared with quarterly-only teams, and structured end-of-cycle retrospectives adding further gains on top.
The mechanism behind the numbers is straightforward. Frequent review keeps the goal salient, so people actually work on it rather than on whatever shouts loudest that day. It surfaces blockers while they are still small. And it creates a light, regular moment of accountability, where each person knows they will be asked what moved. That expectation, repeated weekly, changes behaviour more than any single big meeting ever will.
It is worth being clear about what these numbers are and are not. They come from vendor and practitioner research, not controlled trials, so treat the exact percentages as directional rather than precise. But the direction is consistent across sources and it matches what anyone who has run a team already knows: attention that shows up weekly beats attention that shows up quarterly.
Ownership is the other half of the problem
Cadence alone does not close the gap. A weekly meeting where nobody actually owns anything is just a status update that wastes an hour. The second ingredient is clear, single ownership of every goal and every measure.
The data on ownership is bleak. Research into goal programmes has found that a large share of goals, measures and projects have no named owner at all, with reported figures suggesting that around three quarters of goals lack a clear owner. When nobody owns a goal, everybody assumes someone else has it, and the goal quietly dies in the space between people. The same research finds that goals with a single clear owner get completed at a meaningfully higher rate than goals owned by a group or by no one.
Single ownership does not mean one person does all the work. It means one person is accountable for the outcome and answers for it in the weekly check-in. They can pull in whoever they need, but the buck stops with them. This is uncomfortable to set up because it forces the awkward conversation about who is actually on the hook, and it is exactly that discomfort that makes it work. A goal with a name next to it behaves differently from a goal owned by the team.
The pairing is what matters. Weekly cadence gives you frequent feedback. Clear ownership gives you someone to answer for the feedback. Put them together and the check-in has teeth. Leave either one out and you are back to the quarterly ritual with extra meetings.
How to run a weekly check-in that works
The most common objection to weekly reviews is time. Teams imagine another hour-long meeting on an already full calendar. A good weekly check-in is not that. It is fifteen minutes, tightly structured, and focused on movement rather than status.
It is also worth doing the arithmetic, because the objection usually rests on a false comparison. The comparison being made is a weekly meeting against no meeting. The real comparison is a weekly meeting against an occasional long one plus the cost of a missed quarter. A team of six spending twenty minutes a week invests about seventeen hours across a quarter. A missed objective that could have been caught in week three and instead surfaced in week eleven will cost more than seventeen hours to recover, assuming it is recoverable.
The other version of the objection is that weekly check-ins feel like micromanagement. That is usually a sign the meeting is being run as a report to a manager rather than a shared look at shared numbers. A check-in where everyone, including the most senior person present, is looking at the same figures and asking the same question reads very differently from one where a person reports progress to another person who evaluates it. The format matters as much as the frequency.
Start with the number, not the narrative. For each goal, the owner states where the measure is against where it should be by now. Not a paragraph about activity. A number and a direction. This takes seconds per goal and immediately separates the goals that are fine from the goals that need attention. Most goals in most weeks are fine, and you should spend almost no time on those.
Then spend the meeting only on the exceptions. For any goal that is off track or at risk, the owner names the single blocker and what they will do about it this week. The job of the meeting is to unstick that one thing, not to relitigate the strategy. If the blocker needs a decision from someone in the room, make it in the room. If it needs work outside the room, name who owns it and when it will be done.
Keep the horizon short. A weekly check-in is about the coming week, not the coming quarter. What will you move by next week? That question forces commitments small enough to be real and specific enough to be checked. Next week, you check them. This is the loop, and the loop is the whole point.
Finish with a written record of what each person committed to. It does not need to be elaborate. A shared list of owners, goals, current status and this week's commitment is enough. The record matters because it makes the next check-in fast: you open last week's commitments and ask what happened. Without a record, every meeting starts from memory, and memory is where accountability goes to die.
Making the cadence stick
The hardest part of a weekly cadence is not starting it. It is surviving the third week, when the novelty has worn off and a busy week tempts everyone to skip. The teams that make it stick treat the check-in as non-negotiable, the same slot every week, even when there is not much to report. Especially when there is not much to report, because a quiet week that nobody checks is exactly how drift begins.
Protect the meeting from scope creep. The weekly check-in is not the place for deep strategy debate, project planning, or the long-running argument about priorities. Those are separate conversations. If you let them into the check-in, it balloons to an hour, people start dreading it, and within a month it is dead. Keep it short and keep it about movement, and people will keep showing up because it respects their time.
Watch for the meeting becoming a performance. If people start reporting green when things are amber because green is comfortable, the cadence loses its value. The way to prevent this is to make it safe to report a miss. A leader who responds to a small miss with help rather than blame teaches the team that honesty is cheap and hiding is expensive. That is the culture that makes weekly review work, and it is set by how the leader reacts in the first few weeks.
Finally, connect the weekly rhythm to the longer one. The weekly check-in steers. The quarterly review still has a job, which is to step back, look at whether the goals themselves are still the right goals, and reset for the next cycle. The two are not in competition. The weekly cadence makes the quarterly review honest, because there are no surprises. You already know where everything stands, so the quarterly conversation can be about direction rather than damage.
Three loops running at different speeds
The weekly check-in is the engine, but it is not the whole system. Execution works best as three loops running at different speeds, each catching what the others miss. Getting the roles clear is what stops the weekly meeting trying to do everything and collapsing under the weight.
The weekly loop is for momentum. Did the priorities move, what is blocking them, what happens next. Short, tactical, forward-looking. It should not try to rewrite the strategy or debate whether a goal is still the right goal.
The monthly loop is for patterns. Stepping back once a month shows you trends the weekly view sits too close to see. Is a goal stalling not because of one blocker but because it was under-resourced from the start. Is one owner consistently underwater. Are several goals slipping in the same area, which suggests a deeper problem than any one of them reveals. The monthly loop reads across the goals rather than down each one.
The quarterly loop is for direction. Are these still the right priorities given what we have learned, did the assumptions hold, what should next quarter look like. Because it is informed by three months of honest weekly data rather than a single planning burst, it can be a real decision rather than a reconstruction.
Most teams only ever run the quarterly loop, which is why the plan is both stale week to week and wrong quarter to quarter.
A worked example
Take a twenty-five person services business with a quarterly objective to lift average client retention from 82 per cent to 90 per cent.
Under a quarterly cycle, the first real look at that number happens around week twelve. Under a weekly check-in, the number gets pulled every Monday against the same target.
In week three the number has gone the wrong way, down to 80 per cent. The check-in spends its five minutes on a single question: what changed in the last fortnight that would explain this. It turns out two clients churned for the same reason, slow support response while someone was on leave. That is fixable inside a week. Redistribute the coverage, follow up personally with the accounts most at risk, and watch response time daily instead of waiting for the next quarterly number. By week eight retention is back above 85 per cent and heading the right way.
None of that happens if the first look at the number is in week twelve, by which point three more clients have gone and the pattern is much harder to unwind.
This is the actual value of the cadence, and it is worth being precise about it. The team did not work harder. The same effort landed three weeks earlier, while the problem was still small enough to fix with a roster change rather than a strategic reset.
Work out which kind of stall you are looking at
Catching a problem early only helps if you respond to the right problem. When a check-in surfaces a goal that is not moving, separate the two reasons before deciding anything.
Either the work is not happening, or the work is happening and not producing the result. These need completely different responses, and confusing them wastes weeks.
If the actions simply have not been done, that is a capacity problem, and the honest move is usually to cut rather than push. A stalled goal often means the owner is carrying too much, and pressure does not create hours that do not exist. Decide what comes off their plate, or say openly that this goal is not this quarter's priority.
If the actions were done and the needle did not move, that is a strategy problem, and the goal is telling you the approach is wrong. The worst response is to do the same thing harder next week. This is where the early warning pays for itself, because you have found out in week four with time to try something else, rather than in week twelve with time only to explain.
One more distinction worth holding. Normal variance is not a stall. Anything measured weekly moves around, and treating every dip as a fire is its own way of killing the habit. The useful question is whether the trend over three or four weeks is going the right way, not whether a single week hit the exact pace you get from dividing the quarterly target by thirteen.
What to do when the whole team is off track
A weekly cadence will sometimes tell you something uncomfortable: it is not one goal that is slipping, it is most of them. This is exactly the situation a quarterly review would have hidden until it was too late to respond, and it is worth being clear about how to handle it, because the instinct to push harder is usually wrong.
When several goals are off track at once, the problem is rarely effort. It is almost always that the team took on too much, and the weekly check-in is now surfacing the overload that the planning session buried. The honest response is to cut, not to exhort. Look at the goals, decide which two or three genuinely matter this quarter, and formally pause or drop the rest. A shorter list that gets done beats a longer list that half happens, and the weekly cadence gives you the evidence to make that call with confidence rather than guilt.
Cutting goals mid-quarter feels like failure, which is why teams avoid it and let everything drift instead. It is the opposite. Deciding to focus is a sign the system is working, because you caught the overload early enough to do something about it. A team that finishes three goals looks far better in the quarterly review, and feels far better week to week, than a team that limped at all ten. The weekly rhythm makes this visible in time to act, which is one of its quieter benefits.
There is also a leadership signal in how you respond to a bad week. If the team reports widespread slippage and the reaction is blame, people learn to stop reporting honestly, and the cadence dies. If the reaction is a calm decision to refocus, people learn that the check-in is a tool that helps them rather than a stick that beats them. How a leader handles the first genuinely bad week tends to set whether the whole rhythm survives.
Scaling the cadence as the team grows
A weekly check-in is easy with five people around a table. It gets harder at thirty, and harder again at a hundred, and the common failure is to try to run the same single meeting with far too many people in the room. That does not scale, and forcing it produces a two-hour status marathon that everyone hates. The fix is to layer the cadence rather than enlarge the meeting.
Layering means each team runs its own short weekly check-in on its own goals, and the outcomes roll up. A team lead reports their team's goals in their own fifteen minute session, then carries the exceptions and the important movements up to a leadership check-in that runs the same way. Each meeting stays small and fast, and the information flows upward without any single meeting swelling to an unmanageable size. The structure mirrors the org, and the discipline stays identical at every level: number against target, exceptions only, one action and one owner.
The connective tissue is a shared view of goals and owners that everyone can see. When each level can look at the level below without waiting for a meeting, the check-ins get shorter, because nobody is using the meeting to transmit basic status that could have been read beforehand. The meeting is for the exceptions and the decisions, and everything else is visible on demand. This is where a shared system earns its place, because at scale the alternative is a fog of separate spreadsheets that never quite agree.
What must not change as you scale is the frequency and the honesty. It is tempting to move to fortnightly or monthly check-ins as the organisation grows, on the theory that senior people are busy. That reintroduces exactly the slow feedback loop the weekly cadence was meant to remove. Keep the frequency weekly at every level, keep each meeting short, and let layering handle the scale. The rhythm is what closes the gap, and the rhythm has to stay weekly to work.
A simple structure to copy
If you want a starting point, run this. Every goal has one named owner. Every week, at the same time, the team meets for fifteen minutes. Each owner reports their measure against target in one line. The meeting spends its time only on goals that are off track, agreeing one action and one owner for each. Every commitment is written down, and next week begins by checking last week's commitments.
That is the entire system. It is not clever, and that is the point. Most execution failures are not caused by a lack of clever ideas. They are caused by good plans quietly rotting between planning cycles because nobody looked at them often enough to notice. A short, frequent, honest cadence is the cheapest fix available, and it works for a two-person team as well as a two-hundred-person one.
Tools like Empiraa GPS exist to hold this structure in one place, keeping goals, owners, measures and weekly check-ins connected so the rhythm does not depend on a spreadsheet someone forgets to update. But the tool is secondary. The habit is what closes the gap. Start the weekly check-in this week, keep it short, keep it honest, and give it a month before you judge it.
Further reading: why quarterly goals stall in week three covers the three mechanical causes behind the drift this cadence is designed to catch, and the significance of regular strategy reviews sets out the four phases of the quarterly session the weekly rhythm feeds.
Frequently asked questions
How often should a team review its goals? Weekly is the cadence most closely linked to higher goal completion. A quarterly review is too slow to catch problems while they are still cheap to fix, because a quarter is around thirteen weeks and a goal can drift a long way in that time. Keep the weekly check-in short and reserve the quarterly review for stepping back and resetting direction.
Why do quarterly reviews fail to keep strategy on track? Quarterly reviews arrive too late to steer. By the time a gap is visible, it has usually been growing for weeks, so the review becomes a post-mortem rather than a correction. They also create an incentive to hide, because owning a three month miss is uncomfortable, whereas reporting a one week slip is just information.
What makes a weekly check-in effective rather than a waste of time? Keep it to about fifteen minutes, lead with the number against target for each goal, and spend the meeting only on goals that are off track. Agree one action and one owner for each exception, focus commitments on the coming week, and write everything down so the next check-in can start by reviewing last week's commitments.
Why does goal ownership matter so much? Research into goal programmes has found that a large share of goals have no named owner, and goals owned by no one tend to die in the gap between people. Goals with a single clear owner are completed at a higher rate. Ownership means one person answers for the outcome each week, even if others do the work.
How do I stop the weekly check-in from becoming another long meeting? Protect its scope. Keep it to movement against goals and this week's commitments, and push strategy debates, project planning and priority arguments into separate sessions. A check-in that stays short and respects people's time is one they keep showing up to, which is what makes the cadence survive past the first month.
Do weekly OKR check-ins work the same way? Yes, and the structure is identical. Each key result has one owner, the owner reports the current number against the pace the target implies, and the meeting spends its time only on the key results that are off. The one adjustment worth making with OKRs is to judge the trend over three or four weeks rather than reacting to every weekly dip, because most measures vary week to week without anything being wrong.
We do not have time for a weekly meeting. Is it worth it? Do the arithmetic before deciding. A team of six spending twenty minutes a week invests about seventeen hours across a quarter. A missed objective that could have been caught in week three but surfaced in week eleven almost always costs more than seventeen hours to recover, if it can be recovered at all. The real comparison is not a weekly meeting against no meeting. It is a weekly meeting against an occasional long one plus the cost of a missed quarter.
