
Last updated: September 8, 2026
A Kanban card is the unit of work on a Kanban board, one card per task, carrying description, owner, status, and due date, and it moves left to right as the work progresses. The idea comes from Toyota's 1940s production system, where a card was a signal to start work, which is why a board with no limit on cards in progress is not really Kanban. This guide covers the concept, what goes on a card, five common examples, and what digital cards add.
Forty open tasks, three of them yours, and no idea which one the designer is waiting on. That is the moment most teams reach for a board, and the thing they are really reaching for is the Kanban card: one task, one card, one place it can be.
There is a reason the one-card-at-a-time approach works. The American Psychological Association reports that the mental cost of switching between tasks can run as high as 40% of someone's productive time. A Kanban card pins down a single unit of work, so the team can finish it instead of paying that switching tax all day.
This post covers what a Kanban card is, the pull-signal idea behind it, what goes on a card, five common examples, and how digital cards extend Toyota's original with real-time collaboration and cycle-time data.
| Benefit | What it produces | Physical or digital? |
|---|---|---|
| Visibility | Task status, owner, and deadline visible at a glance | Both |
| Communication | Cards reduce status updates that would otherwise be meetings | Both |
| Efficiency | WIP limits per column prevent overload at any stage | Both |
| Flexibility | Cards move freely as priorities shift, no rebuilding required | Both, digital moves faster |
| Continuous improvement | Cycle-time analytics on digital cards expose bottlenecks for retros | Digital only |
Kanban card: the unit of work on a Kanban board, one card per task, carrying the description, owner, status, and due date in one place. It moves left to right across the columns as the work progresses, and its whole job is to pin down a single piece of work so the team stops switching between five.
Cards live on a Kanban board, which is divided into columns representing the stages of the workflow, usually something like "To Do," "In Progress," and "Done."
The visual nature of Kanban cards helps teams to quickly understand what tasks need to be done, who is responsible for them, and their current status. This transparency facilitates better communication and collaboration within the team.
Every card needs four things, and everything else is optional until it earns a spot.
| Field | Why it is on the card | Required? |
|---|---|---|
| Title | One line that says what "done" produces | Always |
| Owner | The one person who moves it, not a team | Always |
| Column (status) | Where it is in the workflow right now | Always |
| Due date | When it stops being optional | Always |
| Priority or tag | So a glance carries the context without opening it | When the board has more than one kind of work |
| Description | Enough that the owner's replacement could pick it up | For anything longer than a day |
| Subtasks or checklist | The steps, kept inside the card instead of as more cards | For multi-step work |
| Attachments and comments | The spec and the conversation about it, in one place | Digital boards only |
The first four are what let a card move at all. The rest are what let a card be picked up by someone who was not in the meeting, which is most of the point of writing it down.
Read more on how the timestamps on those moves become cycle time, lead time, and throughput.
The concept of the Kanban card originates from the Japanese manufacturing industry, specifically from Toyota's production system in the 1940s. The term "Kanban" itself means "signboard" or "billboard" in Japanese. The system was developed by Taiichi Ohno, an industrial engineer at Toyota, to improve manufacturing efficiency and reduce waste.
In the Toyota Production System, Kanban cards were used as visual signals to indicate the need to move materials within the production process. When a particular part or material was needed, a Kanban card would be sent upstream, prompting the production of more units. This just-in-time (JIT) approach ensured that inventory levels were kept to a minimum and production was closely aligned with demand.
Over time, the core principles of the Kanban system have been adapted for use in various industries beyond manufacturing, including software development, marketing, and project management.
The concept is a pull signal. On Toyota's floor a card did not describe work, it authorized it: a station could only start making a part when a card arrived asking for one. Nothing got built because someone upstream felt productive.
That single idea is why a Kanban card is more than a sticky note with a task on it. The card exists to limit how much is in motion, so a board where every task is "in progress" has kept the cards and thrown away the concept. It is also why the core principles put limiting work in progress right after visualizing it.
In knowledge work the pull is gentler, but it is the same shape. A card moves into a column when that column has room, and the empty slot is the signal to go get the next one.
Related: What Is a Scrum Master? Role, Responsibilities, and How Scrum Works (2026) — if your team runs Scrum instead of, or alongside, Kanban, this covers the role that keeps that framework moving.
The primary purpose of a Kanban card is to provide a clear, visual representation of a task and its status within a workflow. This visualization helps teams to manage their work more effectively by:
Basic Task Card: A simple Kanban card might include the task name, description, assignee, and due date. For example, a card titled "Write Blog Post" could have details like "Create a 1000-word blog post on Kanban cards," assigned to "John," with a due date of "June 20, 2024."

Subtask Card: For more complex tasks, a Kanban card might include a checklist of subtasks. For example, a card for "Launch Marketing Campaign" could have subtasks like "Design Graphics," "Write Copy," "Set Up Landing Page," and "Schedule Social Media Posts."

Bug Tracking Card: In software development, Kanban cards can be used to track bugs. A card might include details like the bug description, steps to reproduce, severity, and assigned developer. For instance, a card titled "Fix Login Bug" could include "Users unable to log in with Google," assigned to "Sarah," with a severity level of "High."
![]()
Sales Pipeline Card: Kanban boards work outside engineering too. Sales teams track each prospect as a card moving through pipeline stages like "Inquiry Requested" and "Committed." A card titled with the prospect's name, such as "Jennifer Chen," can carry contact details, the account's ARR, the assigned account manager, and a temperature label like "Hot" or "Warm," so one glance at the board shows which deals need attention today.

Feedback Card: Kanban cards can also be used to track customer feedback. A card might include the feedback description, customer name, and any follow-up actions. For instance, a card titled "Customer Feedback on UI" could include "Customer mentioned the interface is not intuitive," with follow-up actions like "Schedule a meeting with the design team."

Digital Kanban cards offer additional features and functionalities compared to their physical counterparts, making them even more versatile for modern teams. Here are some common uses:
Read more on Kanban swimlanes, the second axis that keeps a board readable past twenty cards.

Quire is a popular project management tool that incorporates Kanban boards. Here’s how you can get started with Quire Kanban cards:
By following these steps, you can use Quire Kanban cards to improve your team's productivity, communication, and project management.
A Kanban card does one small job: it holds exactly one piece of work still enough that someone can finish it. Everything else on this page, the origin story, the five examples, the digital extras, is in service of that. Write the first four fields on one card this afternoon and move it. That is the whole system, at a scale of one.
A Kanban card visually represents a task within a Kanban system, carrying details like description, status, assignee, and deadline. Cards live on a board divided into workflow columns.
Kanban cards came from Toyota's production system in the 1940s, developed by Taiichi Ohno to improve manufacturing efficiency. The term means signboard in Japanese.
Kanban cards improve visibility, communication, efficiency, flexibility, and continuous improvement. Teams spot bottlenecks faster and scale the system as they grow. A card earns those benefits only when it holds the real detail. In Quire the card is the task itself, with its assignee, dates, tags, description and comments, so moving it moves the record, not a summary, and the team stays productive at work because there is no second list to keep in step.
Common types include basic task, subtask, bug tracking, sales pipeline, and feedback cards. Teams often mix several types on one board.
Digital cards add real-time collaboration, attachments, notifications, analytics, and integrations. They're especially valuable for remote and distributed teams. The difference that matters most is that a digital card can contain work rather than just name it. Quire's cards are nested, so one card holds its own subtasks instead of spawning more cards in the column.