Personal kanban without the board

Personal kanban is a way to manage your own work with two rules: make the work visible, and limit how much of it is in progress. Most people picture a board with columns and sticky notes. The board is the famous part. The limit is the part that actually helps.

Where it comes from

Kanban started as a way to manage flow in manufacturing and was later adopted by software teams. Jim Benson and Tonianne DeMaria Barry adapted it for individuals in their book Personal Kanban, and boiled it down to the two rules above. Everything else, the columns, the colours, the swimlanes, is optional.

Rule one: make the work visible

Work you cannot see tends to grow. Ten half-remembered things in your head feel like fifty. Written down, they are ten, and some of them turn out to be the same thing twice.

Making work visible means every piece of work you have committed to exists somewhere you can look at it. One item per problem or step, with a short title. It also means you can see the state of each item: not started, being worked on, waiting, finished.

Notice that none of this requires a board. It requires a list and a status.

Rule two: limit work in progress

The second rule is where the method earns its keep. You decide how many things may be in progress at once, and you do not start something new until something in progress is finished or deliberately put back.

Why it works:

• Less switching. Every item in progress is something you have to remember the state of. Three is manageable. Nine is not.
• Things actually finish. Starting is fun and finishing is work. A limit forces the finishing.
• Problems show up. When something sits in progress for two weeks, the limit makes it obvious. It is usually blocked, too big, or not really wanted.

For one person, a limit of two or three items in progress is a good start. If you run several projects, you can also limit how many projects are active at once. The guide on how to manage multiple projects goes into that.

Why the board is optional

A board shows the state of each item by where it sits. That is pleasant, and some people think best with things they can drag around. If that is you, use a board. There is nothing wrong with it.

But a board also invites work that is not the work. Designing columns. Adding a column for "almost done". Rearranging cards in a column as a form of planning. And a wide board is awkward on a phone, which is where many of us check our projects.

The same information fits in a list where every item has a status. You lose the dragging. You keep both rules.

Personal kanban with a list and statuses

Here is a setup that keeps both rules without a board:

1. One list per project. Each item is a ticket with a short title and, if needed, a few lines of detail.
2. A handful of statuses. New for not started, in progress for being worked on, blocked for waiting on something, done for finished, and cancelled for things you decided not to do.
3. A work in progress limit. Pick a number, for example two per project or three in total. Before you mark something in progress, check how many already are.
4. Blocked counts. A blocked item is still in progress in your head. Write down what you are waiting for, and treat it as part of the limit, or you will quietly bypass the rule.
5. Filter to what is open. Looking at only new, in progress and blocked items is the list version of glancing at the left side of the board.

The columns of a board map almost directly to statuses. If you want to think more about which statuses one person actually needs, see what personal project management is.

When an agent adds work

If an AI agent works on one of your projects, it will create work too: bug reports, follow-ups, questions for you. Visible work is good, so let it file tickets. But keep the limit yours. The agent can add new tickets and report progress; you decide what moves to in progress. A ticket the agent marks blocked is usually waiting on you, which makes it the first thing to look at.

Common ways it goes wrong

• No limit at all. Then it is just a to-do list with extra steps.
• Items that are really projects. "Build the app" will sit in progress forever. Break it into steps you can finish.
• Nothing is ever cancelled. A list full of things you will never do hides the ones you will. Cancel freely.
• The system becomes the hobby. If you spend more time tuning the board than doing the work, simplify.

The short version

Personal kanban is not about cards and columns. It is about seeing all your work and refusing to start more than you can finish. A list with honest statuses and a small limit does both.

If you want a tool that stays out of the way, Very Simple Projects is a simple personal project management app: a list of projects, numbered tickets with a few statuses, a thread on every ticket, and no board to maintain. It costs $0.99 a month, with the first month free.