lean-stack
Menu

Kanban board examples: 15 boards from different settings

Kanban board examples for factories, hospitals, offices, software, sales, support, portfolios, classrooms and homes, with columns, WIP limits and lessons.

Updated October 24, 2026 · 12 min read · Kanban Software

By the lean-stack editorial team

Hiring

Applied

  • Candidate A
  • Candidate B

Screen · 4

  • Candidate C

Interview · 3

  • Candidate D

Offer

  • Candidate E

Content team

Ideas

  • Case study
  • FAQ page

Drafting · 3

  • Guide

Editing · 2

  • Newsletter

Published

  • Blog post

IT support

New

  • Printer
  • VPN

Triage · 5

  • Laptop

Fixing · 4

  • Email

Closed

  • Password

Bed management

Admit

  • Bed 4

Occupied

  • Bed 1
  • Bed 2

Discharge · 3

  • Bed 7

Cleaning · 2

  • Bed 9
Illustrative boards. Each team names its columns after the real steps in its work.

A kanban board example shows how the same idea, visible work with limits, adapts to different settings. This guide gives fifteen illustrative boards, each with columns, WIP limits and the problem the board revealed.

All fifteen are constructed examples, not case studies. The numbers are made up to show the logic, so set your own limits. The kanban method explains the principles behind them.

Key takeaways

Every kanban board lists workflow steps as columns and caps the work each step can hold.

The same layout idea works in factories, hospitals, offices and personal life.

A board usually reveals a queue or bottleneck within days of going up.

A kanban card needs only the details the next person needs.

What does a good kanban board example show?

A good example shows the workflow, the limit on each step and the delay the board exposes. Without the last part, a board is only decoration.

Visible status saves time that would otherwise go on asking. The McKinsey Global Institute estimated that interaction workers spend nearly 20% of their time looking for internal information or tracking down colleagues who can help with a task.

Read each example below for three things. What are the columns, where is the limit, and what became visible?

If you want ready-to-copy layouts rather than stories, see the kanban board template guide.

Five questions every board should answer

Whatever the setting, a working board answers five questions at a glance. If people still have to ask around, something is missing.

  • What work exists? Every open task, request or deal has a card.
  • Where is each item? Columns show the real steps, including waiting.
  • Who owns it? Each card names the person moving it now.
  • What is blocked? A flag or Blocked mark shows stalled work.
  • What comes next? Agreed priorities say which card to pull when space opens.

Manufacturing: two-bin replenishment

The two-bin system is a classic physical kanban example, and it uses no board at all. A workstation holds two bins of a part. When the first is empty, it is sent for refill and the second bin is used.

Full bin in use

Empty bin returning

Full bin waiting

The limit is two bins per part.

What the board showed

Say a part runs out when a refill takes longer than the second bin lasts. The system shows this at once, so the team resizes the bin or speeds up refilling. This is the pull logic of just-in-time and a pull system, as used at Toyota.

Hospital bed management

A hospital bed board treats each bed as a card and each ward step as a column. It shows where patients wait, which is often discharge rather than admission.

Admission planned

In bed

Ready for discharge

Discharge in progress

Bed cleaning

Bed ready

Limit: the number of physical beds, with a cap on Bed cleaning.

What the board showed

Say many cards sit in Ready for discharge by late morning. The board shows that a bed is blocked by paperwork or transport, not by demand. This kind of visual flow is common in lean healthcare.

HR hiring pipeline

A hiring board puts each candidate on a card and moves them through stages. It shows where candidates wait, which affects whether they stay interested.

Applied

Screening

limit 10

Interview

limit 5

Offer

limit 2

Accepted

Keep personal details off the cards and link to the hiring system instead, with board access limited to the people involved.

What the board showed

Say Interview fills to its limit while Screening keeps feeding it. The board shows that interviewer time is the constraint. The team can add interview slots or stop adding screens until space opens. Illustratively, time from application to offer was about 34 days, with candidates waiting 12 of those days for an interview slot. Adding two interview slots a week and holding screening at its limit brought it to about 24 days.

Marketing content kanban board

A marketing board follows each piece from idea to publication. It shows how many pieces are half-finished at once.

Ideas

Briefed

limit 5

Drafting

limit 3

Design

limit 2

Review

limit 2

Scheduled

Published

Swimlanes can separate blog, email and social.

Card fields

  • Working title
  • Topic or keyword
  • Audience
  • Draft owner
  • Reviewer
  • Channel
  • Publish date

What the board showed

Say Design always holds two cards and Drafting keeps handing it more. The board shows design as the bottleneck. The team may batch visuals or pair writers with a template to relieve it.

Software team board

A software team board is a common knowledge-work example. It comes from David J. Anderson's work on the Kanban Method in the 2000s. It shows where code waits between steps.

Backlog

Analysis

limit 2

Development

limit 4

Review

limit 2

Testing

limit 3

Deploy

Done

Card typesFeatureBugTechnical debtResearch spikeRelease taskDocumentation

What the board showed

Say Review keeps overflowing. The board shows that developers start new work instead of reviewing. The team then agrees to review before starting a new card. Illustratively, average time in Review fell from about 3 days to 1. See kanban project management for the method in detail.

Sales pipeline board

A sales board is a kanban board where each card is a deal. It shows how many deals one person can really work at a time.

Lead

Qualified

limit 15

Proposal

limit 6

Negotiation

limit 4

Closed

Limit: a cap per person on active proposals. An At risk swimlane holds deals that have gone quiet, so they stay visible without crowding the main flow.

Card fields

  • Company
  • Deal size band
  • Next follow-up
  • Lead source
  • Decision maker
  • Last conversation
  • Risks

What the board showed

Say a rep has ten open proposals but time to chase only six. The board shows that extra proposals age without a decision. Setting a limit pushes the rep to follow up before sending more. Illustratively, with a cap of six proposals per rep, the share of proposals that got a decision within 30 days rose from about 4 in 10 to 7 in 10.

Personal task board

A personal board uses a few columns and a small limit to stop you starting too much. It is the simplest example to try this week.

Backlog

This week

limit 5

Doing

limit 2

Waiting

Done

What the board showed

Say you move cards into Doing until nine are open. The limit stops that at two, and the Waiting column shows tasks stuck on other people. A free kanban board is enough to run this.

IT support board

An IT support board tracks tickets and uses classes of service to protect urgent work. It shows how long routine tickets wait behind urgent ones.

New

Triage

limit 3

Working

limit 6

Waiting for user

Resolved

SwimlanesUrgent (limit 2)Standard

Waiting for user keeps tickets that are stuck on the customer apart from internal delays.

What the board showed

Say the Urgent lane is always full. The board shows that most urgent tickets are repeats of the same fault. The team can fix the cause, using a method such as the five whys. In an illustrative month, 18 of 30 urgent tickets were the same printer fault. Fixing the driver cut urgent tickets to about 12 the next month, and standard tickets waited less.

Product discovery board

A product board follows an idea from first hint to measured result. It keeps raw ideas from being mistaken for roadmap commitments.

Ideas

Needs research

limit 4

Validated

Prioritized

limit 5

In delivery

limit 3

Released

Measuring

Card fields

  • User problem
  • Target user
  • Evidence source
  • Expected value
  • Dependencies
  • Success signal

What the board showed

Say Ideas holds 60 cards and Validated holds two. The board shows that research, not delivery, is the slow step. The team caps Needs research at four and closes ideas that wait a quarter without evidence. Tying each card to a minimum viable product test keeps the Validated column honest.

Operations request board

Operations teams take requests from many directions: facilities, suppliers, compliance and internal fixes. A board gives all of them one front door.

Incoming

Triage

limit 5

Planned

In progress

limit 6

Waiting on supplier

Review

Complete

SwimlanesFacilitiesProcurementComplianceImprovement

What the board showed

Say managers keep asking why requests vanish. The board shows that most of them sit in Waiting on supplier, outside the team's control. The team dates each waiting card and chases anything older than a week. Stakeholders can now see that the team is balancing limited capacity, not ignoring them.

Employee onboarding board

Onboarding a new hire touches HR, IT, the hiring manager and payroll. Each card is one new starter, so everyone sees what is ready before day one.

Offer accepted

Before start date

Accounts and equipment

limit 4

First week

Training

30-day check-in

Complete

Card fields

  • Start date
  • Manager
  • Role
  • Equipment needed
  • Checklist link

What the board showed

Say three starters arrive on their first day without a laptop. The board shows that Accounts and equipment begins too late. The team moves that step to ten working days before the start date and adds a standard checklist to every card.

Portfolio board

A portfolio board tracks initiatives, not tasks. Each card is a project or program, linked to its own team board.

Proposed

Evaluating

limit 3

Approved

Active

limit 5

At risk

Completed

Card fields

  • Owner
  • Business goal
  • Major dependencies
  • Risk level
  • Target quarter
  • Team board link

What the board showed

Say twelve initiatives sit in Active for a leadership team that can follow five. The board shows attention spread too thin. A limit of five forces a choice: finish or pause one before approving the next. If cards stall in Evaluating instead, the slow step is decision-making. Strategy work like this connects to hoshin kanri.

Continuous improvement board

An improvement board gives process problems a visible place, so they get an owner instead of coming up again at every meeting.

Ideas

Investigate

limit 3

Experiment

limit 2

Implement

Measure

Standardize

Card fields

  • Problem
  • Proposed change
  • Owner
  • Expected benefit
  • Test period
  • Result

What the board showed

Say the same complaint about missing tools comes up in three team meetings. On the board it becomes one card with an owner and a two-week test. The Standardize column matters most: a change that works gets written into standard work, as in kaizen and PDCA.

Classroom board

Teachers and students use boards to break a large assignment into stages, so it stops looking like one big deadline.

Assigned

Researching

Drafting

limit 2

Revising

Need help

Submitted

What the board showed

Say several students sit in Drafting the week before a deadline. The Need help column shows which of them are stuck rather than slow. The teacher reviews the board at the start of class and spends the time on those cards first.

Home and family board

A home board covers chores, repairs, school forms and trip planning. It works when the jobs are shared, because everyone can see what needs doing.

Ideas

This week

limit 8

Today

Doing

Waiting

Done

SwimlanesOne per person

What the board showed

Say one person ends up holding most of the chores. With an owner on every card, the imbalance shows on the fridge door. A paper board that everyone walks past often works better than an app here.

When does a board need swimlanes?

Swimlanes are horizontal rows that split a board by work type, urgency, team or client. Several examples above use them. Add one when:

Different work shares one flow

Bugs and features, or client and internal work, pass through the same steps.

Urgent work needs protecting

An Urgent lane with its own limit keeps urgent items from swamping planned work.

Several teams share a board

One lane per team shows whose capacity is in use.

Leaders want load by category

Lanes show what kind of work is filling the board.

Start with one split and add more only when someone needs it. Too many lanes make a board hard to scan.

Which board fits your setting?

Match the board to the thing on the cards. Tasks need a task flow, candidates a hiring flow and initiatives a portfolio flow. Start with fewer columns than you think you need.

Personal work

Backlog, Today, Doing, Waiting, Done

Add first: A WIP limit of two or three

Software

Ready, Development, Review, Testing, Done

Add first: Card types and a Blocked flag

Marketing and content

Ideas, Drafting, Review, Scheduled, Published

Add first: Channel labels

Support

New, Triage, Working, Waiting for customer, Resolved

Add first: An Urgent lane

Operations

Incoming, Planned, In progress, Waiting, Complete

Add first: Request categories

Portfolio

Proposed, Approved, Active, At risk, Completed

Add first: One owner per card

What does a kanban card example look like?

A kanban card holds a title, an owner, a start date and anything that blocks it. Keep it short, because the board must be readable at a glance.

Example card

Title
Update returns policy page
Owner
Sam
Started
3 March
Type
Standard
Blocked
Waiting for legal wording

Add a finish date when the card is done. Start and finish dates give you cycle time, which the flow metrics tools page covers.

Common patterns across the examples

In every example, the board exposes a queue in front of one constrained step. The fix is rarely working harder. It is limiting what enters that step.

Limits also reveal how much work was hidden. Teams often find more open items than they expected.

Hidden work has a cost even before it is late. Psychologist David Meyer, whose task-switching research the American Psychological Association summarizes, has said that even brief mental blocks from shifting between tasks can cost as much as 40% of someone's productive time.

To see how work in progress, throughput and cycle time connect, use the Little's Law calculator. For the full method, read the kanban pillar guide.

Seven habits that keep any board useful

The setting changes, but the habits that keep a board alive stay the same:

  • Limit active work: Too many cards in progress slow everything down.
  • Write clear titles: Start with a verb so anyone can read the card.
  • Agree movement rules: Everyone knows what lets a card enter the next column.
  • Show blockers on the card: Not in comments or private messages.
  • Review old cards: Aging work often has no clear owner or no real priority.
  • Use few labels: Each label should help someone filter or decide.
  • Change columns when the work changes: The board follows the process, not the other way round.

If updating the board takes longer than doing the task, simplify it.

Build your first board in an hour

  1. 0 to 15 min

    List the steps one piece of work goes through, including waiting, and write them as column headers.

  2. 15 to 30 min

    Write a card for every open item, and put each one in its current column.

  3. 30 to 45 min

    Count the cards in each column, and set a limit just below the count for each in-progress column.

  4. 45 to 60 min

    Agree when the team will look at the board each day and who moves cards. Note today's counts, so you have a baseline to compare after two weeks.

Frequently asked questions

What is a simple kanban board example?
A simple example has three columns: To do, Doing and Done, with a limit of three on Doing. Many teams start there. Add columns only when work waits between real steps.
What is an example of a kanban board for project management?
A project board might use Backlog, Planned, In progress, Review and Done, with a limit on In progress. Cards are tasks or deliverables. See kanban project management for how to run it.
What is a kanban card example?
A card typically shows a title, owner, start date, work type and any blocker. Keep it brief. The kanban board template guide lists suggested fields for several settings.
Are kanban examples only for software teams?
No. Kanban began in Toyota's factories and now appears in hospitals, offices, support teams and personal planning. The kanban method page explains its manufacturing origin.
Where can I run these boards for free?
A whiteboard, a spreadsheet or a free app plan is enough to start. Our free kanban board guide compares the options and what each limits.
How do I start my own kanban board?
List the real steps, write a card for every open item, set limits just below today's counts and agree a daily look at the board. The one-hour walkthrough on this page covers each step.

Choosing Kanban Software?

Read the buying guide: what to look for, mistakes to avoid and questions to ask vendors.

Open the guide

Related guides

Sources

Books and papers show their publication year. Web pages show the month we last checked them.

  1. 1.David J. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business (Blue Hole Press, 2010)
  2. 2.John Coleman and Daniel Vacanti, The Kanban Guide (kanbanguides.org, May 2025 edition, checked October 2026)
  3. 3.Jim Benson and Tonianne DeMaria Barry, Personal Kanban: Mapping Work, Navigating Life (Modus Cooperandi Press, 2011)
  4. 4.McKinsey Global Institute, The social economy: Unlocking value and productivity through social technologies (mckinsey.com, July 2012)
  5. 5.American Psychological Association, Multitasking: Switching costs (apa.org, March 2006, checked October 2026)

For vendors

Built a lean tool?

Submit it for review. Every tool is checked against our listing criteria and researched from public sources. Approved tools join their category in the next published batch.