Kanban board

A Kanban board is a visual workflow tool: columns represent the stages work passes through — typically something like To do, In progress, Blocked, Done — and each task is a card that moves left to right as it progresses. The word comes from the Japanese for "signboard," and the method grew out of lean manufacturing before spreading to knowledge work. Its whole purpose is to make the state of every piece of work visible at a glance.

The discipline that makes Kanban more than a pretty task list is the work-in-progress (WIP) limit — capping how many cards can sit in a column at once. When a column is full, you finish something before starting something new, which surfaces bottlenecks instead of hiding them behind everyone being "busy."

Why it matters for MSPs

MSP delivery is a constant juggle between planned project work and reactive tickets. A board gives a team a shared, glanceable picture of what's moving, what's stuck, and who's overloaded — without a status meeting to extract it.

• Makes blocked work loud: a card parked in Blocked is a visible problem, not a silent one.
• WIP limits fight the start-everything-finish-nothing pattern that kills throughput.
• Gives daily standups a single artifact everyone reads the same way.

How it works in Current

Current includes a drag-and-drop Kanban board for project tasks, so moving a card between columns updates the task's status directly. It's one view of the same underlying plan that the Gantt timeline and dependency map draw — a card you drag to Done is the same task those views recalculate around. It suits day-to-day flow, while the timeline suits date and dependency planning.