Running a Small Design Studio on a Kanban Board: Our Recommended Setup

Every design studio already runs a workflow — drawings get drafted, checked, revised, and issued. The question is whether that workflow is visible. In most small practices it lives in the team leader's head, a spreadsheet nobody opens, and a Friday scramble to discover what's actually ready for the submission. The work moves; nobody can see it moving.

Kanban fixes exactly this, and it fits deliverable-based design work unusually well — better, honestly, than it fits many of the software teams it's famous in. But the generic "To Do / Doing / Done" board you get by default throws away the fit. Here's the setup we recommend for a small studio: columns, cards, limits, and the weekly rhythm — all runnable on Taskboard, free, with no accounts to create.

The columns: model the drawing's life, not the person's day

The board's columns should be the states a deliverable passes through, because state transitions are where studio problems live. Our recommended pipeline:

Backlog → Drafting → Internal Check → Revisions → Ready to Issue → Issued → Closed

Why these seven:

• Internal Check as its own column is the load-bearing decision. In "To Do/Doing/Done" boards, checking is invisible — and checking is precisely where studio bottlenecks form, because drafting scales with headcount but checking runs through one or two senior people. Make it a column and the pile-up announces itself on screen instead of on deadline day.
• Revisions separate from Drafting distinguishes new work from rework. If the Revisions column is chronically fuller than Drafting, the studio doesn't have a production problem — it has a quality or briefing problem, and now you can see it.
• Ready to Issue decouples "the drawing is finished" from "the transmittal went out," which is where drawings wait for the full package, the cover letter, or the client's portal. Work sitting here isn't stuck; work sitting here for two weeks is.
• Issued vs Closed keeps a drawing visible while comments are pending, and archives it only when the ball is fully out of your court.

Adapt freely — a studio doing lots of authority submissions might add a With Authority column — but keep the principle: every column is a state someone can be asked about. "What's in Internal Check?" is a real question with a real answer. "What's in Doing?" is not.

The cards: one deliverable, fully identified

One card = one deliverable (a drawing, a model, a report — not "work on the hospital"). Each card carries:

• The deliverable number and title as the card name, matching your drawing register — the board and the register must speak the same language
• Current revision and the milestone it's targeting
• Owner — exactly one name; shared cards are orphaned cards
• Due date, driven by the submission date minus the checking and revision time it actually takes, not the optimistic version
• A checklist for multi-sheet or multi-stage deliverables, so partial progress is visible without splitting cards

Pro tip: Resist the urge to card every micro-task ("update titleblock," "plot to PDF"). The board's job is flow visibility, not time tracking — cards at the deliverable level stay meaningful for months; cards at the task level rot within a week and the team stops trusting the board. If a deliverable genuinely needs task tracking, that's what the card's checklist is for.

The one rule that makes it Kanban: limit Internal Check

A board without work-in-progress limits is just a prettier list. You don't need limits everywhere — one is enough: cap Internal Check at what your checkers can genuinely hold (for a studio with one senior checker, three to five cards). When the column is full, the rule is that drafters pull revisions and help clear checking rather than pushing more drawings into the queue.

This single constraint changes studio behaviour more than any software feature: it converts "everyone drafts until Thursday, then the checker drowns" into a steady flow where checking capacity — the studio's true throughput limit — sets the pace. The first two weeks feel slower. The submission week feels unrecognisably calmer.

The timeline view: seeing the collision before it happens

Kanban shows now; deadlines cluster in the future. This is why Taskboard pairs the board with a Gantt view over the same cards — flip to the timeline and the two submissions landing in the same week, the checker's leave overlapping the tender close, the revision window that doesn't exist — all become visible six weeks out, while they're still schedule problems rather than overtime problems.

The board replaces the meandering Monday meeting with a fifteen-minute walk-through, right to left — closest to done first, because finishing beats starting:

1. Issued/Ready to Issue: what leaves this week, and what's blocking the transmittal?
2. Internal Check: is the column at limit? who's clearing it?
3. Revisions: anything bounced twice? (Twice-bounced work gets a conversation, not a third silent loop.)
4. Drafting/Backlog: only now — what gets pulled next, by whom?

Everything else — the design debates, the client stories — happens outside these fifteen minutes, with the people who need them.

Why a file-based board suits a studio

Taskboard saves the whole board as a JSON file rather than a cloud workspace: keep it in the project folder under your naming conventions, back it up with everything else, and snapshot it at each reporting period for a dated record of what moved — a free audit trail. No logins means the whole team participates from day one, and none of your project names, clients, or problems sit on a third-party server. (For how this compares to the freemium SaaS route, see our guide to free Trello alternatives for architecture firms.) The honest fit: small, co-located teams or shared-drive setups with one board curator — which describes most studios that need this article.

Set up the seven columns with your live projects this afternoon; the board earns its keep by the second Monday:

Open Taskboard → — free, no logins, Kanban + Gantt, and the board stays in a file you control.