A December Discipline: Why UK Teams Need a Maintenance Objective, Not a Growth Sprint
December is an awkward month for goal management. In most UK organisations the final weeks of the year are shaped by shutdowns, statutory holiday, compressed client deadlines and the annual round of festive commitments. Planning for the next cycle competes with finishing the current one, and the people who would normally chase progress are the same people covering for absent colleagues.
The result is familiar. OKRs stall somewhere around the second week of December, sit untouched through the break, and are picked up again in January with a mixture of guilt and renegotiation. The quarter has not failed. It has simply been left unattended at the point where attention was scarcest, and the cost is usually paid in the first fortnight of the new year.
A maintenance objective offers a lighter alternative to either abandoning the quarter or pretending that December operates at full capacity.
Why December defeats the standard OKR rhythm
Most OKRs are written for a steady-state quarter. They assume consistent attendance, predictable decision-making and a reasonable volume of working days. None of those assumptions survives mid-December in a UK business.
The pattern tends to run as follows. Final delivery deadlines bunch into the first two weeks. Annual leave is taken in blocks. Approval chains lengthen because one link is on a train to somewhere with poor signal. Then the office closes, and nothing moves at all until the first working Monday of January.
An ambitious key result that depends on eight consecutive weeks of coordinated effort is not badly designed in this context; it is simply badly timed. The answer is not to lower the ambition of the quarter but to change the question December asks. Instead of asking how much more the team can achieve, ask what must not be lost.
What a maintenance objective is, and what it is not
A maintenance objective is a single objective with two key results, both oriented towards preservation rather than growth. It protects the conditions that make January productive: continuity of decisions, accuracy of handovers, cleanliness of data, and the goodwill of customers and colleagues.
It is not a growth target wearing a disguise. Nor is it a licence to coast. The distinction matters, because a weak maintenance objective becomes an alibi. A strong one is specific, dated and verifiable, and it carries the same accountability as any other objective, just aimed at a different outcome.
The template
The structure below is deliberately small. It should be drafting work of around thirty minutes, not a planning workshop.
| Element | Example |
|---|---|
| Objective | Keep fourth-quarter commitments intact through the holiday period so that January begins from strength rather than recovery |
| Key result 1 | Every customer-facing commitment due before 5 January has a named owner and a documented handover by 18 December |
| Key result 2 | Two reduced-capacity check-ins held with all objective owners present or represented, with decisions logged |
The objective is written as an outcome, not an activity. The key results are countable and dated. Neither depends on anyone working through the break.
Key result one: the handover register
The handover register is the operational core of the objective. For each live commitment, it records the deliverable, the current owner, the nominated December custodian, the date of transfer, the location of the relevant files, and the single decision each custodian is authorised to make without escalating.
That last field is the one teams skip and the one that matters most. A handover that transfers tasks but not authority simply relocates the bottleneck. The custodian model works when the person covering can say yes or no within a stated boundary.
Build the register in a shared document, not a personal inbox. Review it once, in the week before the main shutdown, and confirm every row has an owner who has actually agreed to it.
Key result two: the reduced-capacity check-in
Two short check-ins are enough. One in the middle of December, one in the first week of January. Twenty minutes each, standing agenda, no slides.
The function of these sessions is not reporting. It is surfacing the small number of things that could break quietly over the break: a supplier who has not confirmed a date, a customer expectation that has drifted, a decision deferred until someone returns. Reduce the attendee list to objective owners and custodians. Accept representation without penalty, and record the decisions in one place so that anyone returning can reconstruct what happened.
Attendance should be tracked as a key result, because the failure mode here is not a bad meeting but a meeting nobody attends.
The January restart ritual
The restart is where most of the value is realised, and where most teams improvise badly. Schedule it before the break, in the calendar, with a named chair.
Its purpose is to answer three questions in order. What did we protect successfully? What drifted, and what does that tell us about our assumptions? What is the first decision the team needs to make this week?
The final question keeps the session from becoming a retrospective of the holidays. Teams often leave a January restart with a long list of things to catch up on and no clarity about what to do first. A single first decision, agreed in the room, is a better output than a recovery plan.
Adapting the pattern beyond December
Christmas is the most predictable slowdown in the UK calendar, but it is not the only one. August behaves similarly in many professional services firms. Easter creates a fortnight of partial availability. Sector-specific quiet periods, such as the weeks around academic holidays or the aftermath of a merger announcement, produce the same effect.
The principle travels: when capacity is predictably reduced, replace the growth objective with a preservation objective, keep it to one objective and two key results, and schedule the restart before the slowdown begins.
The discipline beneath the template
A maintenance objective is not a concession to the season. It is an acknowledgement that goal systems fail not because people stop caring but because the system stops fitting the conditions. Adjusting the objective to the month is a more honest response than declaring the quarter unrecoverable, and it protects the habit of review that carries the team into the next cycle.
Keep the objective small, make the key results verifiable, and put the restart in the calendar. That is the whole method.
