Using Kanban for Workflow Visualization
Read a DevStride Card view the Kanban way: where work piles up, what is late, what is blocked, and what the column totals and WIP colour are telling you.
What the board is showing you#
Open a perpetual board in Card view. Each column is a status; each card is one item. The picture answers four questions without opening anything:
| Question | Where to look |
|---|---|
| Where is work piling up? | Column item counts in each header, and any column that has turned red — it is over its WIP limit. |
| What is late? | Red card titles and Overdue dates. |
| What is blocked? | The purple relationship icon on a card; switch to 2D view to see the lines, including blockers on other teams' boards in the External Dependencies row. |
| How big is the load? | Board Totals in the footer — items, members, points, time estimate, time spent — and the same subtotals per column. Click a total for the breakdown. |
Reading flow, not just status#
- A long In Progress column with a short Review column means work is started faster than it is finished — the classic WIP problem. The red column is the prompt to stop starting and start finishing.
- Cards that have not moved for a while are the ones to ask about in standup. Add a Blocked Reason on the item so the reason travels with it.
- Use Filters → Assignee to see one person's slice, or the 2D view with Assignee rows and Status columns to see everyone's at once.
Keep the signal clean#
- Let an automation clear Done after a delay so the Done column does not swamp the rest: remove completed work after a delay.
- Hide card fields you do not read (Options → Hidden Fields) and save the layout as a View for the team.
How to move and rank cards: Track and move work with board views.