Kanban Basics for Personal Projects

Last reviewed on 2026-04-24

Kanban started on factory floors in the 1940s and moved to software in the 2000s. Most of what makes it work is unchanged: a visible board, a flow from left to right, and a limit on how much you can have in progress at once. The corporate versions pile on ceremonies and tools, but a personal kanban — for your own projects, side work, or study plan — needs almost none of that.

This guide describes the smallest useful version: what the board looks like, how to feed it, how to avoid the most common failure modes, and where kanban simply is not the right fit.

The three-column board

Start with three columns, in this order:

• To Do — things you have decided to do but have not started.
• In Progress — things you are actively working on right now.
• Done — things you finished.

Every task in the project goes on a card that moves from left to right across these columns. That is the entire method in one sentence. Everything else is refinement.

The rule that makes it work: a WIP limit

The most important rule in kanban is a limit on work-in-progress. Pick a number — three is a good starting point for a solo project — and refuse to have more cards in the "In Progress" column than that. When the column is full and you want to start something new, you first have to finish something or move it back to "To Do".

Without a WIP limit, the In Progress column fills up, nothing ever seems to finish, and the board stops reflecting reality. With it, two things happen:

• You finish more tasks, because context-switching drops.
• You start noticing your real bottlenecks, because blocked tasks sit in the middle column instead of being quietly replaced.

What goes on a card

Each card should describe a single deliverable, not a vague project area. A good card:

• Starts with a verb ("Write intro paragraph", "Book dentist", "Refactor auth module").
• Is small enough to finish in a day or two at most.
• Has a clear "done" condition — you should know when to move it right.

If a card sits in In Progress for more than a week, it is usually too big. Split it into two cards and put the parent in a separate "Epic" tab or as a coloured marker note.

Optional extras (add only when you need them)

The three-column board is the whole system. Everything below is optional, and every addition has a cost.

A "Waiting" column

Useful when you often have tasks that are blocked on someone else. Put cards here when the ball is in another person's court, and move them to In Progress when it comes back. Without this column, blocked work silently clogs the middle.

A "Backlog" column

Some people split "To Do" into a Backlog (stuff you might do) and a focused Next column (stuff you will do this week). Helpful once your To Do list has more than about 20 items. Before then it is noise.

Swimlanes

Horizontal rows that group cards by project or area — "Work", "Home", "Learning" — while the columns still represent status. Useful if you run multiple projects on one board; often easier to just use separate tabs per project.

Colour coding

Pick one meaning for colour. Common choices: priority (red / yellow / blue), area of life, or card type (task / bug / idea). Do not overload colour with two meanings at once.

How to feed the board

A kanban board needs a source of truth for what goes into To Do. Three simple routines cover most people:

1. Daily capture. When something comes to mind, add a card to To Do. Do not think too hard about the right column — just capture it.
2. Weekly review. Once a week, look at every card in To Do. Delete anything you have lost interest in. Split anything that is too big. Decide what you actually plan to pull into In Progress next week.
3. Monthly cleanup. Archive or empty Done so the board does not become a trophy wall. A kanban board is a working tool, not a record of past glories.

Common failure modes

"In Progress" is always full

You are missing a WIP limit or ignoring it. Pick a number and stop starting new things until old things finish. If the board still gets clogged, the cards are probably too big — split them.

Cards sit in Done forever

Done is for "finished and celebrated", not long-term storage. Archive Done at the end of every week. Keep Done small so the board feels alive.

Nothing ever moves

The board is probably out of date. If two days pass without touching it, it is no longer reflecting reality and will stop helping. Either revive it at the next weekly review or accept that you do not need it for this work.

Every card is "priority high"

Priority stops meaning anything. Force yourself to pick three real priorities and leave the rest unmarked.

When kanban is the wrong tool

Kanban is a flow method. It works best when tasks move through stages at a roughly predictable pace. It is a poor fit for:

• Pure research or exploration, where the work does not split cleanly into tasks that finish.
• Heavy deadline work, where a Gantt-style view of dependencies and dates matters more than flow.
• Very small personal checklists, where a plain list in a notes app is faster.

Building the board in CNotepad

Open CNotepad, create a new tab, and pick the "Kanban Board" template. That seeds three header notes — To Do, In Progress, Done — across the canvas. Put each task on its own coloured sticky note in the appropriate column. Drag to move a card between columns. Use the colour picker to mark priorities or areas.

Because the canvas is spatial, you can also mix the pure kanban columns with a "Waiting" cluster in the corner or a "Backlog" column further to the left, without changing anything about the underlying app.

A minimum viable kanban, in five steps

1. Create three columns: To Do, In Progress, Done.
2. Set a WIP limit for In Progress (three is a fine default).
3. Add tasks to To Do as cards, one deliverable each.
4. Pull into In Progress only up to the limit. Work until a card is done, then move it.
5. Do a ten-minute review once a week. Archive Done. Re-prioritise To Do.

That is the whole method. Everything else is garnish. Start with the minimum, notice where it creaks, and add only the extras that solve a real problem you have.

← Back to all guides