Kanban Board
A Kanban board is a visual layout of cards in columns that shows where each deal, lead, or task stands in a process, moving left to right as work progresses.
Last updated July 18, 2026
How a Kanban board works
A Kanban board organizes work items as cards arranged in vertical columns, where each column represents one stage in a process and each card represents one record — a deal, a lead, a support ticket, or a task. Moving a card from one column to the next (typically by dragging it) updates that record's stage in the underlying database. The board itself doesn't store any data; it's a visual representation of stage fields that already exist on each record.
In a CRM, the most common Kanban board tracks deals through a sales pipeline: columns like New, Qualified, Proposal, Negotiation, and Closed Won sit left to right, and each card shows a deal name, value, and owner. A rep scans the board to see exactly how many deals sit in each stage and how much revenue each column represents, without running a report.
Example
A five-person sales team keeps 40 open deals on a Kanban board with six stage columns. A manager glancing at the board notices 14 cards stuck in "Proposal Sent" — more than a third of the pipeline — and knows immediately that follow-up, not new-lead generation, is the bottleneck that week.
Why Kanban boards matter for CRM users
A Kanban board turns pipeline health into something visible at a glance instead of something a manager has to calculate. Column width and card count double as a status report: a column with too many cards signals a bottleneck, and a column with too few signals a gap in the process feeding it. This visual density is why Kanban boards became the default view for pipeline management in most modern CRMs, replacing the flat spreadsheet row as the primary way reps and managers interact with deal data day to day.
Kanban boards also reduce the friction of updating a record. Instead of opening a deal, finding a stage dropdown, and saving, a rep drags a card once. That single action can trigger downstream automation — a stage-change email, a task assignment, a Slack notification — so the board becomes both the interface a rep sees and the trigger point for the automation running behind it.
Kanban board limits
A Kanban board shows stage and basic card detail well, but it isn't suited to deep filtering, multi-field sorting, or bulk edits across hundreds of records. Teams with large volumes typically pair a Kanban view for daily triage with a list or table view for reporting, cleanup, and mass updates — the two views represent the same underlying records, just optimized for different tasks.