Kanban is a visual work management method that turns tasks into cards and the stages of your workflow into columns on a board, so everyone can see what the team is working on at the same moment. Its core rules are simple: make the work visible, limit how much is in progress at once, and measure how cards flow between columns to fix bottlenecks.
Key takeaways
- Kanban rests on visualisation, work-in-progress (WIP) limits and flow management, and you can start it without disrupting your current process.
- According to Microsoft's 2025 Work Trend Index special report, workers are interrupted roughly every 2 minutes during focus work; a WIP limit stops the half-finished jobs those interruptions leave behind from piling up.
- A good board starts with 4–6 columns, and each column needs a written definition of "done".
- Kanban suits continuous flow; for projects with deadlines and dependencies, use it alongside a Gantt chart.
- A weekly board review helps you spot stuck cards and recurring bottlenecks early.
Where did kanban come from, and what is it used for today?
Kanban means "signboard" or "visual card" in Japanese. The method grew out of the card system Toyota used on its production lines to make only the parts that were actually needed. It shares its thinking with other lean manufacturing tools such as the andon, which makes line problems visible the moment they occur.
Today kanban is used by any team handling recurring, continuously arriving work, from software developers and finance teams to agencies and purchasing departments. Its strength lies less in the tool than in the rules it sets.
What does invisible work cost a business?
The real problem kanban solves is that nobody can answer "who is working on what, and where is each job waiting?" When work is scattered across email, chat groups and personal lists, managers lose time in status meetings and staff lose time hunting for answers. Atlassian's State of Teams 2025 research, a survey of 12,000 knowledge workers and 200 executives, found that teams waste 25% of their time just searching for answers.
The second cost is starting too many things at once. According to Microsoft's 2025 Work Trend Index special report, the average worker receives 117 emails a day and is interrupted every 2 minutes by a meeting, email or notification during focus work. Every interruption leaves another job half-done, and half-done work neither delivers value to a client nor turns into an invoice.
This situation often begins with a task list in Excel and ends with a list nobody updates. We explain how teams reach that point in our article on outgrowing spreadsheets.
What are the core principles of kanban?
Teams that practise kanban agree on a handful of core practices:
| Practice | What it means | How it shows on the board |
|---|---|---|
| Visualise the work | Every job is a card, every stage a column | To do, In progress, In review, Done |
| Limit work in progress | A stage holds no more than a set number of jobs at once | A note such as "max 3" in the column header |
| Manage flow | Track how long cards take to move | Stuck cards, long-waiting jobs |
| Make policies explicit | Write the condition for moving a card on | Column description or checklist |
| Build feedback loops | Hold short, regular reviews | A weekly board meeting |
| Improve step by step | Change the process gradually, based on data | Adding, merging or redefining columns |
The practice teams skip most often is the WIP limit. Without one, the board becomes a nicer-looking to-do list: twenty cards pile up in "In progress" and none of them finish.
How do you set up a kanban board step by step?
A small team can work through the steps below in a week:
- Map the flow on paper. List, in order, the stages a job passes through from the moment it reaches the team to delivery. Write down how it really works, not how it ought to.
- Choose your columns. Start with 4–6. For most teams, To do, In progress, In review and Done are enough.
- Set a card standard. Each card should have a clear title, an owner, a due date and, if needed, a priority. Write "Send About page copy to client for approval" rather than "Website".
- Define "done". For each column, write the condition for a card to move on. For instance, moving from In review to Done might require client approval.
- Pick a WIP limit. A good starting rule is no more than two jobs per person in "In progress". When the limit is reached, help with a stuck job instead of starting a new one.
- Move all work onto the board. Turn jobs sitting in inboxes, notebooks and people's heads into cards. Agree from day one that work not on the board does not exist.
- Review weekly. Spend 15 minutes on the longest-waiting cards, columns over their limit and recurring blockers.
In work with shifting scope, such as software development, requirements need to be clear before you begin. Our guide to software requirements analysis helps you decide what each card should contain.
What is the difference between kanban, Scrum and Gantt?
Kanban is a continuous-flow method: work enters the board as it arrives, with no fixed period or sprint. Scrum splits work into fixed sprints of one month or less, often two weeks, and agrees the scope at the start of each. Kanban is the more common choice for ongoing work such as support, maintenance and content production, while product development tends to use Scrum or a mix of the two.
A Gantt chart answers a different question: "When will this project finish, and which late task would push the delivery date?" Kanban shows which stage a task is at right now; Gantt shows the order of tasks over time and their dependencies. Our guide to what a Gantt chart is explains how to read one. Projects with a deadline need both, and our guide to the critical path method shows how to find the tasks that directly affect delivery.
What mistakes do teams make with kanban?
- Too many columns. A twelve-column board shows the complexity of your process, not where the cards are.
- Setting a WIP limit but not enforcing it. If nobody stops when the limit is exceeded, there is no limit.
- Not updating cards. When finished work stays in "In progress", trust in the board fades and the team drifts back to email.
- Putting everything on one board. Separate boards for different clients or projects also make it easier to separate internal and external visibility.
- Letting meetings replace the board. A well-kept board shortens status meetings; for longer ones, AI meeting notes and summaries are another option.
Teams working on site have the same need for visibility; we cover the task flow between site and office in our article on construction project management software. If you want to compare tools before moving your board online, see the criteria in our guide to choosing project management software.
How does SmartPM make kanban task management easier?
SmartPM is the Smart family's web-based project management software, and it shows the same tasks as a list, a kanban board and a Gantt chart. Every project opens with To do, In progress, In review and Done lists, and moving a card from one list to another changes its status. You can name and colour columns and mark which one counts as done; a column that still holds tasks cannot be deleted by mistake.
Picture a digital agency. The project manager uploads the client's proposal or task list to SmartPM's AI-assisted "plan from a document" feature; the items become phased, timed and labelled cards that can be corrected before saving. Team members assign themselves to cards, which display checklists, attachments and due-date and comment badges. A designer presses q to filter only the cards assigned to them and starts the timer from the task panel, so time is recorded next to the work.
When a card reaches "In review", the team requests the client's approval. The client is added to the project with the Client role and sees only tasks marked "visible to client"; internal tasks, time entries and the team list stay hidden. The client chooses Approve or Request changes, and the answer appears as a label on the kanban board. Changes reach everyone who has the project open within a few seconds, without a page refresh.
When the deadline matters, the same cards appear on the Gantt chart with their dependencies; if one job slips, the jobs that depend on it move forward automatically. Reports show overdue tasks and each person's workload, and the AI status summary pulls out delays and suggestions for the week. A practical approach in SmartPM is to agree the WIP limit as a team rule and track it with the workload report. See the SmartPM kanban and task management page for details.
How Digital Bridge can help
Digital Bridge plans your SmartPM set-up together with you; at the start we discuss how to arrange columns, labels, project roles and client access around your workflow. Team and client users work with a single sign-in through their Smart360 account. If you need a bespoke process or a connection to other systems that off-the-shelf software does not cover, our custom web software team builds it. Our guide to software project cost also helps you scope the budget sensibly.
For more project and software guides, browse our software articles. To see whether the board is working, a few KPIs such as the time each card takes to finish are enough.
Next step: see your team's work on one board
Pen and paper are enough to start with kanban today, but as the team grows and client approvals and deadlines come into play, you will need a digital board. To buy SmartPM, fill in the SmartPM sales form; you can explore every feature on the SmartPM product page and contact us with any set-up questions.