Kanban Board vs To-Do List: When to Switch

A to-do list answers one question: what still needs doing? A kanban board answers two more: where is each thing now, and what is being worked on? Stay with a list while the work is yours alone and each item is done in one go. Switch to a board when the work is shared, when items wait on someone else, when they pass from one person to another, or when you need to know who changed what. Switching does not mean retyping anything: paste the list in, sort it into columns, and agree two rules. It takes about an hour.

The difference, in one line each

• A to-do list has two states, done and not done, and an order.
• A kanban board has several states, one per column, and a card moves through them from left to right. Most boards also limit how many cards may sit in the doing column at once.
• The Kanban Guide↗ (opens in a new tab) calls those cards work in progress: items started but not finished. A list has no way to show them.

The simplest board is a list with one extra state. The Agile Alliance glossary describes a basic task board↗ (opens in a new tab) as three columns, To Do, In Progress and Done, with one card per task. That middle column is the whole difference: it makes “started but not finished” something you can see and count.

Signs your list has outgrown itself

The work is shared

Two people working from one list soon collide: both start the same item, or each assumes the other has it. A list says what is left; it does not say who has picked what up. On a board, moving a card into the doing column is the claim, and everyone can see it.

Items wait on something

An item waiting for a reply, an approval or a delivery is neither done nor being done. On a list it sits unticked among items nobody has started, and you have to remember which is which. On a board it sits in its own column, or carries a note saying what it is waiting on, and you can see how long it has been there.

Work changes hands

When one person does a piece of work and another checks it, the item has at least three states: to do, doing, and waiting for review. A list collapses those into one unticked line. A board shows the handoff, and it shows when finished work is piling up because nobody is reviewing it.

You need to know who changed what

A shared document tells you what the list says now. It rarely tells you who ticked an item, who deleted one, or when a priority changed. Once more than one person, or an AI assistant, can change the list, that history starts to matter. For why, see who changed what: an audit trail for AI agents.

Everything is half done

If most of the list is things you have started, the list is hiding the problem. A board makes the pile in the doing column visible, and a WIP limit gives you a rule for it.

People keep asking for a status update

The GOV.UK Service Manual describes a team wall↗ (opens in a new tab) as a shared space showing what a team has done, what it is working on now and what is still to do, which lets other people in the organisation see what the team is doing. If people ask you “where are we with X?” more than once a week, they want that wall.

When a list is still better

• The work is yours alone and nobody else needs to see it.
• Each item is finished in one sitting: phone calls, errands, the shopping.
• The items are steps in a fixed order, such as a release checklist or a packing list. A checklist is a list on purpose; putting its steps on a board loses the order.
• The work is driven by dates. If what matters is what happens on Tuesday, you want a calendar or a list with due dates, not columns.
• There are only a handful of items. Five things do not need a process.

A board for one person can still help if you tend to start too much at once; personal kanban covers that case. And if what you want is a list you and an AI assistant both read and change, see a shared AI to-do list.

What a board costs you

A board is not free. Cards have to be moved, not just ticked. Columns need rules, or the board becomes a list with extra steps. And digital boards have their critics: the Agile Alliance’s own entry on task boards says a virtual board offers much less flexibility than cards on a wall, and advises teams to gain experience with a physical one first. Keep the board as small as the work allows, with as few columns as you can.

How to switch in about an hour

The example below uses fenbs, whose Add many box, next to + New task on the board, takes a pasted list. Any board with a bulk import works the same way.

1. Gather the lists (10 minutes). The notes app, the document, the list in a chat, the sticky notes. Put them in one place.
2. Clean it (10 minutes). One task per line, a few words each. Delete anything done, and anything you know you will never do.
3. Mark the kind (5 minutes). On fenbs every task is a feature, an enhancement or a bug. Start a line with bug:, feature: or enhancement: to set its kind; lines without one take the kind you choose for the batch.
4. Paste it (5 minutes). Add many takes one task per line or a markdown list, including checklists. Indented lines under an item become that task’s note. You choose a lane, a priority from 1 to 10, and optionally a project and category for the whole batch, and you see a preview of every task before anything is created.
5. Sort it (15 minutes). Everything starts in To Do. Move what you mean to do soon into Next Up, and only what is genuinely being worked on into In Progress.
6. Agree the rules (10 minutes). How many tasks may be In Progress at once, and who moves a task to Completed. Write both down where everyone, and every AI assistant, will read them.
7. Bring people in (5 minutes). Invite whoever shares the work, and connect the AI assistant you already use if you want it to read and update the board.

bug: Checkout total ignores the discount code
feature: Export invoices as CSV
  Accounts asked for this monthly
enhancement: Faster search on the orders page
Renew the SSL certificate

Then retire the old list. Two sources of truth is worse than either one; the week after the switch is when people slip back to the list, so say out loud that the board is now the place.

What changes on fenbs, and what does not

A fenbs board has four fixed lanes, To Do, Next Up, In Progress and Completed, so there are no columns to design. Every change is recorded in the History with who made it and when, whether it was a person or an AI assistant, which answers “who changed what?” without anyone keeping notes. When a task is finished, it records how it ended: Completed, Won’t fix, Duplicate, Cannot reproduce or Obsolete, so crossing something off still says why.

Some things a list app may have and fenbs does not: there are no due dates, no reminders and no work-in-progress limit setting, so the limit is a rule you keep yourself. And if you need the list back as text, Copy as Markdown below the board copies the whole board as a Markdown list, lane by lane.