Kanban is one of the simplest ways to make studio work visible, but most guides to it are written for software teams shipping features, not architects producing drawings. Set up naively, a board becomes a graveyard of stale cards nobody moves. Set up well, Kanban boards for architecture studios turn the invisible mess of who-is-waiting-on-what into something the whole team can see at a glance. This is a practical setup, built around how a studio actually works.
The core idea is simple. A board has columns that represent stages of work, and cards that move across them as work progresses. The art is in choosing columns that match architectural work and cards that carry the right information, so the board reflects reality instead of becoming a chore to maintain.
Why Kanban fits architecture work
Studio work is a constant flow of discrete pieces: a sheet to draft, a markup to incorporate, an RFI to answer, a submittal to review. Each one has a state, from not-started to done, and each one has an owner. That is exactly what a Kanban board models. The visibility it creates is the point: when the whole team can see what is in progress, what is blocked, and what is next, coordination stops depending on memory and hallway conversations.
Choose columns that match how work flows
The most common mistake is copying a generic To Do, Doing, Done board and stopping there. That is better than nothing, but it does not reflect a studio. A more useful set of columns captures the real states a piece of work passes through, including the ones where it waits on someone else.
- Backlog: everything identified but not yet started
- In progress: work someone is actively doing right now
- Waiting on consultant: work blocked on a structural, MEP, or civil input
- In review: internal check or QA before it goes out
- Waiting on client: sent for approval and awaiting a decision
- Done: approved and complete for this phase
The two waiting columns are what make a board honest. In architecture, an enormous amount of time is spent blocked on someone else, and if that state is invisible, the board lies about where things stand. Making waiting a visible column is often the single most valuable change a studio can make.
One board per project, or per phase
For most studios, a board per project works well, with cards grouped or filtered by phase. If a project is large, a board per phase keeps things focused, since construction administration looks so different from design development that mixing them on one board adds noise. The right answer is whatever keeps a single board scannable in a few seconds. If you have to scroll forever to understand a project, split it.
Make cards carry the right information
A card is only useful if it tells you what you need without opening it. At minimum a card should say what the work is, who owns it, and what it is attached to. For a studio that means the drawing, sheet, or RFI it concerns, with the relevant PDF attached so the reference is one tap away rather than buried in a shared drive.
A good card answers three questions without being opened: what is this, who owns it, and what is it waiting on.
Add a team queue on top of the board
A board shows the state of the work, but it does not by itself tell each person what to do next. That is where a team queue helps. Ordering the studio's work so everyone can see the next thing to pick up removes the daily question of what should I work on, and it lets a studio manager set priorities without hovering. The board answers where things stand; the queue answers what happens next.
Keep the board honest with a short rhythm
A board only works if it reflects reality, and reality changes daily. The way to keep it honest is a short, regular rhythm rather than a big weekly clean-up. A few minutes at the start of the day, or a fifteen-minute stand-up around the board, is enough for the team to move cards, flag what is blocked, and confirm priorities. The moment a board drifts from reality, people stop trusting it, and once they stop trusting it, they stop using it.
Avoid the common traps
A few failure modes show up again and again. Cards that are too big never seem to move, so break work down to something that can progress in a day or two. Boards with too many columns become fussy, so keep it to the states that genuinely matter. And a board that only one person maintains is not a shared board at all, it is that person's private list, so make updating it a team habit from the start.
Setting it up in Spreadbox
Spreadbox gives you Kanban task boards built for this kind of setup, with a team queue layered on top so the studio always knows the next thing to pick up. You can attach drawings and PDFs directly to cards so the reference sits with the work, track project status against your phases, and keep coordination in team chat channels instead of scattered email. Per-task time tracking lets hours accrue as a natural byproduct of moving a card, and native iOS and Android apps mean you can update the board from a site visit before the detail is lost. Spreadie, the built-in AI assistant, can even turn a rough note into a set of cards, so building out a phase on the board takes seconds rather than an afternoon.