FreeTool
Productivity

Kanban Board — What It Is, How It Works, and How to Use One

Learn what a Kanban board is, how to set one up, and how to use it to manage tasks and projects effectively — with a free online Kanban tool included.

10 min read

Kanban board for task and project management

A Kanban board turns an overwhelming to-do list into a clear visual system. Instead of a single pile of tasks, you see exactly what is waiting, what is being worked on, and what is done — at a glance, in real time. It is the system used by software teams, product managers, freelancers, and students to stay organized without overcomplicating things.

The free online Kanban Board gives you a full-featured board in your browser — no account, no software, and no subscription required.


What is a Kanban board?

A Kanban board is a visual tool that organizes work into columns representing different stages of a workflow. Each task is represented by a card that moves from left to right across the columns as it progresses.

The name comes from the Japanese word 看板 (kanban), meaning "signboard" or "visual card." It was developed by Toyota engineer Taiichi Ohno in the 1940s to optimize manufacturing production by making the flow of work visible and limiting work-in-progress.


The basic Kanban board structure

The simplest Kanban board has three columns:

┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│    TO DO    │  │ IN PROGRESS │  │    DONE     │
├─────────────┤  ├─────────────┤  ├─────────────┤
│ □ Task A   │  │ □ Task C   │  │ ✓ Task E   │
│ □ Task B   │  │ □ Task D   │  │ ✓ Task F   │
│ □ Task G   │  │             │  │             │
└─────────────┘  └─────────────┘  └─────────────┘
  • To Do — tasks that need to be done, not yet started
  • In Progress — tasks currently being worked on
  • Done — completed tasks

This structure alone is enough for most personal projects and small team workflows.


Core Kanban principles

1. Visualize the work

The board makes work visible. You can see at a glance how many tasks are backlogged, how many are in flight, and how many are complete — without reading through a list or asking for status updates.

2. Limit work in progress (WIP)

This is the most powerful — and most overlooked — Kanban rule. Set a maximum number of tasks allowed in the "In Progress" column at any one time. Typical WIP limits: 1–3 tasks for an individual, 2–5 for a small team.

Why WIP limits matter: Multitasking is a myth. Research consistently shows that switching between tasks has a cognitive cost. Finishing one task before starting another produces more output than juggling five tasks at once. WIP limits enforce this discipline.

3. Manage flow

Watch for cards that sit in a column too long. A task stuck in "In Progress" for a week is a signal — maybe the task is too large and needs to be broken down, maybe there is a blocker that needs to be surfaced, maybe the estimate was wrong.

4. Make process policies explicit

Write the definition of "done" for each column on the board itself. When can a card move from "In Progress" to "Review"? When can it move from "Review" to "Done"? Clear exit criteria prevent cards from moving prematurely.


How to set up a Kanban board

Step 1: Define your columns

Start with the simplest setup that describes your actual workflow. Common column sets:

Personal tasks:

Backlog → To Do → In Progress → Done

Software development:

Backlog → To Do → In Progress → Review → Testing → Done

Content production:

Ideas → Outline → Writing → Editing → Publishing → Published

Bug tracking:

Reported → Confirmed → In Progress → Fixed → Verified → Closed

Customer support:

Incoming → In Progress → Waiting on Customer → Resolved

Start simple. You can always add columns later. Adding too many columns at the start creates a board nobody uses because it is too complex to maintain.

Step 2: Add your tasks as cards

Write each task as a single, actionable item. "Work on the project" is not a good card. "Write the introduction section of the project report" is better.

A well-written card:

  • Describes one specific action (not a project or theme)
  • Can be completed in a reasonable time (hours to a few days)
  • Has a clear definition of "done"

Step 3: Set WIP limits

Decide how many cards can be In Progress at once. For solo work: 1–2. For a team: roughly the number of team members.

Step 4: Start moving cards

Work on whatever is in "To Do," move it to "In Progress" when you start, and "Done" when you finish. Resist the urge to pull new cards into "In Progress" until your current cards are done.

Step 5: Review regularly

Look at your board at the start and end of each day. Weekly, review the "Done" column — what did you actually complete? Are there any recurring blockers?


Kanban vs. other productivity systems

Kanban vs. Scrum

Both are Agile frameworks, but they differ in structure:

Kanban Scrum
Work structure Continuous flow Time-boxed sprints (1–4 weeks)
Roles No required roles Product Owner, Scrum Master, Team
Change mid-work Allowed any time Wait for next sprint
Best for Ongoing maintenance, support, variable demand Projects with defined phases
Meetings Optional, as needed Daily standups, sprint reviews, retrospectives

Kanban is better for teams where the mix of work is unpredictable (support queues, ops work, personal task management). Scrum is better for product development with planned features.

Kanban vs. to-do lists

A to-do list is a flat inventory of tasks. A Kanban board shows the status and flow of those tasks. The board answers not just "what needs to be done?" but "what is happening right now?"

Kanban vs. Gantt charts

Gantt charts show tasks on a timeline — great for fixed-deadline projects with dependencies. Kanban shows the current state of tasks — great for ongoing work. Many teams use both: Gantt for planning, Kanban for execution.


Advanced Kanban techniques

Swimlanes

Horizontal swimlanes divide the board by team, project, priority, or person. Each swimlane has its own cards moving through the same columns.

┌──────────────────────────────────────────┐
│  Project Alpha                            │
│  [To Do]    [In Progress]    [Done]       │
├──────────────────────────────────────────┤
│  Project Beta                             │
│  [To Do]    [In Progress]    [Done]       │
└──────────────────────────────────────────┘

Labels and color coding

Color-code cards by type:

  • 🔴 Red = urgent / bug
  • 🟡 Yellow = in review / blocked
  • 🟢 Green = feature
  • 🔵 Blue = maintenance

Due dates

Add due dates to cards to surface time-sensitive items. Most Kanban tools allow filtering by due date or highlighting overdue cards.

Blockers

When a task is stuck — waiting on someone else, a dependency, or a decision — mark it as blocked. A blocked card should not occupy a WIP slot. Move it to a "Blocked" column or add a visual indicator so the blocker gets resolved rather than forgotten.

Card aging

Cards that do not move for a long time are a smell. Some teams use card aging (cards gradually lighten or show a visual indicator the longer they sit) to make stale work visible.


Kanban for personal productivity

You do not need a software team to benefit from a Kanban board. Solo use cases:

Job search: Applications → Interviews Scheduled → Waiting for Response → Offer

Learning: To Learn → In Progress → Practice → Mastered

Home projects: Ideas → To Buy → In Progress → Done

Writing: Ideas → Outline → First Draft → Editing → Published

Freelance work: Leads → Scoped → In Progress → Review → Invoiced → Paid

The key is to limit In Progress to what you are actively working on today, not everything you intend to work on eventually.


Common Kanban mistakes

Too many columns

Seven columns feels organized; using it feels paralyzing. Start with three. Add a column only when you find yourself consistently needing to distinguish a stage that does not fit the existing columns.

No WIP limit

Without a limit, "In Progress" fills up like a second "To Do" list. The board stops reflecting reality. Enforce a WIP limit from the start.

Tasks too large

A card that says "Build the new website" will sit in "In Progress" for three months. Break large work into cards that can be completed in one to three days.

Keeping "done" cards forever

"Done" columns grow until the board is cluttered. Archive or delete done cards weekly. The value of a done card is in completing it, not in keeping it visible.

Not reviewing the board

A board nobody looks at is just overhead. Build a daily habit of checking the board at the start and end of work.


Using the free online Kanban Board

The Kanban Board tool is a fully functional board that runs in your browser:

  • Create and name columns for any workflow
  • Add cards with titles, descriptions, and labels
  • Drag cards between columns as work progresses
  • Color-code cards by priority or type
  • Everything is saved in your browser's local storage — no account needed
  • Works offline after the page loads

It is ideal for personal projects, freelance work tracking, and small team coordination where a full project management suite would be overkill.


Frequently asked questions

Is Kanban only for software teams? No. Kanban originated in manufacturing (Toyota) and is used in hospitals, marketing teams, editorial teams, HR, personal productivity, and anywhere work can be visualized as tasks moving through stages.

How many columns should my Kanban board have? Start with three: To Do, In Progress, Done. Add columns only when a real process step exists between them. Five to six columns is common for software teams. More than six becomes unwieldy for most workflows.

What is a WIP limit and why should I use it? A WIP limit caps how many tasks can be In Progress at once. This forces you to finish work before starting new work, which consistently produces better throughput than doing many things partially. A common starting point: one WIP limit per person working the board.

What is the difference between Kanban and a to-do list? A to-do list is a flat collection of tasks. A Kanban board shows the status and flow of tasks across multiple stages. A to-do list answers "what needs to be done?" A Kanban board answers "what is happening right now and where is work getting stuck?"

Can I use Kanban for personal projects? Yes — it works extremely well for personal use. A simple three-column personal board (Backlog, This Week, Done) is often enough. The discipline of limiting "In Progress" is especially valuable for solo workers who tend to overcommit.

Does Kanban work for creative projects? Yes. Writers, designers, and other creatives use Kanban boards effectively. Columns like "Ideas → Drafting → Revising → Final Review → Published" map naturally onto creative workflows. The WIP limit helps prevent the creative trap of starting many projects and finishing none.


Kanban Board — What It Is, How It Works, and How to Use One — FreeTool24 | FreeTool24