Personal kanban: the three-column board that keeps you moving
By Gerald · 6 June 2026
Kanban started on factory floors and got adopted by software teams, and somewhere along the way personal kanban became its own thing. That is a good development, because a board is a genuinely great way to see your own work laid out in front of you. The mistake almost everyone makes is bringing team-sized complexity to a personal board that does not need any of it.
This is a personal kanban system designed for one person. Three columns, a firm rule against adding more, and a few habits that make it run itself. The reason it works is that it refuses to become the thing most boards become: a place where work goes to be stored and quietly forgotten. It works in any board tool you like, so take the system and apply it wherever you already work.
What kanban actually is, briefly
Kanban is just visualizing work as it moves through stages. Cards represent tasks, columns represent stages, and you move a card from left to right as the work progresses. That is the whole idea, and its power is that you can see, at a glance, what is waiting, what is happening, and what is done. The original factory version added strict limits on how much work could be in progress at once, and that limit, more than the cards themselves, is the part that makes kanban effective. Hold that thought, because it is the part personal boards almost always throw away, and it is the part that matters most.
Why most personal boards fail

The moment a tool lets you add columns, you add them. It feels organized and responsible. "Backlog", "Next up", "Doing", "Waiting on someone", "Blocked", "In review", "Someday or maybe", "Done". Each column made sense when you added it. Together they turned your board into a filing cabinet, and a filing cabinet is the opposite of a board. A board is supposed to show you motion. A filing cabinet just stores things and lets them gather dust.
Here is the failure in plain terms. A personal board has exactly one job: to answer "what should I do next" instantly, and to show you that work is actually moving. Every extra column makes the first job harder, because the answer is now spread across ten places, and it makes the second job impossible, because a task can sit in "Waiting" or "Someday" forever without anyone noticing it has not moved in months. The columns that felt like organization quietly became hiding places.
There is also a subtler failure: the time you spend tending the board. Adding columns, dragging cards between elaborate stages, deciding whether something is "Next" or "Soon", is all work about your work, and none of it is the work itself. A personal system should cost you almost nothing to maintain, because the moment maintenance has a real cost, you stop doing it on the days you are busy, which are exactly the days you most need the system to hold.
The three columns that are enough
- Triage. Everything new lands here. It is the inbox for tasks, the place you dump something the moment it appears without deciding anything about it yet. You have not committed to a Triage item; you have just caught it so it is not lost.
- Executing. What you are actually working on right now. This column should be short. If everything is in Executing, nothing is, because the word stops meaning anything. A short Executing column is the entire discipline of the system, the personal version of the factory's work-in-progress limit.
- Delivered. Done. The satisfying column. Tasks move here and stay as a visible record of what you actually finished, which matters more than people expect.
That is the whole system. New work gets triaged, committed work moves to Executing, finished work moves to Delivered. There is nowhere for a task to quietly pile up, because there is no "Someday" column to bury it in. If something does not deserve to be in one of those three places, it does not deserve to be on the board at all, and that clarity is exactly what a cluttered board lacks.
How to run it day to day
The columns are simple. The habits are what make them work.
Triage in batches, not continuously. Do not sort every task the moment it arrives. Dump it into Triage and clear Triage a few times a day. Continuous sorting is just the filing-at-capture mistake that kills task systems, covered in how to organize tasks without building a system you hate.
Cap your Executing column. Pick a number, maybe three to five, and refuse to exceed it. When Executing is full, you finish something before you start something new. This single rule is what turns a board from a wish list into a tool, because it forces you to actually complete work rather than start endless parallel threads that all stall at ninety percent.
Use a priority flag, not a new column. When something matters most, mark it as a priority so it rises to the top of Executing. You do not need a separate "Urgent" lane, because a separate lane is just another column on the road to clutter. A single flag does the job without breaking the three-column rule.
Let Delivered grow, and glance at it. It is your evidence that the week happened. On the days you feel you got nothing done, scroll Delivered and see the truth. That feedback loop is quietly motivating, and it is the reason not to hide completed tasks the instant you finish them.
Do a weekly sweep. Once a week, clear out Triage items you will never actually do, and be honest about anything that has sat in Executing too long. Five minutes keeps the board trustworthy, the same way a weekly note sweep keeps a note system alive.
Personal kanban for different kinds of work
The three-column model bends to most personal contexts without adding columns. For studying, Triage is the reading and problems you have been assigned, Executing is what you are working through this week, and Delivered is what you have genuinely finished. For a side project, Triage is your idea and feature backlog, Executing is the one or two things you are building now, and Delivered is what shipped. For household and life admin, Triage is everything that piled up, Executing is today's handful, and Delivered is done. The stages stay the same because the underlying shape of work is the same: things arrive, you commit to a few, you finish them. Resist the urge to add a column for each context. The whole point is that one simple board serves all of them, and the consistency is part of why it sticks.
Why the constraint is the feature
It is worth dwelling on why a limit can be better than freedom here, because it runs against the instinct that more options are always good. A board with unlimited lists optimizes for one thing: the ability to represent any possible workflow. That is genuinely valuable for a team coordinating complex, varied work across many people. But for an individual, the scarce resource is not flexibility, it is attention, and unlimited flexibility actively spends that scarce resource. Every time you can add a list, you face a small decision about whether to, and every list you add is a new place to scan and a new place for a card to stall. Three fixed columns remove that entire class of decisions, so the discipline is built into the board instead of relying on your willpower on a bad day. That is the kind of discipline that actually survives, because it does not depend on you being at your best.
Frequently asked questions
What is a personal kanban board? A simple board that visualizes your own tasks as they move through a few stages. The minimal effective version is three columns: what is waiting, what you are doing now, and what is done.
How many columns should a personal kanban board have? Three is enough for almost everyone. More columns tend to become hiding places where tasks stall unnoticed, turning the board into storage rather than a view of motion.
Is kanban good for personal task management? Yes, especially the constrained version. Visualizing work and limiting how much is in progress at once is exactly what keeps personal work moving instead of piling up.
What is the difference between a triage column and a backlog? A triage column is a short-lived inbox you clear regularly, not a permanent backlog you let grow forever. The distinction matters, because a backlog that never gets triaged is just clutter with a respectable name.
Related reading
- How to organize tasks without building a system you hate
- How to organize your notes: a simple system that survives real life
- Note-taking methods, ranked by how much they actually help
Three columns you actually use beat ten columns you hide work in.
If you want a board built around exactly this, three fixed columns and a priority flag instead of endless lists, that is how Flow works, and it is free to try. The system itself works on any kanban tool.
How many columns does your board have right now? I am curious whether it stays clean or quietly fills up.