It’s a Planv1.12.0

Kanban Board Examples for Intake, Reviews, and Shared Work

Compare three Kanban board layouts for request intake, review-heavy work, and shared delivery. See how to handle full columns, blocked cards, and urgent requests.

Andrii PoluosmakUpdated 6 min read

Compare Kanban board examples by looking at where your team gets stuck. Do requests sit unanswered in triage? Do finished drafts pile up before review? On a shared board, does an urgent request bump work someone has already started? Choose columns around those waits and agree on what the team will do when a column fills. Use the department name to tell you who owns the work, not where it belongs on the board.

Choose your layout by comparing where work waits

Open your board or task list and find the cards that haven't moved. Check whether a card needs an answer, a free reviewer, or a decision about which job the team takes next. Try splitting a column if its cards need different next actions. Combine two columns if the team does the same thing in both.

The authors of The Kanban Guide leave the layout to the team and call for rules that say when work starts, when it finishes, and how it moves. Mark the start point on any Kanban board template you copy. You can put a request on the board before you count it as work in progress (WIP). After you start it, count it until you finish it, even while it waits.

Kanban board examples: intake, review, and shared delivery

Use these Kanban workflow examples to pick a starting layout, then test the limits with your own cards.

1. Request intake: separate triage from ready work

Columns: New → Triage → Ready → In Progress → Done

TriageReadyIn Progress (2 of 2)
Request missing an acceptance conditionRequest ready for deliveryTwo requests already started

Kanban University describes replenishment as choosing requests that meet the readiness criteria when the team has capacity. Give triage and delivery separate decisions. Have the triage owner check that the card names what the requester needs, who can answer questions, and what the requester will accept as done. If something is missing, leave the card in Triage with the question on it. Move it to Ready once you have the answer.

Use this Kanban board example if requests that need answers keep getting mixed in with work the team can start. Leave the Ready card in place while both delivery slots are in use. Once a team member moves either started card to Done, someone on the delivery team pulls the next eligible request into In Progress and starts counting it as delivery WIP. If triage is quick and requests don't sit waiting for answers, try keeping the readiness check without a separate column.

2. Review-heavy work: show the queue and the review separately

Columns: Ready → Making → Waiting for Review → In Review → Done

MakingWaiting for Review (2 of 2)In Review (1 of 1)
Finished draft that can't enter the queueTwo drafts ready for a reviewerOne draft under active review

Leave the finished draft in Making if Waiting for Review is full. Note why it can't move and help clear the queue before taking on another draft. In its guidance on Kanban WIP limits, Atlassian suggests helping with reviews when the team reaches a limit. If approval belongs to a designated reviewer, gather missing references or check the queued drafts against the brief. In It's a Plan, use soft and hard column limits to show a warning or block a move into a full column.

After finishing the active review, the reviewer pulls the oldest eligible draft from the queue. You now have room to move the finished draft out of Making. Keep both review columns if the team needs to see which drafts still need a reviewer and which already have one. If the distinction seldom changes what someone does next, try combining them.

3. Shared delivery: make urgent work and blockers visible

Columns: Ready → In Progress → Verify → Done

LaneReadyIn ProgressVerify
StandardNext shared requestRequest blocked on another teamStandard item queued for verification
ExpediteUrgent request awaiting a decisionEmptyEmpty

A shared delivery board shows a blocked card still in progress in the Standard lane and a highlighted urgent card awaiting approval in the Expedite lane.

Kanban University defines expedite work by the high and immediate impact of delay. If you're comparing Kanban swimlane examples, check which requests each policy would admit. Have the delivery lead record what happens if the request waits, who approved the expedite, and what work has to pause. Try keeping one expedite active across the board. If a second urgent request comes in, have the lead choose which one gets the slot and record the trade-off. Keep the other request waiting.

If the urgent request qualifies, the delivery lead approves it, names who will take it, and checks for room. If the destination column is full, free a slot or follow a written exception. A lane doesn't give the team more capacity. After verification, move the card to Done and free the expedite slot.

Leave the blocked standard card in In Progress and count it against WIP. On the card, note what you're waiting for, who will follow up, and the next check-in. To find urgent items without changing their place on the board, you can save a filtered view of those cards in It's a Plan.

Test the columns and rules with live work

Start your next board check with the work closest to Done and work back toward intake. At each full stage, ask who can help finish or unblock a card. Note the cards that keep waiting and what they need. The authors of The Kanban Guide define work item age as the time since a card started. Track that apart from the review wait: a card you started days ago might have reached review this morning.

At the next check-in, keep a column if it shows the team a wait they can act on. Merge it with another stage if people make the same decision in both. If you keep hitting a limit, check what's holding cards in place before you raise it. Look at the work you paused to make room for an expedite and check whether anyone picked it back up. Drop the lane if your regular rules can handle urgent work.

Copy the closest layout into your board or start with an It's a Plan Kanban board view. Add your current work, including blocked cards, and agree on what the team will do the next time a column reaches its limit.

Key takeaway

Choose columns based on where work waits and what the team can do about it. Test the layout with live cards, and agree on what happens when a column fills, a card is blocked, or an urgent request arrives.

Andrii Poluosmak

Founder

Andrii founded It’s a Plan and leads its product and roadmap, from the open-source edition to Pro for teams. He works with the project’s contributors and the teams that run It’s a Plan.

All posts by Andrii Poluosmak

Put your next project on the board.

The open-source issue tracker you host yourself.