Board Swimlanes by Decision Owner: Seeing Who Holds Each Open Question

Workboard Pro editorial ·

A field notebook containing handwritten notes by botanist Sherwin Carlquist during a field expedition between 1988 - 2012 to Mexico, Florida, California, England, South Africa, Malaysia, New Zealand (islands of Rangitoto and Antipodes), and
Illustrative image. Carlquist, Sherwin John, 1930-2021 · CC BY 4.0 · Cropped and resized. Image source

Most task boards are built around stages: To Do, In Progress, Review, Done. Stages answer the question of where work is, but they rarely answer the question teams most often get stuck on, which is who is supposed to decide the next thing. A card can sit in In Progress for a week with no visible problem, while the real blocker is a pending decision that nobody has claimed. Swimlanes organized by decision owner change the picture. Instead of asking only what stage a task is in, you ask whose move it is. This article walks through how to set up that structure, what it reveals, and how to keep it honest without turning it into a scorecard for individuals.

Why stage columns hide the real bottleneck

Stage columns describe the workflow a team imagines. They are useful for showing progress, but they blur a common failure: work that is technically moving but waiting on a decision. When a designer needs a pricing answer before finishing a mockup, the card looks like active design work. The board shows it in progress, and nobody notices that the next step belongs to someone outside the design group.

Decision-based lanes make those waits visible. Each lane names a person or role who currently holds the next move. A card that appears in the 'waiting on finance' lane reads very differently from one in the 'designer is drafting' lane, even though both might sit in the same stage column. You can see at a glance which owners are carrying the most open decisions, which is often more informative than counting cards per stage.

Setting up decision-owner lanes

Start by listing the people or roles who regularly make decisions that unblock work: a product lead, a finance contact, a client-facing person, an engineer who must approve a technical approach. Keep the list short. Five to seven lanes is usually workable for a small team. If you have more, group roles together rather than creating a lane for everyone.

Within each lane, keep your stage columns or use a simple status tag such as 'needs decision,' 'needs input,' or 'ready to proceed.' Avoid making the lane count the source of truth for who is assigned work. A card can have a doer and a decision owner, and those can be different people. Record the decision owner separately so the lane answers 'whose move is this' rather than 'who is typing on it.'

What to look for when you review the lanes

Once lanes exist, review them weekly with a short set of questions. Which lane holds the most cards? A heavy lane often points to a person who is a bottleneck, or to a decision type that lacks a clear process. Which cards have sat in a lane longest? Age is a strong signal: a decision that has waited for two weeks deserves a direct conversation rather than another reminder. Are any cards sitting in a lane with no named owner? Those are the most dangerous, because they belong to everyone and therefore no one.

Pay attention to cards that bounce between lanes. A task that moves from design to finance back to design several times suggests the original question was poorly framed. Rewriting the decision as a specific yes-or-no question, with a deadline, often resolves the loop faster than more meetings would.

A checklist for keeping lanes useful

Use the following checks when you set up or revise decision-owner lanes. First, confirm each lane has one named role, not a committee. Second, make sure every card in a 'needs decision' state states the specific question being asked. Third, set a rule for how long a decision can wait before it is escalated or reframed, and apply it consistently. Fourth, review lanes in the same weekly meeting where you review priorities, so decisions are treated as part of planning rather than as side notes. Fifth, retire lanes that stay empty for a month, since unused structure adds noise.

Finally, keep the focus on the work and the decision, not on the person. A lane showing that finance holds six open questions is a prompt to ask whether finance needs more time, a clearer intake form, or fewer requests. It is not a verdict on anyone's performance. Teams that treat lanes as a map of waiting rather than a ranking tend to keep using them, and that consistency is what makes the view worth having.