Kanban Board Template for Product Managers

Set the WIP limit for "In Progress" equal to your team size minus one. For a team of 5, start with a WIP limit of 4. For "Review," start with 2. For "Ready," start with the number of items your team typically pulls in a week. These are starting points. After 2-3 weeks, look at where cards pile up and adjust. The goal is to create a slight constraint that forces the team to finish before starting.

A scrum board resets every sprint. You fill it during sprint planning and clear it at the end of the sprint. A [kanban](/glossary/kanban) board is continuous: work flows through it without fixed time boundaries. Scrum boards have a committed scope. Kanban boards have WIP limits instead. Teams that do a lot of unplanned or reactive work (ops, support, platform) often find kanban more natural. Teams shipping large planned features may prefer the structure of sprints. The [Kanban Roadmap](/roadmap-type/kanban-roadmap) explains how to build a roadmap around continuous flow rather than sprint cycles.

Daily, either in a synchronous standup (15 minutes max) or an async Slack check-in. Walk the board from right to left. For each card in Review or In Progress, ask: "Is this moving? Is it blocked? Does it need help?" Once a week, do a replenishment session where the PM moves prioritized items from Backlog to Ready. Monthly, review your WIP limits and column definitions.

Only if your board has 15+ active cards and you need visual grouping to stay oriented. Common swimlanes: by work type (Features, Bugs, Tech Debt), by team member, or by initiative. For a small team with 8-12 active cards, swimlanes add visual noise without helping. Try without them first and add them when the board starts feeling crowded.

Any tool that supports column-based views with WIP limits will work. Linear, Jira, Notion, Trello, and GitHub Projects all support kanban boards. The tool matters less than the discipline. A physical whiteboard with sticky notes and Sharpie WIP limits on each column works better than a perfectly configured Jira board that nobody updates. The [Product Operations Handbook](/product-ops-guide) covers how to choose and configure tools for your team's workflow.