How to Run a
Year-End Retrospective

A retrospective is not the same as a recap. A recap lists what happened. A retrospective asks why it happened, what you'd repeat, and what you would not. Done well, it produces two or three decisions — not twenty. Done badly, it turns into a procrastination ritual that ends with a fresh January resolution list and no actual change.

This guide is written for the kind of retrospective that fits in a single quiet afternoon late in the year. It assumes you are reviewing your own life and work, not running a team ritual.

When to do it

The sweet spot is roughly mid-November through the second week of December. That window has three properties working for it. The year is almost over but not over, so memory is still warm. Holiday demands have not yet crowded the calendar. And the gap to January is wide enough that any decision you make has time to convert into structure, not into a New Year's resolution that fades by mid-month.

If you've already used the September Sprint to plan forward and the October Finish to execute, a November or early-December retrospective sits naturally as the third panel of the same triptych.

What to actually look at

Most retrospectives go wrong because they start with "what did I accomplish?" — a question that quietly biases you toward whatever you remember most vividly. A better starting move is to gather artifacts before you start judging anything.

Pull together, in front of you on one surface:

• The goals you wrote down at the start of the year, even if you stopped looking at them in March.
• Your calendar at a one-month-per-page zoom. Notice the texture of each month, not the individual meetings.
• Your bank or budget summary — the months where money moved most, in or out, often mark the months that mattered most.
• Any project board, journal, or note app you used regularly. Skim the entries; do not read every word.
• Photos from the year, scrolled quickly. Energy and presence show up here more honestly than in any to-do list.

Give yourself thirty minutes to gather these. Resist the urge to start analyzing while you collect.

Four questions that produce signal

Skip the generic "what went well" prompt — it will produce a polite, useless list. Try these instead:

1. Which decisions am I glad I made? Force yourself to name a real decision (a yes, a no, a quit, a start), not an event that happened to you.
2. Where did time go that I did not consciously choose? Look at the calendar artifacts. Recurring meetings, obligations that crept in, half-finished projects you kept paying attention to.
3. What did I outgrow this year? A relationship pattern, a job title, a way of working, a hobby. Outgrowing something is a signal, not a failure.
4. What would future-me regret if I do not change it? This is the question that should produce the discomfort. Sit with it.

Write answers in full sentences. Bullet points are tempting but tend to flatten the texture you are trying to surface.

Common traps

A few patterns sabotage almost every retrospective. Watch for them in your own draft.

• Mistaking activity for direction. A heavy quarter is not the same as a productive one. If you cannot explain what an effort moved toward, count it as activity, not progress.
• Counterfactual envy. Comparing your real year to an imagined alternate year ("if only I'd started in March…") is a way to feel bad without learning. Compare your year to the actual options you had at the time.
• Pile-on planning. The retrospective produces a long list of changes, all of which start on January 1. None of them will. Pick two changes, at most.
• Performing the retrospective. If you find yourself writing for an imagined reader — a manager, a future employer, a journal you'll publish — stop. The retrospective only works as private work.

Turning reflection into a decision

The output of a useful retrospective is not a list of insights. It is two to three concrete decisions. A decision has a verb (stop, start, change, schedule, drop) and a subject (this meeting, that project, that habit, that relationship).

For each candidate decision, ask yourself a single follow-up: what structure would make this stick when I'm tired in March? Habits that depend on willpower in March do not survive March. Habits that are built into your calendar, your spending, or someone else's expectations of you usually do.

If you cannot answer the structure question, the decision is not ready. Move it to a parking list, not into your January plan.

A short checklist for closing the year

• Gather artifacts before judging anything.
• Answer the four signal questions in full sentences.
• Resist pile-on planning — name two changes, not twenty.
• Attach structure to each change before promoting it from idea to plan.
• Use the year-end checklists for the practical close-out items you would otherwise forget.

The retrospective is the bridge between this year and next. The September Sprint is the bridge between next year's intentions and its execution. Both work better when the other one has been done honestly.