What is a Kanban board and how to use it

By Equipo Onion 4 min read
In this article
  1. Where Kanban comes from
  2. The parts of a Kanban board
  3. How to set up your first Kanban board
  4. Example: a Kanban board for a marketing team
  5. Common mistakes when starting with Kanban
  6. Kanban, Scrum and other ways of working
  7. Start a Kanban board in Onion

A Kanban board is a visual way to organize work: every task is a card and every column is a stage in your process. When a task moves forward, its card moves to the next column. The whole team can see at a glance what is waiting, what is in progress and what is done.

This guide covers where the method comes from, the parts of a Kanban board, how to set up your team's first board and the mistakes worth avoiding early on.

Where Kanban comes from

Kanban is a Japanese word that roughly means "card" or "signboard". The system started in Toyota's factories, where physical cards signaled when to produce or restock parts. The core idea was to make only what was needed, when it was needed.

Over time, software, marketing and operations teams adapted that logic to knowledge work. Today there is a reference definition, The Kanban Guide by John Coleman and Daniel Vacanti, which sums up the method in three practices: defining and visualizing a workflow, actively managing the items in it and improving the workflow over time.

The parts of a Kanban board

A Kanban board has very few pieces. That simplicity is a big part of why it works.

Columns

Each column represents a state of the work. The most basic board has three: To do, In progress and Done. Many teams add their own stages, such as In review or Blocked, to match how they actually work.

Cards

Each card is a unit of work: a task, a bug, an article to write or a candidate in a hiring process. A good card has a clear title and just enough information to work on it, such as an assignee, a due date or a priority.

Work in progress limits

Work in progress (WIP) is the number of tasks that have started and are not finished yet. Limiting it keeps the team from opening many tasks at once and finishing none. We cover it in depth in our guide to Kanban WIP limits.

How to set up your first Kanban board

You do not need a full methodology to get started. These five steps are enough to have a useful board this week.

  1. Pick one concrete project. A launch, a content sprint or a client's backlog works better than "all of the team's work".
  2. Define columns based on your real process. Start with three or four stages and add more only when tasks sit in a state the board does not show.
  3. Write one card per task. Use titles that start with a verb, like "Write the welcome email".
  4. Add the information your team needs. An assignee, a date and a priority label are usually enough at first.
  5. Review the board together. A short check-in two or three times a week is enough to spot stuck tasks and decide what comes next.

To go deeper on designing stages, read our guide on how to design Kanban board columns.

Example: a Kanban board for a marketing team

Picture a team of three that publishes content every week. Their board could have these columns:

  • Ideas: proposed topics that are not approved yet.
  • Writing: articles someone is drafting.
  • Review: drafts ready for a second reader.
  • Scheduled: approved content with a publish date.
  • Published: what is already live.

Each card holds the channel (blog, newsletter or social), the publish date and the owner. In the weekly meeting, the team sees in seconds which articles are stuck in review and who has too many open tasks.

Common mistakes when starting with Kanban

  • Too many columns on day one. A board with ten stages is hard to keep up to date. Start simple and add columns when you need them.
  • Cards that are too big. "Redesign the website" describes a whole project. Break it into cards someone can finish in a few days, like "Define the homepage structure".
  • No limit on work in progress. If everything is in progress, nothing moves. Set a limit, even an informal one.
  • Boards nobody updates. An outdated board causes more confusion than no board at all. A regular team review fixes this.

Kanban, Scrum and other ways of working

Kanban does not require new roles or fixed cycles, so it suits teams with continuous work or priorities that change often. Scrum organizes work into fixed-length sprints instead. If you are choosing between them, read our comparison of Kanban vs Scrum.

Start a Kanban board in Onion

Onion is a free online Kanban board built for small teams. You can create color-coded columns, move cards with drag and drop and add properties like assignees, dates or tags. It also has a list view and roles for inviting your team. See all Onion features or create your first board at app.getonion.app.