Loading
Because the board is often a separate tool. It is kept current for standup, the plan is kept current for the client, and neither matches the third thing — what people are actually doing.
The Kanban board is a status view of the project's tasks, with columns from the project's own statuses.
Cards are tasks. Dragging one changes its status, which changes the plan, capacity and anything depending on it, because there is nothing between the card and the work.
A review column holds nine cards while build holds two. The bottleneck is visible without a report, and a work-in-progress limit on that column stops it recurring next week.
It will not show sequence. A board says what state things are in, not what has to happen first — that is the Gantt's job.
Status drives the plan and the client portal; blocked cards leave personal queues; and column limits warn before they are exceeded.
Yes, warning or blocking, per column.
Yes, filtered by label, client or team.
By person, phase or priority.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.