Kanban

A kanban board lays records out as columns of cards, where the column a card sits in is its status and moving a card between columns is how that status changes. Orvain's Kanban family is two column styles. The deal column gives each card a company logo, a deal number and a field list (website, amount, contact, categories, close date) over an attachment, comment and duration footer. The task column carries priority and category tags, a title and description, a progress bar, an avatar stack and comment and link counts.

The column, not the board, is the unit worth designing. Whether a board gets used comes down to how much a card says before anyone opens it, which is a triage decision, not a layout one: pick the two or three fields somebody reads to decide what to touch next and leave the rest in the detail view. The count pill deserves the same care. It is the number people quote in a stand-up, so it has to count what the current filter shows, not the column's whole contents.

5 blocks

Deal board

CRM pipelines, sales deal tracking, revenue-ops boards

Deal forecast

Sales forecasts where the money by stage matters more than the cards: weekly pipeline reviews

Task board

Sprint boards, project trackers, editorial pipelines

Sprint pipeline

Sprint and delivery boards that work to limits: the shape of the work at a glance

Task board, ink

Quiet team boards and editorial calendars where the cards carry the colour of the work, not the chrome

01

Using Kanban

Reach for it when

  • Work moving through a fixed set of stages everyone on the team names the same way.
  • Sets small enough that a column can be read top to bottom: a sprint, a quarter's open deals.
  • When the shape of the work is the question: where things pile up, what has stalled.
  • Records whose status changes far more often than any of their other fields.

Reach for something else when

  • Items genuinely in two states at once, or whose status is derived. A table with a status column and filters does not force a single bucket.
  • Columns hundreds of cards deep. Nobody scrolls that far; a filtered list or a saved table view finds the record instead.
  • Planning by date. A board says what stage something is at and nothing about when: a calendar or a schedule view answers that.
02

Where it shows up

01

Sales pipeline

Deals grouped by stage, each card showing amount, contact and close date. The column counts tell a manager where the quarter actually stands long before anybody opens a forecast report.

02

Sprint board

One iteration, one column per state. Tags carry priority, the avatar stack says who is on it, and the progress bar separates work that has genuinely started from work that has only been claimed.

03

Hiring stages

Candidates moving from screen to offer. This is the shared view in a weekly review, because a column that is emptying, or one that never does, is visible from across the room.

04

Content pipeline

Drafts moving from idea to published, where the editor mostly cares about what is stuck in review. A cover image makes a card recognisable faster than its working title ever will.

03

Questions

How many columns should a kanban board have?

As many as there are real stages, which usually lands between four and six. Past that the board scrolls sideways and the far column stops being looked at, which quietly hides the finished or blocked work. If you need more, merge stages nobody treats differently, or collapse terminal columns behind a count.

Does a kanban board need drag and drop?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.