There is no more satisfying place on a kanban board than the Done column. Every card that lands there is a small win — a thing that was hanging over someone’s head, now finished. So it is no surprise that most of us are happy to let it pile up. A tall stack of Done feels like proof that the team is working, that the week meant something. But leave it alone long enough and that same column quietly turns against you: a wall of hundreds of old cards you have to scroll past to find anything, hiding this week’s real work behind three months of ancient history.
Cleaning out the Done column is one of those tiny habits that keeps a board usable for the long haul. The trick is knowing when to clear it — because clearing too soon robs you of something valuable, and never clearing at all buries you. Here is a simple way to get the timing right.
Why a Bloated Done Column Actually Hurts
A crowded Done column isn’t just ugly — it costs you in real ways. The most obvious is speed and focus: when the right side of your board is a mile long, the eye has to travel past all of it, and the board stops giving you a clean at-a-glance read of where things stand. A board you have to scroll and squint at is a board people quietly stop opening.
There’s a subtler cost too. The Done column is supposed to answer a useful question — “what did we actually finish lately?” — but it can only answer it if “lately” is visible. When last Tuesday’s win is sandwiched between four hundred cards going back to spring, the column stops telling you anything about your current pace. And on many tools, thousands of stale cards genuinely slow the board down. Board hygiene isn’t fussiness; it’s what keeps the board fast enough and clear enough to trust.
The Simple Rule: Review, Then Archive on a Cadence
Here is the whole habit in one sentence: let finished cards sit long enough to be seen and reviewed, then archive them on a regular schedule — don’t clear them the instant they’re done, and don’t let them live forever.
For most small teams, that cadence is weekly. Once a week, you look at everything in Done, take whatever value is left in those cards, and then move them out. The point of the delay is that a card in Done still has a job to do for a few days: it’s evidence of throughput, a talking point for a review, a reminder of a decision. Once you’ve captured that, the card has given you everything it’s going to — and it’s just taking up space. That’s the moment to clear it.
Give Finished Work a Moment Before You Clear It
Before you sweep the Done column, spend two minutes actually looking at it. This is the step almost everyone skips, and it’s the one that makes the whole habit worth doing.
Read down the finished cards and ask a few quick questions. What did we ship this week — does it feel like a lot, or surprisingly little? Did anything sit in “Doing” far longer than it should have before it finally landed here? Is there a card that’s marked Done but doesn’t really meet your bar for finished? That last one matters: a Done column is only honest if everyone agrees on what “done” means, which is exactly why a shared definition of done is worth writing down. Skim, notice, maybe say a quick “nice work” to the team — and then archive. You’ll be surprised how much a two-minute glance at your own finished work teaches you about how the week really went.
When to Keep Cards Longer
Weekly is a good default, but it isn’t a law. Some finished cards earn a longer stay, and it’s worth knowing which ones.
Work you’ll report on later. If you invoice by project, review deliverables with a client, or summarize the month for your own records, keep the relevant Done cards until that reporting moment has passed. Clearing them too early means reconstructing what happened from memory.
Cards that are part of a bigger picture. If a finished task is a milestone in a longer effort — a phase of an onboarding, one deliverable in a project — leave it visible until the whole thing lands, so the board still tells the full story.
Anything still under discussion. If a card is technically done but might bounce back — a client hasn’t confirmed, a review is pending — it isn’t really finished. Consider a “Ready to review” or “Awaiting sign-off” step before Done so those cards don’t clutter your record of truly completed work in the first place.
Archive, Don’t Delete
Cleaning out the Done column should almost never mean deleting cards. Most kanban tools — KanbanBlocks included — let you archive finished work: it disappears from the active board but stays searchable if you ever need it. That distinction matters more than it sounds.
Archived cards are a quiet record of everything your team has shipped. Six months from now, when someone asks “when did we finish that client’s setup?” or “have we done a project like this before?”, the archive answers instantly. Deleted cards answer nothing. So when you do your weekly sweep, archive as your default and reserve deletion for genuine junk — test cards, duplicates, things created by mistake. Keep the history; just get it off the board you look at every day. If you’re pulling any numbers from your finished work, like a simple read on how much your team ships each week, archiving keeps that data intact while the board stays clean.
Make It a Standing Habit, Not a Spring Cleaning
The reason Done columns get out of control is that clearing them is nobody’s job until it’s suddenly an overwhelming one. Four hundred cards is a chore you’ll avoid; ten cards is a thirty-second sweep. The whole game is doing it often enough that it never becomes a project.
The easiest way to guarantee that is to bolt it onto something you already do. If you run a Friday wrap-up or a Monday planning session, make “clear the Done column” the last item on the checklist — it fits naturally into a weekly reset habit alongside tidying the rest of the board. Two minutes to review, a few clicks to archive, done. Do that every week and your Done column stops being a landfill and goes back to being what it’s meant to be: a short, honest, satisfying record of the work you actually finished. Keep it light, keep it recent, and let the archive hold the rest.