How to Set WIP Limits on a Basecamp Kanban Board

If you run a Kanban board, WIP limits are the one rule that does the most work. WIP stands for “work in progress,” and a WIP limit caps how many cards are allowed in a column at once. The point is simple: stop a team from starting ten things and finishing none. Basecamp has no native way to set a WIP limit on anything, and we’ll be straight with you up front: Assistant for Basecamp doesn’t add a hard cap either. What you can do is run a WIP limit as a visible team rule on a real board, and that turns out to be most of the value. This guide shows how.

What is a WIP limit in Kanban?

A WIP limit is a maximum number of cards you allow in a column. If your In Progress column has a WIP limit of 4, the rule is that no more than 4 cards can sit there at the same time. When the column is full, nobody pulls a new card in until someone finishes one and moves it out.

It sounds like a restriction, but it works the opposite way. A WIP limit forces a team to finish what it started before grabbing the next thing. Half-done work is the most expensive kind, because it ties up people and gives you nothing shippable. Limiting work in progress is how Kanban keeps the flow healthy: fewer things open, more things done.

The clearest sign you need one is a column that keeps growing. If In Progress has 12 cards and three of them haven’t moved in a week, that column is a parking lot, not a workflow.

Does Basecamp let you set a WIP limit?

No. Basecamp’s native tools have no concept of a column limit. Its Card Table gives you columns and cards you drag between them, but there’s no setting to cap how many cards a column holds, and to-do lists have no board view at all. You can eyeball a list and notice it’s getting long, but nothing warns you or stops the pile from growing.

And here’s the honest part: no extension can bolt a true, enforced cap onto Basecamp either, because Basecamp will always let anyone add another to-do to a list from its own UI. Assistant doesn’t ship a column-limit setting. What it gives you is the thing a limit actually needs to function: a board where the pile is visible the moment it forms. On that board, each to-do list becomes a column, so your project’s real structure is the board, and every column header shows how many cards are in it. (Everything the board does is on the Kanban board for Basecamp page.)

How to run a WIP limit on a Basecamp Kanban board

In practice, a WIP limit is a team agreement plus a visible count. Kanban teams ran limits on whiteboards with a number written above each column long before any tool enforced them. The same pattern works on Basecamp:

1. Get the board up. Install Assistant for Basecamp from the Chrome Web Store, open a project, and click Kanban. One admin connects the Basecamp account and everyone on it gets the board. The getting started guide walks through the first connection.
2. Write the limit into the column name. Rename the to-do list to carry its cap: In Progress (max 4). Because each column is a real Basecamp to-do list, the limit is now visible to the entire team, including people who never open the board.
3. Let the count do the policing. Each column header shows its card count, so In Progress (max 4) sitting at 6 is an instant red flag. When the count hits the cap, the rule is that nobody pulls in a new card until one moves out.

The limit lives in your team’s working agreement, not in a database setting. That’s how physical Kanban boards have always worked, and it has a real advantage: the rule survives even for teammates looking at the plain to-do list view.

What number should the limit be?

There’s no universal answer, but a few rules of thumb hold up:

• For an In Progress style column, start near your team size. A team of five rarely works five things well at once, so a limit of 3 to 5 is a sane starting point. If cards still stall, the limit is too high.
• Tighten the column that stalls, not the whole board. WIP limits matter most on the middle columns where work actually happens. A Backlog or Done column usually doesn’t need one.
• Adjust after a week or two. If you keep hitting the limit and shipping fine, raise it. If cards sit blocked, lower it. The right number is the one that keeps cards moving.

A limit you constantly override isn’t a limit, it’s a suggestion. The value comes from treating “the column is full” as a real stop.

Make the stall visible before it happens

A full column tells you something is stuck. To see why, pair the count with a couple of other signals on the same board:

• Statuses like Blocked or Waiting on client mark exactly which card is holding the column up. Here’s how to add custom statuses to Basecamp tasks.
• Grouping rebuilds the board by assignee or status, so you can see whose column is jammed. See how to filter and group Basecamp tasks.

Together these turn “the column is full” into “this card is blocked on the client, that’s why nothing’s moving.” For the full board reference, the Kanban help doc covers columns, filters, and grouping.

Where Basecamp’s own tools still win

Honesty matters here. Basecamp’s Card Table is a genuinely good tool if a board is all you want and you don’t mind tracking work separately from your to-do lists. It’s built in, it’s free, and there’s nothing to install. If your team already lives happily in Card Tables and a growing column has never hurt you, you may not need an extension at all.

What you can’t do natively is get a board over the to-do lists where most teams actually track work, or see per-column counts, statuses, and grouping in one view. That’s the specific gap Assistant fills, and it’s worth being clear that it’s a gap, not a reason Basecamp is bad at everything.

Does this move my data or replace Basecamp?

No. Assistant runs inside Basecamp and your data stays in Basecamp. The board is a view on top of your existing to-do lists; nothing is copied out, and teammates who don’t install the extension see Basecamp exactly as before. If you uninstall, your lists and items are exactly as you left them.

Assistant is one flat price, $29/month or $290/year for the whole team, unlimited seats, with a 7-day free trial and no credit card. Full details are on the pricing page.

The short version

A WIP limit caps how many cards a column can hold, which forces a team to finish work before starting more. Basecamp can’t do this natively, and no add-on can hard-enforce it. Run it as a team rule instead: put the board over your lists with Assistant for Basecamp, write the cap into the column’s name, and treat the column count hitting that number as a real stop. Start the limit near your team size and lower it the moment cards stop moving.