How to run a Q4 project review on one board
The last quarter of the year has a particular kind of clutter. Projects that were urgent in March are still sitting on the board, half done. Actions waiting on people who changed jobs in July. Ideas that nobody remembers adding. If you carry all of it into January, Q1 starts heavy before it has started at all.
A Q4 project review fixes that. It is not a retrospective or a strategy session. It is a cleanup with one question asked about everything: close it, carry it, or drop it?
Pick an hour, not a day
Small teams do not need an offsite to review the year. Block one hour in early December, before people start disappearing for holidays. Put the board on a shared screen. Everyone who owns projects attends. That is the whole setup.
If your board is very large, split the hour across two sessions. The point is that the review happens, not that it is exhaustive.
Go row by row
On a 2D board, each row is a project, which makes the review mechanical in a good way. For every row, look at all four columns at once:
- Mine: what is still ours to do, and is it really still needed?
- Other: who are we waiting on, and how long has it been?
- Next Steps: is anything here actually going to happen next quarter?
- Done: did this project deliver what it set out to?
Then decide the fate of the row.
Close it
A project is closed when its outcome has been reached or when the remaining actions are trivial. Move the last items to Done, write one line of what it delivered, and collapse or archive the row. Closing feels small but matters: it is the only way the board stops growing forever. See the problem with growing task lists.
Carry it
A project carries into Q1 if it still matters and has a clear next action. For each carried row, check three things:
- Every action in Mine has a real owner and makes sense out of context
- Every action in Other names who you are waiting on
- There is at least one action in Next Steps that someone could start in the first week of January
If a carried project has no clear next action, it is not really carried. It is drifting.
Drop it
Some projects no longer matter. The client moved on, the idea was overtaken, the priority changed. Dropping is a decision, not a failure. Say it out loud in the review, so nobody keeps half-working on it. If something might come back, park the idea in a single "someday" row rather than leaving it scattered across active projects.
Clear the Other column first
The Other column is where most year-end mess lives: follow-ups nobody chased, approvals that went quiet, questions nobody answered. In Axtio, actions waiting in Other show their age, and after seven days they count toward the toolbar's "to chase" button. A Q4 review is the moment to chase every one of them or let them go. See the waiting-on-someone problem.
Write down what you learned, briefly
At the end of the hour, spend five minutes on two questions:
- Which projects went well, and what made them work?
- Which stalled, and where did they stall?
Most stalls on a 2D board are visible: work stuck in Other, or rows with nothing in Mine for weeks. That pattern is more useful for next year than any number. See bottleneck thinking for projects.
Leave a clean board for January
The goal of the review is a board you are happy to open on the first Monday in January: fewer rows, fewer stale actions, a clear next step in every remaining project. The planning for Q1 is easier when the board already tells the truth. See how to plan Q1 on one board.
A checklist for the hour
- Every row: close, carry or drop
- Every action in Other: chase or remove
- Every carried row: one clear next action
- Five minutes on what worked and what stalled
- Archive closed rows
It is the least glamorous meeting of the year and one of the most useful.