A board is not a straight line
Why does a neat left-to-right board so often feel disconnected from how the work really happens? Because real work branches, pauses, loops back, and reconverges. A single straight line does not describe that; it flattens it into a status illusion that looks clean while the real flow hides underneath. Boards are not inherently linear, that is a habit, not a law.
Design the flow on a canvas
ScrumDo lets a team design its workflow on a canvas instead of accepting a fixed template. Lay out the stages, parallel paths, review loops, and handoffs that fit the actual work, a support flow, a delivery flow, and a research flow can each look different because they are different.
- Lay out stages, branches, and loops that match the real path, including rework.
- Run several flows for several kinds of work instead of forcing one shape on all of them.
- Use classes of service so urgent and routine work follow different policies on the same board.
- Keep blockers and WIP visible so waits and stuck cards are obvious, not buried.
WIP limits are more than a maximum
Most teams think of a WIP limit as a single ceiling on a column. In practice, limits come in several shapes, and each protects something different. Used together, they keep flow honest without micromanaging people.
| Kind of WIP limit | What it does | Why it helps |
|---|---|---|
| Maximum | Caps how much can sit in a stage at once | Forces finishing over starting and surfaces bottlenecks |
| Minimum | Asks for a floor of work in a stage | Keeps a stage from starving and people downstream idle; signals when to pull |
| Horizontal (row / lane) | Limits work across a whole row or initiative, not one column | Stops one initiative from quietly hogging the board |
| Per person | Caps how much any one person carries | Protects people from overload and the multitasking tax |
| Work type | Limits a kind of work, bugs, support, features | Keeps one work type from crowding out the rest |
| Class of service | Limits by policy, for example Expedite = 1 | Enforces one-emergency-at-a-time and reserves capacity for the rest |
Structure everyone can agree on
Flexibility without agreement is just chaos with nicer columns. The value of designing the flow together is that the whole team, Crew, Managers, and the stakeholders reading the board, read it the same way. A column means the same thing to everyone, the definition of done is shared, and a card’s position tells one honest story instead of several conflicting ones.
Make it reflect the flow of value
The best structure mirrors how value actually moves to the customer, not just the team’s internal activity. Columns should show where value is being created, where it is waiting, and where it is at risk, so a glance reveals not "who is busy" but "where value is stuck." That is what turns a board from a task list into a flow of value the whole room can reason about.
Key terms
- Workflow canvas
- A surface where a team designs the stages, branches, and loops of its own flow instead of accepting a fixed template.
- Nonlinear flow
- Work that branches, pauses, loops, and reconverges rather than moving in one straight line.
- Flow of value
- The path work takes to become value for the customer, what the board should mirror, not just internal activity.
- WIP limit
- A constraint you design into the flow of work. It can set a maximum or a minimum, span a row, or apply per person, work type, or class of service, each a different sort of constraint that keeps the flow of value honest and moving toward the north it aspires to.