Kanban Card Best Practices: What to Include on Every Card
Write effective Kanban cards with clear titles, descriptions, acceptance criteria, and labels. Learn what information every card needs to be actionable.
Best Practices
Detailed Explanation
Writing Effective Kanban Cards
A well-written card reduces ambiguity, speeds up work, and minimizes back-and-forth communication. Here is what every card should include.
Essential Card Elements
Clear Title -- A concise, action-oriented summary. Use the format:
[Verb] [Object] [Context].- Good: "Fix login timeout on mobile Safari"
- Bad: "Login bug"
Description -- Additional context that the title cannot capture. Include:
- What needs to happen
- Why it matters
- Links to relevant documents, PRs, or designs
Acceptance Criteria -- Specific conditions that define "done":
- "User can log in on Safari iOS 16+ without timeout"
- "Unit tests added for the new timeout handler"
Color Label -- Categorize the type of work:
- Bug, Feature, Tech Debt, Documentation, etc.
Tips for Better Cards
- Keep cards small. If a card will take more than 3 days, break it into smaller cards.
- One deliverable per card. Do not bundle unrelated tasks.
- Include a due date if there is a hard deadline.
- Update the description as you work. Add findings, blockers, or decisions so the card becomes a living record.
Anti-Patterns to Avoid
- Vague titles -- "Misc fixes" or "Various updates" tell nobody anything.
- Empty descriptions -- If you cannot describe it, it is not ready to work on.
- Zombie cards -- Cards stuck in a column for weeks. Set a policy: if a card has not moved in 5 business days, discuss it in standup.
- Mega-cards -- Cards representing weeks of work. These hide complexity and block flow.
Use Case
Use this guide when training team members on how to write cards that are clear, actionable, and appropriately scoped for a Kanban workflow.