Generic Kanban boards — To Do, In Progress, Done — work fine for personal task management. They break down almost immediately when you apply them to agency client work: multiple projects running simultaneously, different workflow stages per project type, dependencies on client approvals, deliverables that need review before they can move forward.
The problem isn't Kanban. It's Kanban boards that weren't designed for how agencies actually work.
Why Agencies Struggle with Generic Project Boards
The mismatch between standard project boards and agency reality shows up in a few consistent ways:
No client approval stage: Agency work almost always involves a review-and-revise loop. A board without a "Client Review" column treats that waiting time as invisible — work moves to Done when it's actually just sitting in a client inbox, blocking delivery and distorting the team's view of what's actually complete.
All projects share the same board: A single board for everything means a designer can't see their tasks across five clients at once, and a project manager can't get an overview of all active work without switching between views.
No connection between board status and billing: When a deliverable moves to Done, something billable usually happened. A Kanban board that doesn't connect to invoicing means milestone billing requires someone to manually match board status to invoice triggers — a process that routinely creates billing delays and missed milestones.
No WIP awareness across projects: A column limit on a single project board doesn't account for the same person being in the "In Progress" column on four different project boards simultaneously. Real WIP management for agencies requires a cross-project view.
No stage for what comes after delivery: Agency projects don't end when deliverables are sent. There's handover documentation, retainer transitions, feedback capture, and follow-up work. Boards that only model delivery miss the tail of every project.
Kanban vs Scrum for Agencies: Which Works Better
Both Kanban and Scrum are used in agencies. They suit different types of work:
Scrum works well for: Long-running product or software development engagements with stable teams, iterative scope, and regular sprint reviews. If your agency runs dedicated development teams for clients on 6–12 month engagements, Scrum's sprint structure creates useful predictability and rhythm.
Kanban works better for: Most agency work — campaigns, creative projects, content, strategy, and anything with variable scope and irregular delivery cadence. Kanban doesn't require fixed sprint cycles or formal ceremonies, which makes it more adaptable to the constant context-switching and shifting client priorities that define agency life.
The practical difference: In Scrum, you commit to a fixed scope for two weeks and protect the sprint. In Kanban, you manage flow continuously — new work enters the top of the queue, and the team pulls work as capacity opens up. Agencies that serve many clients simultaneously almost always find Kanban more practical, because client priorities don't respect sprint boundaries.
Many agencies use a hybrid: Kanban boards for day-to-day project flow, with Scrum-style retrospectives at project milestones to assess what's working.
How to Set Up a Kanban Board for Agency Work
The column structure is everything. Here's a practical template for most agency project types:
Backlog: Everything that's been scoped and agreed but not yet started. Items here are fully briefed — not ideas or requests — so the team can pull them without needing additional context.
In Scoping: Work that's been requested but needs definition before it can start. Brief being developed, questions being asked, dependencies being confirmed. This stage prevents "In Progress" from becoming a black hole of half-briefed work.
In Progress: Active work. Apply a WIP limit here — the maximum number of cards that can be in this column per person or per team. WIP limits are the mechanism that forces prioritisation and prevents the illusion of productivity that comes from starting many things and finishing few.
In Review (Internal): Finished from the team's perspective, but needs internal QA or approval before going to the client. This stage protects clients from seeing work that isn't ready and protects the team from client feedback on work that should have been caught internally.
Client Review: Sent to the client and awaiting feedback. This column makes waiting time visible — you can see exactly how many items are blocked on external input, which is useful for spotting slow-moving clients before they become delivery risks.
Revisions: Client feedback received and work being updated. This is a distinct stage from "In Progress" because revisions have different time pressure and context.
Done — Pending Invoice: Work is complete and accepted. The invoice hasn't been sent yet. This column is the critical link between delivery and billing — it's the trigger for the invoicing process, and its existence prevents the common agency problem of completing work and forgetting to bill for it.
Invoiced / Closed: Invoice sent. Project phase or milestone financially closed.
Adapt this structure to your project types. A retainer workflow might collapse some stages; a complex brand project might add stages for concept approval or legal review. The principle is that every card should represent real work, every column should represent a real state, and every transition should mean something happened.
Kanban Metrics Agencies Should Track
The power of Kanban is that it generates useful operational data by default, if you know what to measure:
Cycle time: How long does a card take to move from "In Progress" to "Done"? Average cycle time by task type tells you your realistic delivery pace — which should directly inform your project scoping and client commitments. If your average design task takes 4 days but you're quoting 2, you have a pricing and scheduling problem that cycle time data surfaces clearly.
Lead time: The total time from when a task enters the Backlog to when it's Done, including wait time. Lead time is what clients experience — cycle time is what your team experiences. A large gap between the two means tasks are sitting in queues before the team gets to them.
WIP trends: How many cards are typically in each column at any given time? Consistently full Review columns suggest a QA bottleneck. Consistently full Client Review columns suggest clients are slow to provide feedback — which is either a client management issue or a sign that you're sending work for review before it's actually ready.
Throughput: How many tasks does the team complete per week? Throughput trends tell you whether your delivery capacity is increasing, stable, or declining — independent of how busy everyone looks.
Blocked time: Cards that can't move because of a dependency, missing information, or external blocker. Tracking how long cards spend blocked, and why, identifies systemic issues that repeated stand-up meetings fail to surface.
Kanban in Monton: Beyond the Basic Board
Monton's project boards are built on Kanban principles but connected to the data that makes them operationally useful for agencies — not just visually pleasing.
Cross-project visibility: See tasks across all active projects in a single board filtered by team member, status, or client. A project manager can review all in-flight deliverables for a specific designer across six clients in one view — not by opening six different boards.
Time tracking on cards: Log time directly from a task card. Every hour logged against a card updates the project's cost and margin automatically. The connection between work in progress and financial outcome is live, not reconstructed at month end.
Invoicing trigger from board status: When a card moves to "Done — Pending Invoice," it can trigger a billing workflow in Monton. Milestone billing becomes a board operation rather than a separate process someone has to remember to run.
Custom columns per project: Every project type has a different workflow. Monton lets you configure column structures per project rather than forcing all work into a single schema — so a brand project, a performance campaign, and a website build each have the stages that reflect how they actually move.
Capacity awareness in the board view: WIP limits in Monton connect to actual team capacity, not arbitrary card counts. The system tells you not just that a column is full, but whether the people in that column have the bandwidth for more.
Kanban boards for agencies should be operational tools that reflect the real state of delivery — not visual summaries you update for the client report. The right setup makes the board the place where work actually happens, which means the data in it is automatically useful for everything else: invoicing, capacity planning, and profitability analysis.