OS Notion Project Management
Notion Tutorials · July 28, 2026 · 5 min read

How to Use Kanban Boards in Notion for Project Management

In short

Everyone knows how to drag a card between columns. Fewer people know how to set WIP limits that actually stick, or simulate swimlanes since Notion's board view doesn't support them natively.

Everyone knows how to drag a card between columns on a Kanban board. Fewer people know how to set WIP limits that actually hold, or how to simulate swimlanes, since Notion’s Board view doesn’t support two-level grouping natively. This guide covers both.

Beyond drag-and-drop

A Kanban board in Notion is just a Board view of your Tasks database, grouped by the Status property. The mechanics are simple; what actually determines whether it stays useful past week two is column discipline and WIP limits — covered below.

1 To Do unlimited 2 In Progress WIP limit: 3 3 Review WIP limit: 2 4 Done unlimited
A WIP limit is a team norm, not something Notion enforces — put the agreed number directly in the column name as a visible reminder.

Setting up your columns (Status property)

Keep Status to 4–6 options — To Do, In Progress, Review, Done covers most workflows. More granular stages feel precise but make the board harder to scan at a glance, which defeats the purpose of a Kanban view in the first place.

WIP limits: enforcing focus, not just visualizing it

Notion won’t stop anyone from dropping a sixth card into a column with an agreed limit of three — there’s no native enforcement. The practical fix: put the limit directly in the column name (“In Progress (max 3)”), so it’s a visible team norm every time someone looks at the board, and review weekly for columns quietly growing past it.

The swimlane workaround

Trello-style swimlanes — a second grouping dimension layered visually across the board — aren’t a native Notion feature. The workaround: build a separate, filtered Board view per lane (one per Assignee, or per Project), each still grouped by Status. Not visually identical to true swimlanes, but functionally equivalent for most teams’ actual needs.

Need a sprint-specific board instead of a general Kanban?

Software teams usually want a Backlog/Sprint split rather than a single flat board — see the agile-specific structure.

Read the software team guide →

Setup roadmap

Setup Roadmap

  1. 1

    Define your Status options

    Keep it to 4–6 stages — To Do, In Progress, Review, Done is enough for most teams.

    10 min

  2. 2

    Create the Board view, grouped by Status

    From the “+ Add view” menu on Tasks.

    2 min

  3. 3

    Add WIP limit labels to column headers

    Notion doesn’t enforce these, but note the agreed limit directly in the column name (e.g., “In Progress (max 3)”) as a visible team norm.

    5 min

  4. 4

    Build filtered board views for swimlane-style breakdowns

    One board per Assignee or Project, same underlying Status grouping.

    10 min per lane

  5. 5

    Review board health weekly

    Check for columns that are quietly growing past their intended limit.

    5 min/week

Launch checklist

Kanban Launch Checklist

  • Status property has 4–6 clear stages, not a dozen overlapping ones
  • Board view is grouped by Status and set as a default or pinned view
  • Agreed WIP limits are visible directly in column names, since Notion won’t enforce them automatically
  • Backlog and To Do are separate, not merged into one noisy column
  • Filtered per-person or per-project board views exist if the team needs swimlane-style breakdowns

Common mistakes

Common Kanban Mistakes

  • Too many Status columns. — Ten granular stages sound precise but make the board harder to scan than four honest ones — collapse anything that isn’t a meaningfully different state of work.
  • No WIP limit at all. — Without an agreed limit — even an unenforced, visible one — “In Progress” quietly becomes a parking lot for half-started work.
  • Expecting native swimlanes. — Teams that assume Notion works like Trello with Power-Ups end up frustrated by a missing feature; the filtered-board-per-lane workaround covers most of the same need.
  • One shared board trying to serve every use case. — A single board can’t be simultaneously a daily work view and a client-facing progress view — build separate filtered views instead of overloading one.

Free Notion Template

Kanban Board with WIP Limit Labels

The Starter Kit with a pre-configured 4-column board and visible WIP limit labeling.

Duplicate This Template →

Template link placeholder — replace href with the live Notion “Duplicate” share link before publishing.

FAQ

Does Notion support swimlanes like Trello Power-Ups?

Not as a native two-level grouping feature. The practical workaround is a second, filtered Board view per swimlane category (e.g., one board per Assignee or Project), rather than one board with visual lane dividers.

Can Notion enforce a WIP limit, or is it just a visual guideline?

It’s a visual/process guideline — Notion won’t block you from adding a fifth card to a column with a WIP limit of 3. Treat the limit as a team norm, and optionally add a view filter or a manual check to catch violations.

Should To Do and Backlog be the same column?

Usually not — keep Backlog as a separate, unpointed pool of everything that might happen, and To Do as specifically what’s committed for the current work period. Merging them makes the board noisy with unscoped ideas.

Can I have more than one Kanban board for the same Tasks database?

Yes, and it’s often useful — one board grouped by Status for daily work, another filtered to a single project or person as a focused view. Both are live views of the same underlying data.

Want this built for your business?

We turn workflows like this into a working Notion system in days, not months.

Find Your Solution

More like this