Kanban boards in Asana: how the board view compares to a dedicated tool
Asana does kanban through its Board view. A project set to Board shows its sections as columns, tasks as cards, and you drag cards from one column to the next as work moves along. The same tasks can be viewed as a list, a calendar or a timeline, so a kanban board in Asana is one view of a project rather than a separate kind of object.
What Asana does not have is a built-in column limit. Asana's own kanban page says that work in progress "can be limited by using custom fields and rules to flag WIP limits", which is a workaround rather than a setting. Whether that matters depends on how strictly the team runs kanban. This article covers the setup using the names Asana shows on screen, how the kanban practices map onto Asana's features, what each plan includes (checked on Asana's pricing and help pages on October 8, 2026), and when a dedicated board tool is the better fit.
Setting up a kanban board in Asana, step by step
Asana's help article on board view describes the setup. In order:
1. Create the project as a board
Click the Quick Add button in the top bar and select Project, then click +Blank Project. In the window that follows, choose Board as the project layout and default view, then click Create project. Right-clicking the Board tab and choosing Set as default makes it the view everyone sees first.
2. Add the columns
In Board view, columns are sections. Click + Add section or the section placeholder and type a name. A typical kanban set is Backlog, Ready, In Progress, Review and Done. Dragging a task onto the section placeholder also creates a new section.
3. Add cards
Use +Add task at the bottom of a column, the + button next to a section name, or the main +Add task button. Each card can show the assignee, due date, subtasks count and custom fields.
4. Arrange the columns and cards
Drag sections to reorder them and drag tasks between them. Ctrl or Cmd plus click selects several tasks at once to move them together. The three dot menu next to a section title lets you add a rule, rename, delete or add a section. A section has to be empty before it can be deleted.
5. Adjust how cards look
The Options button opens layout settings for card size, column color matched to field options, and whether card images are shown. Right-clicking a task gives Add cover image.
6. Save the view
Filters, sorting and grouping are set from the top left of the project. Save view saves the setup for everyone working on the project, and + Save as a new tab keeps it as an additional view.
How kanban practices map onto Asana
Kanban is more than columns. The table below lists the practices teams usually expect from a kanban board and how each one is handled in Asana, according to Asana's help center and kanban page.
| Kanban practice | How Asana handles it |
|---|---|
| Columns for workflow stages | Sections, shown as columns in Board view |
| Drag a card to the next stage | Native, with updates sent to collaborators when tasks move sections |
| WIP limit per column | No native setting. Asana suggests custom fields and rules to flag a threshold |
| Swimlanes | Group by a field, with a subgroup to organize tasks into rows by section, assignee or custom field |
| Move cards automatically | Rules triggered by events such as a due date or completion |
| Cycle time | Recorded with custom fields or rules, then reported in dashboards |
| Other views of the same work | List, calendar and timeline (timeline from Starter) |
The pattern is consistent. The basic board works the same way it does in any kanban tool. The practices that make kanban a method rather than a to-do list, especially WIP limits and cycle time, are possible in Asana, but they are built from general features such as custom fields, rules and dashboards rather than offered as kanban settings.
For many teams that is fine. A team that uses a board mainly to see who is doing what will not miss a WIP setting. A team that runs kanban to control flow, and relies on a column turning red when it is overloaded, will spend time building and maintaining something that dedicated tools treat as a basic option. For comparison, GitHub Projects has a column limit setting that shows the count against the limit and highlights the column when it is exceeded.
Automating the board with rules
Rules are what make Asana's board more than a static picture. A rule has a trigger and an action. Section based triggers are designed for board view: when a task is moved into a section, a rule can act on it, for example by assigning it to someone. Rules can also move tasks between columns based on triggers such as a due date or completion.
Useful kanban rules include:
- When a task moves to In Progress, set a "Started" date field. When it moves to Done, mark it complete and set a "Finished" date. The difference between the two is the cycle time.
- When a task moves to Review, assign it to the reviewer.
- When a task is marked complete in any column, move it to Done.
Rules are reached through Customize in the top right corner of the project. On paid plans, a lightning bolt icon on a section shows that a rule applies there, and clicking it opens the rules for that section.
Some limits from Asana's help center are worth knowing:
- The custom rule builder is available on Starter, Advanced, Enterprise and Enterprise+.
- A project can have at most 50 rules, regardless of plan.
- A custom rule can have up to 20 triggers and up to 20 actions.
- Rules run on tasks and the first level of subtasks only.
- Edits to a rule apply going forward, not to past events.
Four board layouts that work well in Asana
Asana's kanban page lists several ways teams use boards. Each needs a slightly different set of columns.
Request intake. Columns such as New, Accepted, In Progress and Delivered. Requests for creative assets or bug fixes arrive in New and are assigned from there. A form on a paid plan can create the cards automatically.
Linear workflow. One column per stage of a process that always runs in the same order, such as Draft, Edit, Legal and Published. This is the closest to classic kanban, and the one where a WIP flag helps most.
Roadmap buckets. Columns named by quarter or by Now, Next and Later. Cards are initiatives rather than tasks, and they move rarely. Here the board is a planning picture, not a flow.
Sprint tracking. Columns for each step of a design or development sprint. The board is reset or duplicated for each sprint, so a project template saves setup time.
Choosing the layout before creating sections avoids the most common problem with Asana boards: columns that mix stages and categories, so a card could belong in two places at once.
Which Asana plan you need for kanban
Board view itself is available on the free plan. The features that turn a board into a working kanban system are on paid plans. Prices below are from Asana's pricing page on October 8, 2026.
| Personal (free) | Starter | Advanced | |
|---|---|---|---|
| Price | $0 | $10.99 per user per month billed annually, $13.49 billed monthly | $24.99 per user per month billed annually |
| Users | 2 | No user seat limits | No user seat limits |
| Board, list, calendar views | Yes | Yes | Yes |
| Timeline and Gantt | No | Yes | Yes |
| Custom fields | No | Yes | Yes |
| Automations | Not listed | Unlimited | Unlimited |
| Reporting dashboards | No | Yes | Yes |
| Free guests | Not listed | Unlimited | Unlimited |
| Storage | Unlimited, 100 MB max per file | Same | Same |
The free plan's two user limit is the deciding factor for most teams. A board for a team of three or more needs Starter. Because the WIP limit workaround depends on custom fields and rules, and cycle time reporting depends on dashboards, a team that wants to run kanban properly in Asana should plan on Starter from the beginning.
Starter also includes unlimited free guests. That makes it practical to bring a client or contractor onto a board without buying a seat for them.
When a dedicated kanban tool fits better
Asana is a general work management tool with a good board view. A dedicated kanban tool, or a project management tool where kanban is one of several first-class board types, makes a different trade-off. The questions below separate the two cases.
Is the board the main way the team works? If almost everyone opens the board every day and rarely uses list or timeline views, the extra structure of Asana adds steps without adding value. If the team switches between list, timeline and board for different audiences, Asana's single project with many views is a real advantage.
Does the team need WIP limits as a setting? If limits are part of the agreement on how work flows, a tool that shows them natively removes a rule and a custom field that someone would otherwise have to maintain.
How many people need full access? At $10.99 per user per month billed annually, a team of eight on Starter pays for eight seats. Tools differ a lot in how many people their free tiers allow, so the headcount often decides the question more than the features do.
Where does the conversation happen? Asana keeps comments on tasks. Teams that also need a chat channel next to the board usually connect a separate chat tool. Tools that put chat in the same place as the board avoid that split.
The side by side Asana comparison lists the differences in plan limits and included views, and the features page shows how kanban, Gantt and calendar boards share the same cards in one alternative.
Making the Asana board work better this week
For teams staying in Asana, a few changes make the board noticeably more useful.
Put the definition of done in the column names. "Review" is vague. "Review: code reviewed, QA passed" tells everyone when a card can move. Section names can be long enough to carry that.
Add a WIP flag with one rule. Create a single select custom field called "Over limit". Then add a rule on the In Progress section that sets it when a task arrives, and check the count in a saved view filtered to that section. It is not a hard limit, but it gives the team a visible signal.
Use subgroups for swimlanes. Group the board by assignee, with a subgroup by section, to see one row per person. Overloaded people stand out immediately.
Record start and finish dates automatically. The two rule setup described above gives cycle time data without anyone typing dates. After a month, a dashboard chart of cycle time shows whether the process is getting faster.
What to change first
Decide whether the team needs WIP limits as a hard rule or as a signal. If a signal is enough, set up the custom field, the section rule and the start and finish dates in Asana this week. If the team needs native limits, chat beside the board, or more people on a free tier, try a tool built that way: Pinateca is free for up to 5 people and 10 boards.
Q1. Does Asana have WIP limits on kanban columns?
Not as a built-in setting. Asana's kanban page suggests using custom fields and rules to flag WIP limits and alert the team when a threshold is reached. Custom fields and the custom rule builder are available from the Starter plan.
Q2. Is Asana's board view free?
Yes. The free Personal plan includes list, board and calendar views. It is limited to 2 users, so a team of three or more needs Starter or above.
Q3. Can I create swimlanes on an Asana board?
Yes, by grouping. Asana lets you group tasks and add a subgroup, organizing them into rows by section, assignee or custom field. Saving the view keeps the layout for everyone on the project.
Q4. How many rules can one Asana project have?
Asana's help center sets the maximum at 50 rules per project, regardless of plan. Each custom rule can have up to 20 triggers and up to 20 actions.
Q5. Why can I not delete a column in Asana board view?
In board view, columns are sections, and a section has to be empty before it can be deleted. Move its tasks to another section, or delete them, and then delete the section from the three dot menu.