What is Kanban?

Marcel Tit

Written by

Marcel Tit

Read Time

2 minutes

Kanban is a project management tool that allows you to get a more visual overview of the tasks that either need to get done or are complete.


At its core, it consists of a physical or digital board with three columns (To Do, In Progress, Done) and tasks listed as story cards. Every card will be pulled from left to right until it gets done. Finally, they will leave the workflow.

More advanced ones are web-based and include workflow limits and priority lanes for urgent tasks. Also, these task management tools are proved to be efficient for remote tasks too. 

Kanban rests on three main principles that promote:

  • Workflow visualization
  • Work-in-progress (WIP) limits
  • Workflow measurement

Its main goal? To visualize and maintain the workflow while eliminating waste.

A brief history of Kanban

Taiichi Ono, an industrial engineer at Toyota, developed the Kanban in the 1940s as a scheduling system for the manufacturing sector. He inspired himself from the self-stocking techniques used by supermarkets, where consumption was based on customer demand. Hence the pull character of the system.

The system was first used at Toyota factories, in order to balance material supplies with actual production. Factory workers would communicate the inventory levels of specific materials through a card called “Kanban” (which literally means “signboard” in Japanese). Every card would be carried all the way to the warehouse, indicating the requirements for the demanded material.

Later, David J. Anderson pioneered the Kanban method to software development in 2010, as a tool for agile teams. Since then, Kanban has been a key component of project management solutions, which now includes everything from task management to automated invoicing software. It’s ideal for people who want to manage a project from A to Z— accounting included.

Why are Kanban boards useful?

Kanban boards didn’t simply gain popularity overnight. Their widespread acceptance is mainly due to the following four benefits:

  1. Visualize your project workflow – get your team to be more focused through project transparency.
  2. Identify and remove bottlenecks – add work limits for in-progress columns to avoid overproduction and eliminate different kinds of waste throughout the project.
  3. Improve team collaboration – allow your team to make better estimates on lead time (the time it takes a feature request to be completed), ultimately improving the project’s success rate.
  4. Speed up your workflow – since transparency leads to a faster process and less work.

Found this article useful? Please spread the knowledge and share it with your teammates and followers.

Subscribe via email

Get monthly tips on how to successfully run projects and remain sane at the same time.

Thank you for subscribing!

Hmm, something went wrong... Please try again.