The meeting where nobody says the number
It is the last week of September and there is a meeting in the diary called "Q4 kick-off". Everyone in the room has already done the arithmetic on Q3. The revenue target is short, or the two hires did not land, or the service line that was meant to be live in August is still sitting in a doc with three open comments on it.
Nobody says the number out loud. Someone says the pipeline is looking healthier, someone else says September is always slow, and the conversation slides into next quarter. Forty minutes later the meeting ends and the quarter that just failed has never been discussed.
Most quarterly misses in a business of ten to a hundred people are not mysterious. Too many objectives, no clear owner, work that never got scheduled. Those reasons only surface if somebody insists on naming them, and the social pressure in a growing team runs the other way.
So start by saying the number. Out loud, in the room, without a softening clause attached to it. "We said eighteen new customers and we did eleven." Everything useful in the next fortnight depends on that sentence being said first.
Two bad reactions, both expensive
There are two standard responses to a missed quarter and both of them feel responsible at the time.
The first is to roll the plan forward untouched. Targets carry into Q4 unchanged, sometimes with the shortfall bolted on top, and the logic is that the team needs to push harder. It requires no admission and no re-planning, which is why it is popular, and it is the more damaging of the two, because it teaches everyone that the goals are decorative.
If a target moves from one quarter to the next without anything about the plan changing, the team learns that missing it produces no adjustment. Do that twice and your quarterly goals become a wish list that gets retyped every ninety days. People still nod in the meeting. They simply stop organising their week around it.
The second reaction is the opposite: tear the whole thing up. New objectives, new framework, sometimes a new tool. This feels decisive and it is usually a way of avoiding the diagnosis, because rewriting is creative work and diagnosis is uncomfortable work.
The cost is subtler. You throw away the parts of the strategy that were working alongside the parts that were not, and you reset everyone's understanding of what matters. A team of thirty takes about six weeks to absorb a genuinely new set of priorities, so rebuilding the plan every quarter leaves you almost no time in execution.
There is a third option, less dramatic than either. Keep the strategy, diagnose the execution, and make the next plan smaller. Research in this area consistently finds that execution, not strategy formulation, is where plans break down. Harvard Business Review's 2015 article "Why Strategy Execution Unravels, and What to Do About It" by Sull, Homkes and Sull is the standard reference on that point, and it holds for growing companies as much as large ones. McKinsey research has found that around 70% of strategic transformations fail at the execution stage rather than the strategy stage.
Your Q3 strategy was probably fine. What happened to it was not.
Work out why it missed before you decide what happens next
There are three real reasons a quarter misses, and they call for completely different responses. Get the diagnosis wrong and you will fix something that was not broken.
The first is that the goal was wrong. You committed to a number the business was never in a position to hit, based on an assumption that turned out to be false. Maybe you sized the target off one unusually good month, or assumed a partner channel would deliver leads and it delivered three.
The second is that the goal was right but nobody owned it. It was reasonable, and it belonged to "the team" or "sales" or "everyone". Work that belongs to everyone gets picked up by whoever has a quiet Thursday, which in a busy company is nobody.
The third is that the goal was right, it was owned, and the work was never scheduled. This is the most common and the hardest to see, because on paper everything looks correct: an owner, a number, genuine intent. What was missing was a block of protected time in anyone's week. The objective lost every collision with client work, and client work collides daily.
Telling them apart takes evidence rather than opinion. For a wrong goal, write the assumption underneath the number as a sentence: "we assumed forty qualified leads a month from referral". Then go and count. If referrals ran at twelve a month all quarter, and at twelve a month in Q2 as well, the goal was wrong on the day you set it and the team never had a chance.
For an unowned goal, the test is faster. Ask three people, separately, who was responsible. If you get three answers, or one answer with a qualifier attached, it was not owned. Your meeting notes will confirm it: if the follow-up action was assigned to the meeting rather than to a person, there is your answer.
For unscheduled work, look at calendars and at what actually shipped. If the owner was clear and the number was reasonable, and yet nothing moved between week two and week nine, the work was not in anyone's week. What those weeks went to is almost always delivery, support or an escalation, which tells you the objective was competing against work with a customer attached, and losing every time.
Expect more than one cause. A target that was too high, owned by someone with a full delivery load and no protected time, is all three stacked, and fixing only the target will not help.
The honest audit: what the last ninety days actually tell you
Before you write a word of the Q4 plan, spend two hours looking backwards. Not a retrospective with sticky notes and feelings, an audit with artefacts.
Read the Q3 plan as though someone else wrote it, and count the objectives. More than five for a company your size and you have already found something. Growing organisations reliably overcommit at the planning stage, because everything on the list is genuinely worth doing and nothing on the list forces you to choose.
Then look at the numbers attached to each objective and ask whether they were measured during the quarter. Not at the end, during. An objective with a number nobody looked at between kick-off and wrap-up was not a goal, it was an intention. In research on OKR adoption, 71% of companies say they have not yet mastered the process, which is a polite way of saying that a lot of goal-setting stops at the setting.
Next, build the real list of what consumed capacity for ninety days, from tickets, invoices and shipped work. Put it beside the plan. In most misses the two lists barely overlap, and that gap is the most useful artefact in the exercise.
Count the reviews as well. If leadership looked at progress against the plan once at the start and once at the end, the plan had no mechanism for correction, and a quarter is long enough to drift a very long way without anyone noticing.
Finally, check the connection between team goals and company goals. Around 65% of teams say their OKRs are not clearly linked to company goals, and the growing-company version of that is a sales target nobody in delivery, marketing or operations could explain their contribution to. If team goals were set separately and never reconciled, people were working hard on things that did not add up to the number you were chasing.
Write it down in half a page: what we committed to, what we did, where those diverged, and why.
What carries forward, what gets killed
Now you decide. Every objective from Q3 falls into one of three buckets: it carries forward roughly as it was, it carries forward in a changed form, or it dies.
Carrying forward unchanged is legitimate when the goal was right and execution failed for a reason you can now fix. If the number was sound and the problem was ownership or scheduling, keep the objective and change the conditions around it. That is not stubbornness.
Changing the form applies when the goal was directionally right but wrongly sized. Halving a target is not a defeat. A target you hit builds momentum and evidence, and the second miss costs far more credibility than the first.
Then there is killing things, which is where almost every organisation of this size stalls. Everything on the list has a sponsor, a rationale, and usually somebody who has already done work on it. Stopping it means telling a person their work is not continuing, and in a company where everyone knows each other, that conversation is genuinely unpleasant.
So instead of killing anything, teams deprioritise. The objective stays on the plan in a smaller font, or moves to a watch list, or gets described as ongoing. It keeps consuming attention, meeting time and the guilt of an unfinished commitment, while producing nothing. Deprioritising without removing is the most expensive form of politeness in a growing business.
The discipline is simple to state and hard to apply: if an objective is not in the top handful for Q4, take it off the page. Not smaller, not later, off. Tell the person whose work it was, tell them why, and tell them what you want them on instead. Do it in person and early, because the alternative is that they find out through a document.
One pressure test for each survivor: what does the business lose if you do not do this in the next ten weeks? If the honest answer is "not much, but we would like to have it", it is a good idea rather than a Q4 objective, and good ideas outnumber capacity in every company worth working for.
Q4 is ten working weeks, not thirteen
Here is the arithmetic most Q4 plans ignore. The quarter nominally has thirteen weeks. You do not get thirteen weeks.
Take out the public holidays, and the last two weeks of December, when the business is winding down even if the office is technically open. In Australia the December drop-off is real and it starts earlier than people plan for: client decision-making thins out from late November, and by the second week of December you are mostly talking to people who are finishing things rather than starting them.
Then take out annual leave. In a team of thirty, December leave means a meaningful share of your capacity is not there, and it clusters around the people who have been going hardest all year.
Plan for roughly ten working weeks. That should change the shape of the plan in two specific ways.
First, fewer objectives. If you set five for a thirteen-week quarter and missed, setting five for a ten-week quarter is not a correction, it is an escalation. Three is usually right for a company of this size, and two is not a failure of ambition.
Second, front-loading. Anything that needs a client decision, an external approval or a supplier belongs in October and early November. Ignore that and you end up waiting on a customer sign-off in the week everyone stops answering email.
A plan that acknowledges the calendar is also a plan people believe. When a team reads a Q4 plan that assumes full capacity through December, they privately discount the whole document, and a discounted plan does not get executed no matter how well it is written.
Every objective gets a name, not a department
If the diagnosis found an ownership problem, this is the section that fixes it, and it takes more than assigning a name at the planning meeting.
Ownership does not mean "responsible for that area". A head of sales is responsible for sales in a general, permanent way, which is too diffuse to move a specific number. Ownership of a Q4 objective is narrower: this named person reports on this number, by name, every fortnight, in a meeting where other people are listening.
That definition does a lot of work. One owner per objective, because a number reported by two people is reported by neither. The owner has to know the current figure at all times, which forces them to build some way of seeing it. And the number gets stated in front of peers on a schedule, which is the mechanism that actually changes behaviour.
The owner does not have to do all the work. They do have to answer three questions without preparation: where is the number now, is it on track, and what moves it next. An owner who cannot answer those in a corridor is not the owner yet.
Check two things when you assign them: authority and capacity. Giving an objective to someone who has to ask permission for every meaningful move is a slow way of keeping it yourself.
Say the ownership out loud in the meeting where the plan is agreed, and write the person's name next to the objective. Not their title, their name. Titles absorb accountability. Names do not.
The review rhythm that stops Q4 repeating Q3
Most quarters fail in the middle, quietly, over several weeks where nobody is looking closely. The fix is a cadence short enough to catch drift and frequent enough that drift never gets large.
Fortnightly is right for a company of this size. Weekly becomes an operations meeting and loses its connection to the plan. Monthly gives you two checkpoints in a ten-week quarter, which is not enough to correct anything.
Keep it to thirty minutes and keep the structure identical every time. Each owner states their number, says whether it is on track, and names the next action. No slides, no status narrative, no discussion of anything going fine. Problems get named in the meeting and solved outside it, otherwise the review becomes a working session and the other objectives get no airtime.
The most important part is a standing question: what is off track, and why. Ask it every fortnight, of every owner, in those words. A number that is behind is information. A number that is behind for a reason nobody can articulate is a warning, and it is usually the first visible sign of the same failure that cost you Q3.
Insist on evidence rather than sentiment. "Pipeline feels good" is not a report. "We are at nine of eighteen, up from six a fortnight ago, and the next thing is two proposals going out Friday" is a report, and the difference between them is the difference between a plan that corrects itself and one that discovers a problem in the final week.
Keeping it all visible in one place is what makes the cadence cheap to run. Empiraa GPS is built for that: objectives, the numbers under them, the named owner and the actions sit together, so the fortnightly review is a matter of reading the current state rather than assembling it the night before.
One rule: never cancel it. Skip the review because the week is busy and you have taught everyone the plan yields to whatever is loudest, which is the behaviour that produced the miss.
What you tell the team about a missed quarter
The team already knows. In a company this size there is no version of a missed quarter that stays inside the leadership meeting. What varies is whether they hear an accurate account or construct their own.
Hiding it is the expensive option. When leadership goes quiet about a result everyone can see, people fill the gap with the worst available explanation, which is usually about job security. Anxiety without information is what starts good people taking recruiters' calls.
So be candid. Say what the target was, what the result was, what the diagnosis found, and what is changing because of it. Four sentences covers it. The diagnosis matters most, because a miss with an explanation is something the organisation can act on, while a miss without one is just bad news.
Do not catastrophise either. A missed quarter in a business this size is normal, not a crisis, unless it is the fourth in a row or cash is genuinely tight. Present it as an emergency and you spend credibility you will want later.
Take your share of it. If the objectives were badly sized, that was a leadership decision, and so was leaving a number unowned. A leader who names their own contribution makes it safe for everyone else to be honest about theirs.
Then be explicit about what is stopping. "We are not doing the partner programme this quarter" is reassuring to hear. Silence about the partner programme is not.
A Q4 planning sequence you can run in a week
Order matters here, so this is the one place a list beats prose. Run it over five working days.
- Monday: do the audit. Two hours, leadership only. Pull the Q3 plan, the record of what actually got done, and the meeting notes. Write the half page of findings, including which of the three failure reasons applied to each missed objective.
- Tuesday: test the assumptions under any number you plan to carry forward, against real data from the last two quarters rather than the version you remember.
- Wednesday: decide the kill list. Sort every Q3 objective into carry, change or kill, and aim to leave three standing. Have the conversations with affected people the same day.
- Thursday: size and own. Set each target against ten working weeks, assign one named owner, and confirm they have the authority and the capacity. If they do not, change the owner or change the objective.
- Friday: lock the rhythm and tell the team. Put the fortnightly reviews in the calendar for the whole quarter before you leave the room, then brief the team on the miss, the diagnosis, the shorter list and who owns what. Most of that work is deciding rather than writing. If it takes three weeks, the kill decisions are being avoided.
Smaller, owned, reviewed
A missed quarter is only wasted if you skip the diagnosis. The quarter itself cost you ninety days. Failing to work out why costs you the next ninety as well.
The pattern is not complicated. Diagnose with evidence you can point at. Carry forward what deserves it and take the rest off the page. Size Q4 for the ten weeks you have. Give every objective one name. Review fortnightly, and ask what is off track and why.
None of that is a new strategy. It is the same strategy with fewer things on it, clearer ownership, and a way of catching drift while there is still time to correct.
