Kanban for Web Agencies: Streamlining Your Visual Production Workflow

Why Web Agencies Need a Better Workflow Model

Web agencies operate in a uniquely chaotic environment. On any given Monday, your team might be wireframing a new e-commerce site, debugging a client’s WordPress plugin, pushing a Prestashop theme update to staging, and responding to an urgent SEO audit request—all before lunch.

Traditional project management methods struggle here. Waterfall is too rigid. Pure Scrum assumes a single product backlog and fixed sprints, which rarely map to the reality of agency life where priorities shift with every client phone call.

That’s where Kanban comes in.

Originally developed by Toyota in the 1940s to optimize manufacturing, Kanban has become one of the most effective workflow management systems for creative and technical teams. Its core promise is simple: visualize your work, limit what’s in progress, and optimize flow.

For web agencies specifically, Kanban offers something invaluable—a way to see exactly where every project stands across design, development, QA, and deployment, without forcing artificial time-boxes on inherently unpredictable creative work.

Understanding Kanban Fundamentals

Before we dive into agency-specific implementation, let’s ground ourselves in Kanban’s core principles.

The Four Foundational Principles

• Start with what you do now. Kanban doesn’t require a radical restructuring. You map your existing workflow onto a board and improve incrementally.
• Agree to pursue incremental, evolutionary change. No big-bang transformations. Small adjustments, measured results.
• Respect current roles and responsibilities. Kanban doesn’t prescribe roles like Scrum Master or Product Owner.
• Encourage leadership at all levels. Every team member can identify and suggest improvements.

The Six Core Practices

1. Visualize the workflow
2. Limit work in progress (WIP)
3. Manage flow
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally

The beauty of Kanban is that it meets you where you are. At Lueur Externe, we’ve seen agencies try to adopt Scrum overnight and burn out within two sprints. Kanban’s evolutionary approach makes adoption far more sustainable—especially for teams already stretched thin across multiple client accounts.

Designing a Kanban Board for Web Production

The heart of Kanban is the board. Get the board right, and everything else follows. Get it wrong, and the system becomes just another ignored tool.

Mapping Your Real Workflow

A Kanban board should reflect how work actually flows through your agency—not how you wish it did. Here’s a typical board structure for a mid-sized web agency:

Column	Purpose	WIP Limit	Typical Owner
Inbox / Requests	Raw client requests, internal ideas	None	Project Manager
Brief & Spec	Requirements gathering, scope definition	3	PM / Account Manager
Design	UI/UX wireframes, mockups, visual design	4	Design Team
Design Review	Internal and client feedback on visuals	2	PM + Client
Development	Front-end, back-end, CMS integration	5	Dev Team
Code Review / QA	Peer review, cross-browser testing, accessibility checks	3	Senior Dev / QA
Client Approval	Staging review, sign-off	2	Client + PM
Deploy & Done	Push to production, post-launch verification	None	DevOps / Senior Dev

Notice the WIP limits on each column. These are not suggestions—they are hard constraints that prevent your team from drowning in half-finished work.

Why Separate Design and Development Queues Matter

One mistake agencies make is lumping design and development into a single “In Progress” column. This hides the most common bottleneck in web production: the handoff between design and development.

When designers finish mockups faster than developers can build them, a queue of approved designs piles up. Without visibility into this queue, the PM keeps accepting new design work, making the development backlog worse.

By splitting design and development into separate columns—each with its own WIP limit—you make this bottleneck visible and manageable.

Implementing WIP Limits That Actually Work

Work-in-progress limits are the single most transformative aspect of Kanban, and also the most resisted.

The Math Behind WIP Limits

Little’s Law, a foundational principle of queuing theory, states:

Average Cycle Time = Average WIP / Average Throughput

In plain language: the more things you work on simultaneously, the longer each one takes to finish.

Consider this scenario for a 4-person development team:

• Without WIP limits: 12 tasks in progress, throughput of 6 tasks/week → average cycle time = 2 weeks
• With WIP limit of 6: 6 tasks in progress, throughput remains 6 tasks/week → average cycle time = 1 week

Same team, same throughput—but half the delivery time simply by limiting concurrent work. Clients don’t care how busy you are; they care when their project ships. WIP limits directly accelerate delivery.

Setting Your Initial WIP Limits

A practical starting formula:

WIP Limit per column = (Number of people working in that stage × 1.5), rounded up

For a design team of 3: WIP limit = 5 (3 × 1.5, rounded up).

The multiplier of 1.5 accounts for blocked items (waiting for client feedback, third-party assets, etc.) while still keeping the team focused. Start here, then adjust based on data after 2-4 weeks.

What Happens When a Column Hits Its WIP Limit

This is where discipline matters. When the Development column is at capacity:

• Don’t start a new development task.
• Do help unblock existing tasks (pair programming, clearing QA items, assisting with code review).
• Do pull work backward if possible—help the column downstream (QA, client approval) clear its queue.

This “stop starting, start finishing” mentality is counterintuitive but extraordinarily effective. Teams at Lueur Externe have observed that enforcing WIP limits consistently for just 30 days typically results in a 30-40% reduction in average project delivery time.

Kanban Metrics Every Web Agency Should Track

You can’t improve what you don’t measure. Kanban provides elegant, low-overhead metrics that give you genuine insight into your production health.

Cycle Time

Cycle time measures how long a task takes from the moment work starts to the moment it’s done. For web agencies, tracking cycle time by task type reveals powerful patterns:

• Landing page design: average 3.2 days
• WordPress custom plugin: average 8.7 days
• Prestashop product import module: average 5.1 days
• SEO technical audit: average 4.4 days

These averages allow you to make realistic commitments to clients. Instead of guessing, you can say: “Based on our historical data, a project like yours typically takes 6-9 business days from kickoff to staging.”

Throughput

Throughput is the number of tasks completed per unit of time (usually per week). Tracking throughput over months reveals your team’s true capacity—not the aspirational capacity in your resource plan, but the actual, proven output.

Cumulative Flow Diagram (CFD)

The CFD is Kanban’s most powerful diagnostic tool. It plots the number of tasks in each workflow stage over time. A healthy CFD shows roughly parallel bands that flow steadily rightward. Warning signs include:

• Widening bands: work is accumulating faster than it’s being completed (growing WIP)
• Flat lines at the top: nothing new is entering the system (demand problem)
• Flat lines at the bottom: nothing is finishing (delivery problem)

Most Kanban tools (Jira, Kanbanize, Linear) generate CFDs automatically. If you’re using Trello, the Butler automation combined with a simple Google Sheet can approximate one.

Real-World Kanban Configurations for Common Agency Scenarios

Let’s look at how Kanban boards can be tailored for different types of web agency work.

Scenario 1: E-Commerce Build (Prestashop / WooCommerce)

For a full e-commerce build, the standard board gets extended with commerce-specific columns:

• Inbox → Spec & Catalog Planning → Theme Design → Front-End Integration → Back-End / Module Development → Product Data Import & Config → Payment & Shipping Testing → Client UAT → Go-Live

The bottleneck here is almost always Product Data Import & Config. Clients underestimate the effort of preparing clean product data. Giving this stage its own column with a WIP limit of 2 forces early conversations about data readiness.

Scenario 2: Ongoing Maintenance & Support

For retainer-based maintenance work, a simpler board works best:

• Triage → Scheduled → In Progress → Testing → Done

Add swimlanes for urgency (Critical, Normal, Low) so the team always knows what to pull next. A WIP limit of 2-3 on “In Progress” per developer ensures urgent bugs don’t languish because someone is deep in a low-priority feature request.

Scenario 3: SEO & Content Production

SEO workflows have a distinct rhythm. A content-focused Kanban board might look like:

• Topic Research → Keyword Mapping → Writing → Editorial Review → SEO Optimization → Client Approval → Published

The key insight here is separating Writing from SEO Optimization. When writers try to optimize while drafting, quality suffers in both dimensions. Keeping them as separate stages—each with a WIP limit—lets specialists do what they do best.

Common Kanban Mistakes in Agency Settings

After years of helping agencies optimize their production workflows, we’ve identified the most frequent pitfalls.

Mistake 1: Treating Kanban as Just a Board

Pinning sticky notes on a wall (or dragging cards in Trello) is not Kanban. Without WIP limits, explicit policies, and regular flow reviews, you just have a fancy to-do list. The board is the most visible part of Kanban, but the discipline behind it is what delivers results.

Mistake 2: No Cadence of Review

Kanban relies on regular feedback loops. At minimum, implement:

• Daily standup (15 min): walk the board right-to-left, focusing on blocked items
• Weekly replenishment (30 min): decide what enters the board from the backlog
• Bi-weekly retrospective (45 min): analyze metrics, adjust WIP limits, discuss process improvements

Skipping these meetings turns Kanban into a passive information radiator instead of an active management system.

Mistake 3: Ignoring Blocked Items

A card sitting in “Client Approval” for 11 days isn’t a Kanban problem—it’s a communication problem. But Kanban makes it visible. The solution: add a blocked indicator (red flag, tag, or dedicated sub-column) and review all blocked items in every standup. If a client consistently delays approvals, the data gives you leverage to renegotiate SLAs or adjust your process (e.g., scheduled approval windows).

Mistake 4: One Board to Rule Them All

Agencies often start with a single board for everything. This quickly becomes unmanageable. A better approach:

• Portfolio board: high-level view of all active projects (each card = one project)
• Team boards: detailed task-level boards for design, development, and content teams
• Client-facing board: simplified view shared with clients for transparency

This hierarchy gives leadership strategic visibility without cluttering the team’s operational board.

Tool Comparison: Choosing the Right Kanban Platform

The tool matters less than the practice, but the right platform reduces friction. Here’s a quick comparison for agency use:

Tool	Best For	WIP Limits	CFD / Analytics	Price (per user/month)
Trello	Small teams, simplicity	Via Power-Up	Limited	Free–$10
Jira	Large teams, advanced reporting	Native	Excellent	$7.75–$15.25
Linear	Dev-heavy teams	Native	Good	Free–$8
Notion	All-in-one workspace	Manual	Limited	Free–$10
Kanbanize	Kanban purists, scaled Kanban	Native	Excellent	~$15+
Teamwork	Client-facing agencies	Native	Good	$5.99–$19.99

For most web agencies with 5-20 people, Jira or Linear offers the best balance of Kanban features and integration with development tools (Git, CI/CD). If your team lives in Slack and needs something lightweight, Trello with the Corrello Power-Up for analytics is a solid choice.

Scaling Kanban as Your Agency Grows

Kanban scales naturally—which is one of its greatest advantages over framework-heavy approaches.

Service Level Expectations (SLEs)

As you accumulate cycle time data, you can define SLEs: “85% of standard WordPress development tasks are completed within 7 business days.” SLEs replace vague promises with data-backed commitments. They build client trust and set internal performance benchmarks.

Classes of Service

Not all work is equal. Define classes of service to manage priority without constant firefighting:

• Expedite: Production site is down. Drop everything. (WIP limit: 1 across entire board)
• Fixed date: Hard deadline (product launch, campaign go-live). Scheduled backward from the date.
• Standard: Normal client work. Pulled in FIFO order.
• Intangible: Internal improvements, tech debt, tooling. Allocate 10-20% of capacity.

This framework prevents the common agency trap where “everything is urgent” and nothing gets finished.

Connecting Kanban to Business Outcomes

Ultimately, Kanban is a means to an end. The metrics that matter to agency leadership are:

• On-time delivery rate: percentage of projects delivered by the agreed date
• Client satisfaction / NPS: correlated with predictability and communication
• Revenue per team member: efficiency gains from reduced WIP should translate to higher output per person
• Team morale / turnover: overloaded teams burn out; Kanban’s WIP limits are a structural defense against overwork

Agencies that track these alongside Kanban flow metrics can draw direct lines between process improvements and business results.

Conclusion: Start Simple, Improve Continuously

Kanban isn’t a silver bullet, but it’s the closest thing web agencies have to a universal workflow improvement system. It doesn’t ask you to abandon your current processes overnight. It asks you to see your work clearly, stop overloading your team, and make small improvements every week.

The agencies that thrive in 2025 won’t be the ones with the fanciest tools—they’ll be the ones with the most disciplined, transparent, and adaptive workflows. Kanban gives you the framework to build exactly that.

At Lueur Externe, we’ve been refining web production workflows since 2003—across Prestashop builds, WordPress projects, complex AWS architectures, and SEO campaigns. If you’re looking for a partner who understands both the technical and operational sides of web production, get in touch with our team. We’d love to help you build a workflow that actually works.