Asana Kanban Tracking: Boards, Fields, and Automation
How Kanban Works in Asana
Asana represents Kanban as a project in board view. Columns are stages; cards are tasks; the goal is steady flow from one stage to the next without large queues.
Most Kanban teams settle on 4–6 columns. More columns add ceremony without information; fewer columns hide bottlenecks.
- Backlog → In Progress → Review → Done — the simplest pattern; works for many teams
- Backlog → Refined → Ready → In Progress → Review → Done — for teams with intake triage
- When Kanban beats list view — when stage is the dominant signal and item count is moderate
- When Kanban beats timeline — when no fixed deadline exists for the body of work
- Sub-tasks — visible on the card; useful for checklist-style detail without splitting work
If the team can\'t articulate what each column means in one sentence, the board needs simplification. Stage definitions live in a pinned task or the project description.
4–6 columns, clear stage definitions, sub-tasks for checklist detail. Simpler boards work better.
Fields, Labels, and Filters
Custom fields turn Kanban cards into structured data. Priority, owner, type, and customer are the most common; filters then narrow the board to what you want to see.
Field hygiene determines whether filters work. With five clean fields, filters answer real questions; with twelve sloppy fields, the board becomes noise.
- Priority — single-select; values High / Medium / Low or P0 / P1 / P2 (pick one and stick with it)
- Owner — built-in assignee field; one per card
- Type — single-select; Feature / Bug / Chore / Spike — useful for filtering and reporting
- Customer or project — text or dropdown; helps when one Kanban board serves multiple customers
- Custom field limits — soft ceiling at 5–7; verify field-per-task limits in plan tier before assuming unlimited
Filter the board, don\'t multiply boards. One board with smart filters scales better than five boards that need to be cross-referenced.
Five clean fields beat twelve sloppy ones. Filter the board; don't create more boards.
Automation for Kanban Flow
Kanban automation removes the small moves that slow the team down: assignments, reminders, and end-state cleanup. Each rule should save more time than it takes to maintain.
The most useful Kanban automations are quiet. They don\'t create notifications; they reassign or move cards based on data changes.
- Move on status change — when Status = In Review, move to Review column; clean and silent
- Auto-assign by type — Type = Bug → assign to QA lead; Type = Feature → assign to dev lead
- Due-date reminders — 24 hours before due date, comment with reminder; reduces missed cards
- End-state cleanup — when section = Done, archive after 14 days; prevents board sprawl
- Plan limits — Personal: no rules. Starter: 250 runs/month/project. Advanced: 25,000 actions/month/project.
Rules that fire constantly inflate plan-tier usage. Watch the rule runs counter monthly; if you\'re hitting the cap, audit which rules are overkill.
Automate moves and cleanup, not notifications. Watch plan-tier usage if rules fire often.
Dashboards and Bottleneck Tracking
A Kanban dashboard shows queue depth per column, aging cards, blocked work, and throughput. The combination surfaces where flow is stuck.
Six cards on a Kanban dashboard is enough for most teams. The board itself does most of the visual work; the dashboard adds trend.
- Cards per stage — count of tasks in each column; sustained growth in one column = bottleneck
- Cards per owner — count of tasks assigned to each person; helps spot personal bottlenecks
- Aging cards — tasks in In Progress longer than 7 days; flag for review
- Blocked tasks — list card; unblocking effort focus for the week
- Throughput — cards completed per week; trend over absolute number
- Workload — Advanced plan; combines effort with assignments for a fuller capacity view
If the In Progress column keeps growing while Done stays flat, the bottleneck is in Review or downstream — not the team\'s capacity to start work.
Watch queue depth, aging, blockers, throughput. Growing In Progress + flat Done = downstream bottleneck.
Kanban Limits and Alternatives
Asana's Kanban is competent. Trello wins for true simplicity; Jira wins for deep reporting; Linear wins for keyboard-first software teams. Pick based on the team's dominant need.
The alternative matrix below maps each tool to where it beats Asana. Useful for procurement conversations; less useful as a feature checklist.
| Need | Right tool |
|---|---|
| Mixed team, Kanban + other workflows | Asana |
| Single-board team, lowest ceremony | Trello |
| Software team, keyboard-first workflow | Linear |
| Complex agile reporting | Jira |
| Spreadsheet-feeling Kanban | monday.com |
- If the team only uses one board, Trello is faster to set up and easier to maintain
- If Kanban is one of many workflows the team runs, Asana\'s versatility wins
- Reporting gap: Asana\'s Universal Reporting (Advanced) covers most Kanban metrics; Jira goes deeper on cumulative flow and cycle time
Migrating Kanban boards between tools is fast; migrating organisations between tools is slow. Pick based on the broader workflow, not the board alone.
Asana for mixed workflows, Trello for single boards, Jira/Linear for software-heavy teams.
Frequently asked questions
Can I see WIP limits on an Asana Kanban board?
Not as a first-class UI feature, but you can enforce them via a custom field counter and a rule. The card count per column is visible at the top of each column. For strict WIP-limit enforcement with visual alerts, dedicated Kanban tools (Kanbanize, LeanKit) go deeper.
How many columns should a Kanban board have?
Four to six is the sweet spot for most teams. More columns add ceremony without information; fewer columns hide bottlenecks. The simplest pattern (Backlog / In Progress / Review / Done) works for many cross-functional teams; intake-heavy teams add a Refined or Ready stage upstream.
Does the free Asana plan support board view?
Yes. Board view is available on every plan including the free Personal tier. The paid tiers add Timeline, dashboards, Workload, Goals, Portfolios, and higher automation limits — none of which are required for basic Kanban tracking.
Can I automate moves between Kanban columns?
Yes, with rules. Common patterns: when Status field changes to "In Review", move card to Review column; when section = Done, archive after 14 days. Rules count against plan-tier usage (Starter 250/mo, Advanced 25,000/mo per project).
How does Asana Kanban compare to Trello?
Trello is simpler and faster to set up for a single board. Asana is more powerful when Kanban is one of several workflows the team runs (list view, timeline, calendar, dashboards). Teams that outgrow Trello often migrate to Asana; teams that find Asana heavy sometimes downgrade to Trello.