Kanban Board
看板
Aliases:看板任务看板kanban拖拽看板任务面板
What is it
A column-per-status task board — usually "To do / In progress / Done" — where cards move between columns as work advances. Column position is the process stage, a card's home is its status: the whole flow and its bottleneck column are visible at a glance.
Interactive playground
Try it. Make an informed choice.Loading lab…
✓ When to use
- Task management with stable, limited statuses — dev, hiring, content pipelines
- Teams that need bottlenecks visible — which column is piling up
- Lightweight personal pipelines advanced by stage
✕ When not to use
- More than 4–5 status columns — cognitive load explodes
- Complex dependencies and hierarchies — use a Gantt or tree
- Scheduling purely by time — a calendar fits better
Variants
Classic three-column
经典三列
To do / In progress / Done — the universal default
WIP limit
WIP 限制
Column header caps concurrent cards; overflow highlights
Swimlanes
泳道
Horizontal lanes inside columns by owner or priority
Implementation
flex/grid columnsdrag-and-drop or button movesdata-status per columnoptimistic moveStructure — a horizontal flex of column containers, each holding a vertical card list; moving a card is really a status-field change (optimistic update: move first, sync after). Drag ordering uses native DnD or pointer events; simple cases can settle for left/right move buttons. Show counts in headers; give empty columns a minimum drop-target height and keyboard users a button alternative to dragging.
Related concepts
Reorders list items by direct manipulation: press an item (or its handle), drag it to a target slot while neighbours give way and a drop hint appears. It turns ordering into a spatial, what-you-see-is-what-you-get action — with buttons kept as an accessible fallback.
PatternsSimilarUpdate the interface immediately as if the operation will succeed while the real request runs in the background; settle on success, roll back to the original state with a notice on failure. It solves the "wait for the server on every action" problem — trading brief uncertainty for a zero-latency feel, ideal for frequent light actions like likes and bookmarks.
PatternsSimilarAn admin home screen that concentrates key data and entry points into one view, organized as regional grids: header and sidebar handle navigation, while KPI cards, charts and a primary table fill the content area so users grasp system status at a glance and drill down directly. It anchors the information architecture of the product.
PagesUsed withA summary list on one side with the selected item's full detail on the other; clicking an entry updates the detail pane instantly. It solves the constant back-and-forth between list and detail pages — overview and depth share one screen, so users keep their sense of place and switching or comparing multiple items becomes cheap.
PatternsSimilar