What is a Kanban card? Structure, examples, and best practices

A kanban board can hold dozens of tasks, but poorly written kanban cards slow the team down. People open a card and still need to ask who owns it or what the next step is. A clear kanban card keeps the key details in one place, so work moves with fewer follow-up questions.

If you are wondering what a kanban card is, how teams use it, or what a clear setup looks like in practice, this guide covers the core structure, key fields, team-specific examples, and a simple process to get started. It also gives you a practical starting point if you are looking for a kanban card template, comparing kanban cards templates, or searching for a kanban board sample.

What is a Kanban card?

A kanban card is one unit of work on a kanban board. It is a visual task card that moves across board columns from To Do to Done as the workflow moves forward.

Think of a kanban card as a sticky note that holds the owner, the due date, the result, and any context the team needs to finish the task without extra back-and-forth.

What should a Kanban card include?

A well-structured kanban card answers three questions: what needs to be done, who does it, and when. If you need a simple kanban card template, start with the core fields first, then add the rest only when your team really uses them. The exact task details may vary, but these card fields cover most workflows.

Required fields:

• Title — a short, specific task name. Write "Update homepage hero copy," not "Update site."
• Assignee — the person responsible for moving the work forward.
• Due date — the deadline or target date.
• Status — shown by the card's position in board columns such as To Do, In Progress, or Done.

Optional fields:

• Priority — a priority label such as High, Medium, Low, or color labels, depending on how the team marks urgency.
• Description — the task description with context, links, and details.
• Checklist — small steps inside the card, useful when one task has a few moving parts.
• Labels / Tags — a category or type, such as Bug, Feature, Content, or Ops.
• Attachments — files, screenshots, or documents linked to the task.
• Dependencies — work that must be completed before this card can move.

A weak kanban card looks like this: Title: "Fix it." Assignee: empty. Due date: empty. The team has no clear owner and no clear timing.

A stronger version looks like this: Title: "Fix checkout button alignment on mobile." Assignee: Alex. Due date: March 15. Priority: High. Checklist: test on iOS, test on Android, verify in staging. Now the task card can move without a verbal handoff.

Kanban card examples by team type

Good kanban cards keep the same structure across teams, but the details change with the work. These are also useful as kanban card examples for small teams, especially when the goal is to keep task setup clear without adding too much process.

Software Team

• Title: "Add password reset flow"
• Assignee: Dev
• Due: Sprint end
• Priority: High
• Checklist: API endpoint / Frontend form / Email template / QA
• Label: Feature

Marketing Team

• Title: "Write Q2 email campaign copy"
• Assignee: Copywriter
• Due: April 3
• Priority: Medium
• Checklist: Subject line variants / Body copy / CTA / Proofreading
• Label: Email
• Attachment: Brand guidelines.pdf

Operations Team

• Title: "Onboard new contractor — John Smith"
• Assignee: HR
• Due: March 20
• Priority: High
• Checklist: Send welcome email / Add to Slack / Set up access / Intro call
• Label: Onboarding

These examples also show a practical point. The more often a team repeats the same process, the more useful a checklist becomes. It reduces guesswork and helps people follow the workflow without stopping for clarification.

How to create Kanban cards in Vaiz

As a work management platform, Vaiz makes creating kanban cards straightforward. If you need to set up the board first, you can follow this guide on how to create a Kanban board in Vaiz. Once the board is ready, you can add cards directly in the column where the task should start, which also makes it easier to see how to create kanban cards in a practical workflow, then fill in the key details and move the work through the process as it progresses.

How to add a Kanban card:

1. Open the board where you want to create a new card and make sure you are in the "Cards" view.
2. Choose the column where the task should appear, such as Backlog, Todo, or In Progress.
3. Click "Add task" inside that column to create a new kanban card.
4. Add a title and keep it action-oriented. A simple verb plus object works well, like "Review landing page copy" or "Prepare April invoice draft."
5. Assign a team member and set a due date. These two fields already make the task much easier to track.
6. Add extra context when needed, such as a description, checklist, attachments, or labels.
7. Use custom fields for anything specific to your process, such as content stage, approval owner, or client name.
8. Save the card and move it across the board as the work progresses.

A few Vaiz features make this easier in real work:

• Custom fields let you add the extra card fields your workflow needs without turning the setup into a long admin task.
• Tasks linked to documents help when the card needs a brief, spec, or draft right inside the task.
• Multiple views let you keep the same set of tasks in Kanban, List, or Timeline, so teams can switch views without rebuilding the process.

Create your kanban board and cards in Vaiz, free for teams up to 10, in Vaiz Boards.

Conclusion

A good kanban card is not about adding more fields for the sake of structure. Its job is to make the task clear enough that someone can pick it up and move it forward without a separate explanation. Start with the basics: title, assignee, and due date. Then expand gradually, adding only the fields your team actually uses. That keeps the board easier to maintain and the cards easier to trust.