Boards and backlogs are the two most common ways PM tools display work. They look different and suit different working styles, but they answer the same fundamental question: what needs to be done, by whom, and where does it currently stand?
Kanban boards
A Kanban board displays work as cards moving across columns that represent stages in your workflow. The simplest version has three columns: To Do, In Progress, Done. More mature boards add columns that reflect the team's actual process: Backlog, Ready, In Development, In Review, Done.
The power of a board is immediate visual status. At a glance, anyone can see how much work is in each stage, which items are moving, and which have been sitting in one column for too long. Cards that don't move are a signal — something is blocked, deprioritised, or unclear.
Kanban boards work particularly well for teams with ongoing, flow-based work rather than fixed project cycles. Support teams, operations teams, and marketing teams often prefer boards because work arrives continuously rather than in planned sprints. Agile development teams also use boards within their sprint cycles.
Backlogs
A backlog is a prioritised list of work items — typically features, tasks, bugs, or stories — ordered from most important to least. The top of the backlog is what the team works on next. The bottom is a holding area for ideas that may never happen.
Backlogs are the primary planning tool in Scrum. The Product Owner maintains the backlog, constantly re-ordering it as priorities shift and new information arrives. During sprint planning, the team pulls items from the top of the backlog into the sprint.
The key discipline of backlog management is ruthless prioritisation. A backlog with 400 items and no clear ordering is not a planning tool — it's a wishlist. A good backlog has a clear top 20 items that are well-defined and ready to work, and a long tail of lower-priority ideas that are acknowledged but not obsessed over.
Using boards and backlogs together
Most modern PM tools combine both views. The backlog is where work is captured, refined, and prioritised. The board is where active work is tracked through delivery. Think of the backlog as the queue and the board as the factory floor.
In a Scrum context: the sprint backlog (what the team committed to this sprint) often displays as a board, while the product backlog (everything that might be built) is managed as an ordered list. The team moves between the two views depending on whether they're planning (backlog) or delivering (board).
For a beginner PM, the practical habit to build is keeping both current. A board that hasn't been updated since Monday and a backlog where the top items are six months old aren't tools — they're decoration. The value of these views depends entirely on the discipline of keeping them accurate.
Summary & next steps
Boards display work as cards moving through workflow stages — great for visual status at a glance. Backlogs display work as a prioritised list — great for planning and sequencing. Most teams use both: the backlog for what to work on, the board for tracking it through delivery. Both require active maintenance to be useful.
Next: timelines and Gantt charts — the scheduling view that shows when work happens, how tasks depend on each other, and whether the project is on track.