Kanban boards in Asana: how the board view compares to a dedicated tool
A small team is already using Asana, or is about to, and the work mostly moves through stages: requested, in progress, in review, done. The board view looks like a kanban board, cards drag between columns, and it seems like the obvious choice. The real question is whether Asana used as a kanban board will stay comfortable once the team grows, dates start to matter, and people outside the team need to see progress. Or whether a tool built around boards first would be a better fit.
This article walks through how kanban works inside Asana, what the plans include as of September 2026, where the board view is strong, where teams tend to hit friction, and how to decide between staying in Asana and moving to a dedicated kanban board tool.
How the board view works in Asana
Asana is a work management platform built around tasks and projects. Every project can be shown in several views, and board is one of them. Asana describes its kanban boards as a way to "plot out projects and workflows using columns and cards", with cards that can be dragged from one stage to the next.
Columns are sections
In a board view, each column is a section of the project. If the same project is switched to list view, those columns become section headers in a list. This matters because the board is not a separate object. It is one way of looking at the project's tasks. Renaming a column renames the section everywhere.
Cards are full tasks
A card on the board is a normal Asana task. According to Asana, each card shows the due date, assignee, and subtasks. Opening a card shows the full task pane with description, comments, attachments, and any custom fields the project uses. Nothing is lost by working from the board instead of the list.
Switching views
Asana states that teams can "quickly switch from a Kanban board view to a list, Gantt chart timeline, or calendar view." That flexibility is one of the main reasons teams choose it. The same set of tasks can be a board for the daily stand-up and a timeline for a planning meeting, but only on plans that include timeline and Gantt, as covered below.
Rules and automation
On paid plans, Asana supports customizable rules that can move cards to other columns or assign tasks when something happens. A common example is assigning a reviewer when a card lands in the Review column. For teams that repeat the same hand-offs every week, this removes a lot of manual clicking.
What each Asana plan includes for kanban
Kanban features in Asana are spread across plans. Board view itself is available on every plan, but some of the features that make a board useful for a team are on paid tiers. The figures below are from Asana's pricing page, checked in September 2026.
| Plan | Price per user per month | User limit | Board view | Timeline and Gantt | Workflow rules |
|---|---|---|---|---|---|
| Personal | Free | Up to 2 seats per project and team | Yes | No | No |
| Starter | $10.99 billed annually, $13.49 billed monthly | Unlimited members | Yes | Yes | Yes |
| Advanced | $24.99 billed annually, $30.49 billed monthly | Unlimited members | Yes | Yes | Yes |
| Enterprise | Custom pricing | Unlimited members | Yes | Yes | Yes |
What the free plan means in practice
The Personal plan is designed for individuals. Asana's pricing page lists a limit of up to 2 seats per project and team, and notes that paid plans let teams add unlimited members. A team of three or more that wants to share one board will need a paid plan. Current prices and limits change, so confirm them on Asana's pricing page before deciding.
The jump in cost
For a team of five on Starter, the monthly cost is five times the per-user price. That is often reasonable for teams that use Asana's broader features: portfolios, goals, reporting, and integrations. For a team that mainly wants a shared kanban board with dates, it is worth checking whether the price is being paid for features the team will not use.
Where Asana works well as a kanban board
Asana's board view is not a thin add-on. For many teams it is the right answer. These are the situations where it tends to fit best.
Teams that already live in Asana
If the rest of the company tracks work in Asana, adding a kanban board for one team keeps everything connected. Tasks can be referenced across projects, and managers do not need to learn another tool to see progress.
Work that repeats with the same hand-offs
Rules that move cards, assign people, or set fields when a card changes column are useful when the same steps happen dozens of times. Content production, design requests, and support escalations often have this shape.
Teams that report upward
Asana's higher plans include reporting and portfolio features that roll up many projects. If leadership wants a single view of several teams, the board is only one small part of the value.
Tasks that belong to more than one project
Asana lets a single task appear in more than one project. A design request can sit on the design team's board and in the marketing launch project at the same time, without being copied. For cross-functional work, this avoids the familiar problem of two cards drifting out of sync.
Where teams tend to hit friction
The same depth that makes Asana powerful can make it feel heavy when the main job is a simple shared board. These are the points small teams most often mention.
The board is one view among many
Because Asana is task-first, the board is a view of a project rather than the center of the product. People who open Asana land in My Tasks, Inbox, or Home, not on the team's board. Teams that want the board to be the first thing everyone sees each morning need to build that habit on purpose.
Kanban practices need to be set up by hand
Classic kanban relies on work-in-progress limits: a cap on how many cards can sit in a column. Teams using Asana often handle this with conventions, such as writing the limit in the section name ("In progress, max 4"), or with custom fields and rules on paid plans. Before committing, test how the team will make limits visible, because a limit nobody sees is not a limit.
Columns multiply faster than they should
Because a column is just a section, adding one costs nothing, and boards drift toward a column for every possible state. A board with eleven columns stops being readable on a laptop screen, and cards sit in narrow stages that nobody actually manages. The practical fix is not specific to Asana: keep the columns to the stages where a card genuinely waits for a different person, and express everything else as a field or a tag on the card. If a column never has more than one card in it, it is a label, not a stage. This is worth deciding before the board fills up, because renaming and merging sections later means touching every card that sits in them.
Free plan size
For teams of three to five people, the free plan's seat limit is often the first wall. Everything else may work fine, but sharing a board across the whole team needs a paid plan.
Timelines sit behind a paid plan
Many small teams discover, a few weeks in, that they need to see dates as well as stages. On the Personal plan, timeline and Gantt views are not included. The cards already have due dates, but seeing them laid out against time requires upgrading.
Chat lives elsewhere
Asana has comments on each task and project messages, but day-to-day team conversation usually still happens in a separate chat app. That is a normal setup, but it means two places to check. Some teams prefer a tool where the board and the team chat sit side by side.
Asana compared with a dedicated kanban board tool
A dedicated kanban board tool puts boards at the center: the board is where people land, and other views grow from it. Some of these tools also include Gantt, calendar, and chat from the start. The comparison below is about the shape of the two approaches, not a ranking.
| Question | Asana | Dedicated kanban board tool |
|---|---|---|
| What is the core object | Tasks and projects, with board as one view | The board, with cards as its content |
| Where people land when they log in | Home, My Tasks, or Inbox | Usually the workspace and its boards |
| Automation | Rules on paid plans | Varies by tool, often simpler or none |
| Reporting across many teams | Strong on higher plans | Usually lighter |
| Timeline and Gantt on the free plan | Not included on Personal | Varies by tool, some include it |
| Team chat | Comments and messages, chat usually in a separate app | Some tools include workspace chat |
| Learning curve for a small team | Moderate, many features to ignore | Usually lower, fewer concepts |
When staying in Asana makes sense
If the company already pays for Asana, if automation and reporting are in use, or if tasks regularly span several teams, the board view is likely the better choice. Switching would split data across tools.
When a dedicated tool makes sense
If the team is small, works mostly from one or two boards, needs dates and chat as much as stages, and does not use Asana's reporting, a board-first tool can cost less and ask less of people. A side-by-side view of the differences is on the Asana comparison page.
How to test the fit in one week
Opinions about tools are cheap. A short trial with real work answers the question faster.
Pick one live project
Choose a project that is running this week, not a demo. Set up the same columns in the tool being tested, and move real cards during the real stand-up.
Write down three must-haves before starting
For example: everyone on the team can edit the board, dates are visible as a timeline, and a client can see progress without editing. At the end of the week, check each one with a yes or a no.
Count the clicks for the daily routine
Time how long it takes each person to find their cards, update them, and see what is blocked. The daily routine is what the team will repeat hundreds of times, so small differences add up.
Check what leaving would look like
Before putting months of work into any tool, check whether cards can be exported, and whether the team could move them to another tool if needed. If the team is coming from Trello, check whether the new tool can import boards directly.
Decide on a date
Set a day at the end of the week to decide. Running two tools for a month leaves the team with two half-updated boards and no answer.
What to change first
If the team already uses Asana's rules and reporting, keep the board there and make WIP limits visible in the column names. If the team mainly needs one shared board with dates and chat, run a one-week trial of a board-first tool on a live project. Pinateca is free for up to 5 people and 10 boards, which is enough to test that side by side.
Q1. Does Asana have a kanban board on the free plan?
Yes. Board view is included on Asana's free Personal plan. The free plan is aimed at individuals, with a limit of up to 2 seats per project and team, so a larger team sharing one board will need a paid plan.
Q2. Can Asana set WIP limits on board columns?
Asana does not present WIP limits as a standard board setting on its plan comparison. Teams commonly write the limit into the section name or use custom fields and rules on paid plans to flag when a column holds too many tasks. Check Asana's help center for the current options before relying on a specific method.
Q3. How much does Asana cost for a team of five?
On the Starter plan, Asana lists $10.99 per user per month billed annually, or $13.49 billed monthly, as of September 2026. For five users that is five times the per-user price. Prices change, so confirm on Asana's pricing page.
Q4. Can the same Asana tasks be shown as a board and a Gantt chart?
Yes, on plans that include timeline and Gantt views. The board, list, timeline, and calendar are different views of the same project tasks, so moving a card on the board or changing a date on the timeline updates the same task.
Q5. Is it hard to move a kanban board out of Asana?
Asana projects can be exported, but how smoothly they import elsewhere depends on the destination tool. Before committing to any tool for the long term, test an export and import with one real project so there are no surprises later.
