Kanban Project Management for A&E Teams: A Practical Guide

Kanban came from manufacturing, was adopted by software, and most A&E firms have ignored it as a result. They should not. Adapted to design phases, review cycles, and the realities of A&E work, Kanban produces some of the cleanest team management you can build.

Why Kanban fits A&E better than you would think

The A&E workflow is fundamentally a series of work items that move through stages: ideation, draft, internal review, client review, revision, issue. That is exactly what Kanban is built for.

Where many firms get stuck is treating Kanban as a software ritual. It is not. It is a visual layer over the work your firm already does, with three rules that make a difference.

1. Make the work visible.
2. Limit work in progress at each stage.
3. Manage flow, not assignments.

Designing the right columns

Generic Kanban templates do not work for A&E. The columns must reflect how design work actually moves. The most useful set for most firms is six columns.

• Backlog. Items identified but not yet picked up.
• In Progress. Currently being produced.
• Internal Review. Done by the producer, awaiting senior or peer review.
• Client Review. Sent out, awaiting client comments.
• Revisions. Comments received, work in progress on revisions.
• Done. Issued and closed.

This six column model surfaces the bottleneck that most A&E firms ignore: the wait time between Client Review send and the comments coming back. Tracking it visually changes how PMs follow up.

Work in progress limits, the part that matters

Every column has a maximum number of items allowed. When the column is full, no new item enters until something leaves.

A typical setup for a five person team might be: In Progress 5, Internal Review 3, Client Review unbounded (you do not control this), Revisions 4. The exact numbers are less important than having limits at all.

The value is forcing the team to finish before starting. Most A&E teams have 12 things "in progress" and three things actually moving. Limits fix that.

What goes on a card

Cards should be project deliverables, not tasks. The unit is something the team can fully complete and ship: a structural plan set for SD, a wall section package, a permit revision, an RFI response.

Each card carries a small set of fields.

• Title (deliverable name)
• Project
• Phase
• Owner
• Due date
• Block reason if blocked

That is it. Resist the urge to add 15 fields. The board's value is being readable in one glance.

The daily standup that keeps it alive

15 minutes, in front of the board (physical or digital). Walk the board right to left, focusing on what is closest to done.

• What is in Done since yesterday.
• What is in Revisions and what is the close out plan.
• What is in Client Review and how long has it been there.
• What is blocked, who can unblock it.

Notice what you do not do: ask everyone what they are working on. That is a status meeting. The board already shows it.

Where teams typically fail

• Cards that are too granular. If the team adds tasks instead of deliverables, the board becomes noise.
• No WIP limits. Without limits, Kanban is just a fancy to do list.
• Skipping the daily standup. The board only stays accurate if it is touched daily.
• Treating Client Review as if you control it. You do not. Track wait time, do not pretend it is your column.
• Mixing too many projects on one board. One board per active project, with a portfolio view above for the partner.

Tooling: the actual answer

For a team of 5, a physical board on a wall works well. For 5 to 25, a digital tool like Trello, Linear, or a Kanban view inside your firm management platform works better. For larger teams or distributed firms, an integrated tool that ties cards back to project budgets and time entries pays off quickly.

The principle is simple: the tool must be checked daily by the people doing the work. A perfect tool that nobody opens is worse than a whiteboard that everyone walks past.

Combining Kanban with phase based project management

Kanban does not replace your phase based project plan. It complements it. The phase plan tells you what the project is delivering and when. The Kanban board tells you what is moving today.

The two layers together are far stronger than either alone. The plan keeps the project on schedule at the macro level. The board keeps the team unblocked at the daily level.

The first 30 days

Pick one project and one team. Build the six column board. Add WIP limits on day one, even if they feel arbitrary. Do daily 15 minute standups for two weeks. After two weeks, adjust the column structure if the work flow demanded different stages.

By day 30 you will have a board the team trusts and a workflow that runs noticeably smoother than it did before.

Roll out to a second project after that. Then a third. Within a quarter, Kanban becomes part of how the firm runs, not a special initiative.