Learning Before Leaving: A December Review That Gives January a Head Start

December is a difficult month in which to ask a team to think carefully. Energy is finite, diaries are fragmented, and a significant number of people are already mentally preparing for a shutdown. Yet the end of the year also offers something valuable: a natural pause before the next cycle begins. The question is whether that pause produces a document nobody reads or a small set of decisions that change how January feels.

A year-end team review often fails in one of two ways. It becomes a post-mortem, in which the loudest retrospective voices catalogue faults and the quieter members leave feeling judged. Or it becomes a celebration, warm and well-meant, with no evidence and no consequences. Neither approach improves performance. A learning review sits between the two: it is honest about difficulty, specific about success, and disciplined about what happens next.

Why December reviews drift

The first problem is purpose. If the invitation says “review the year”, people will bring opinions about the year. Some will bring grievances. Others will bring a list of achievements designed to be noticed. The conversation then becomes an appraisal by another name, and the team learns that candour is risky.

The second problem is timing. A ninety-minute meeting in the last week before Christmas is not a neutral setting. People are tired, some are preparing to leave, and others are already planning January. A review that asks for deep reflection without acknowledging those conditions will attract either silence or performance.

The third problem is follow-through. Many teams produce a useful list of lessons in December and then discover, by the second week of January, that the list has become an artefact. The lesson was real; the routine for using it was not.

Set the purpose before the invitations

Before the meeting, tell the team what kind of conversation this is. It is not a performance appraisal, a scoring exercise, or a chance to relitigate individual mistakes. It is a structured learning session with a limited output: no more than three changes the team will test in the first quarter.

Ask participants to bring two examples. The first should be a piece of work that went well, with a brief explanation of why. The second should be a moment when effort did not produce the expected return. The word “why” matters more than the word “who”. This small pre-read shifts the room from recollection to analysis.

It also helps to separate the review from the Christmas social event. A mince pie can follow the meeting; it should not substitute for it. The tone should be formal enough to signal seriousness and human enough to permit honesty.

A ninety-minute structure

A workable format is ninety minutes, facilitated by the manager or by a neutral colleague. The facilitator’s job is to protect the process, not to defend the year.

1. Frame the session (five minutes). Restate the purpose, the output, and the ground rules. Agree that the team will discuss systems and decisions rather than personalities. Note that the session will end with three commitments, not thirty.

2. Build an evidence wall (ten minutes). Ask each person to write one success and one frustration on separate notes. Place them on a wall or shared board under two headings: “What created value?” and “What created drag?” This prevents the meeting from being dominated by the first confident speaker.

3. Examine what worked (fifteen minutes). Cluster the successes and ask what made them possible. Look for repeatable conditions: a clearer brief, an earlier decision, a better handover, a smaller scope. The aim is not to admire the outcome but to identify the mechanism.

4. Name what to stop (fifteen minutes). Review the drag items. Ask where effort was spent without return. This is the most sensitive part of the session. Use system language: “What made this hard?” rather than “Why did this happen?” The output should be a short list of activities, meetings, or habits the team can reduce or remove.

5. Decide what to carry forward (twenty minutes). Choose no more than three experiments for the first quarter. Each should be practical, observable, and owned. For example: “Reduce the weekly status meeting to a written update and use the saved time for problem-solving.” Or: “Agree a single handover checklist for client work.”

6. Assign commitments (fifteen minutes). For each experiment, record an owner, a start date, and the evidence that will show whether it is working. Keep this to one page. A lengthy action plan is a sign that the team has not made choices.

7. Close with a clear message (five minutes). Summarise what has been decided and what has been deliberately left alone. Thank people for the specificity, not merely for their attendance.

A question set that avoids blame

The quality of a learning review depends on the questions. Useful prompts include:

• What did we do this year that made the biggest difference to our customers or colleagues?
• Where did we spend significant effort without a corresponding return?
• What did we tolerate that we should stop tolerating?
• What did we learn about how this team works best?
• What should we do more of, less of, or differently in the first quarter?
• What would we want to be true by the end of March, and what would tell us it is happening?
• What support does the team need from the wider organisation?

Avoid questions that invite a verdict on individuals. “Who struggled this year?” is not a learning question. “What made execution difficult in the third quarter?” is. The difference is not semantic; it determines whether people speak honestly.

Follow-through that survives January

The review is not the meeting. It is the routine that keeps the meeting alive. At the end, produce a one-page learning brief with three sections: what worked, what to stop, and what to test. Circulate it within two working days, while the conversation is still fresh.

Then attach the commitments to existing routines. The first team meeting of January should begin with the three experiments, not with a new agenda that buries them. Each commitment should appear in the relevant one-to-one. A thirty-day check should ask a simple question: what evidence do we have that this change is helping? At sixty days, the team should decide whether to keep, adjust, or abandon each experiment.

This is where many reviews fail. They treat follow-through as a separate project rather than a small adjustment to routines that already exist. The team does not need another dashboard. It needs the same meeting, the same one-to-one, and the same planning cycle to refer back to the decisions made in December.

The test of a good review

By the end of January, a useful review should leave the team able to answer three questions without consulting a document: What did we learn? What did we change? What difference is it making? If the answers are vague, the review was probably theatre. If the answers are specific, December has done more than mark the end of the year. It has given January a head start.