📋 Lesson 3.1: Designing Your Workflow: Lists, Stages & WIP Limits

What a "Stage" Really Is

Back in Lesson 1.1 we said lists are usually stages, read left to right, and that direction means progress. Now we take that seriously. A stage isn't just a bucket to dump cards in — it's a meaningfully different state that a piece of work passes through on its way to done. The test for a good list is simple: does moving a card into this list represent real, observable progress? If yes, it earns a column. If a list is just a category ("Emails," "Phone calls") that a card never graduates out of, that's a filter or a label, not a stage.

Consider a freelance designer's work. Each project genuinely passes through distinct states: it's been requested, it's actively being worked, it's out with the client for feedback, and it's approved. Those are stages. Reading them left to right tells you exactly where every project stands — without opening a single card.

Notice two things. First, work can flow backward — a "Client Review" card that needs changes goes back to "In Progress." That's normal and honest; a board should show reality, not a fantasy where everything only ever moves right. Second, every arrow is a real transition someone makes on purpose. That's what separates a designed workflow from a pile of columns.

Workflow Patterns That Work

You don't have to invent your workflow from nothing. A handful of patterns cover the vast majority of real work. Start from the closest one and adjust.

Pattern 1 — Queue → Active → Done

The classic three, and still the right answer more often than people expect. A queue of work waiting to start, an active stage where things are being worked, and done. If your work is mostly "there's a list of things, I pick one up and finish it," don't over-engineer — this is it. To Do / Doing / Done is this pattern.

Pattern 2 — Intake / Triage

When requests arrive from many directions and need sorting before anyone works them, add an intake stage up front: Inbox → Triage → To Do → Doing → Done. New cards land in Inbox raw; in Triage you decide priority, add labels, and either promote them to To Do or archive them. This keeps the "real" queue clean and stops half-formed requests from clogging your active work. (Trello's own Inbox, which we cover in Lesson 8.1, is a purpose-built capture surface for exactly this intake step.)

Pattern 3 — The Review Gate

Any work that someone else checks before it's done needs a Review stage between "In Progress" and "Done": To Do → In Progress → Review → Done. This is the backbone of team boards (Lesson 3.3), but solo work benefits too — a "Review" list is where you let a draft cool off before you proof it. The gate makes handoffs and quality checks visible instead of invisible.

Here's a general-purpose board — a small marketing team's content workflow — built from the intake + review patterns combined:

See the 2 / 2 next to "Doing"? That's a WIP limit — the list is at capacity, so nothing new comes in until something moves to Review. We build that next.

The Waiting / Blocked Lane

Here's the stage almost everyone forgets, and the one that quietly wrecks the most workflows. What happens when a card can't move forward because it's waiting on someone else — a client reply, an approval, a delivery, a teammate's part? If it stays in "Doing," it lies to you: your active column looks full, but nothing is actually happening. If you drag it back to "To Do," you lose the context that it was already started.

The fix is a dedicated Waiting / Blocked list. When a card gets stuck, it moves there with a note about what it's waiting on. Now the board tells the truth: this many cards are truly in motion, and these are parked, waiting on the world.

A red label plus a "waiting: …" note makes blocked cards jump out. Some teams add a bright Blocked label instead of a whole list — either works; the point is that stuck work is impossible to miss.

WIP Limits: Finish More by Doing Less

This is the heart of the lesson, and the idea that turns a nice-looking board into a genuinely faster way to work. WIP stands for Work In Progress. A WIP limit is a cap on how many cards are allowed in a given list at once — most importantly your "Doing" list.

Why limiting work speeds it up

It feels backward, so let's make it concrete. Say you start ten tasks. All ten are "in progress," none is finished. You context-switch between them, each switch costs focus, and value is delivered only when something is actually done — which, at this rate, is never. Now cap "Doing" at three. You're forced to finish one of the three before pulling in a fourth. Things start crossing into Done. The counter-intuitive truth of Kanban: your throughput goes up when your work-in-progress goes down.

How to set a WIP limit

There's no single magic number — it depends on the work and, for teams, the number of people. Good starting points:

• Solo: cap "Doing" at 2–3. You genuinely can't focus on more.
• Team: a rough rule is one to two cards per person in the active stage. A four-person team might cap "In Progress" at 5–6.
• Watch and adjust: if the limit is never reached, it's too loose; if work is constantly bottlenecked before the limit, the bottleneck is a later stage (like Review), not Doing.

Enforcing the limit in Trello

Trello doesn't hard-block a list at a number by default, but you have three levels of enforcement, from gentle to automatic:

1. By eye. Write the limit right in the list name — "Doing (max 3)" — and honor it. The card count next to the title (which Trello can show) makes overflow obvious. Free, and surprisingly effective.
2. The List Limits Power-Up. A free Power-Up (Power-Ups are unlimited on Free, see Lesson 6.1) that highlights a list in yellow/red when it exceeds the number you set. You can still drop a card over, but the board shouts at you — which is usually enough.
3. Butler automation. For real teeth, a Butler rule (Lesson 5.1) can watch the list and react when it's over capacity — post a warning comment, add a "⚠️ Over WIP" label, or notify you. Here's the shape of that rule:

You'll write rules exactly like this by hand in Lesson 5.1 — no code, just plain English. For now, just know the enforcement exists when eyeballing isn't enough.

Anti-Patterns & Redesigning Safely

Designing a workflow is as much about what you leave out as what you add. A few traps to avoid:

❌ Too many lists

If your board scrolls sideways forever, you've probably turned attributes into stages. "High Priority," "Low Priority," "Bug," "Feature" aren't stages — they're labels (Lesson 2.3). A card should pass through stages, not live permanently in one. Rule of thumb: most boards are healthiest with 4–6 lists.

❌ The "Someday" swamp

A "Someday / Maybe" list starts innocent and becomes a graveyard of forty cards no one will ever read. Ideas are fine — but give them a real home (a separate "Ideas" board, or a backlog you actually triage) and keep them out of your working lanes. If a card hasn't moved in three months, it's not someday, it's no.

❌ A Done list that never empties

Done is satisfying, but 300 done cards slow the board and bury the recent wins. Periodically archive old Done cards (a Butler scheduled command can do this weekly — Lesson 5.3). Archiving keeps them searchable without cluttering the view.

Redesigning without losing cards

Good news: reshaping a board is completely safe. Cards, lists, and their contents are never harmed by rearranging. To redesign:

1. Rename lists in place where the meaning is close (double-click the title).
2. Add new lists (like Review or Blocked) and drag existing cards into them.
3. Reorder lists by dragging their headers so they read left-to-right as progress.
4. Archive (don't delete) any list you're retiring — its cards are preserved and recoverable if you change your mind.

Nothing is destructive except deleting, and even archived items can be restored. Experiment freely.

🎯 Project: Redesign Your Workflow

Time to turn a generic board into one that models your real work — with a Blocked lane and a WIP limit that you'll actually feel working. Use the "My Week" board from Module 1, or any real board you've built. This should take about 20 minutes and leave you with a board that tells the truth at a glance.

Board: Home Renovation

Backlog        | To Do          | Doing (max 2)   | Blocked / Waiting   | Done
---------------|----------------|-----------------|---------------------|-------------
Repaint hall   | Order tiles    | Fix the fence   | Permit (city, wk 3) | Pick paint
New light fix. | Book plumber   |                 | Countertop (vendor) | Measure kitchen
Replace deck   |                |                 |                     | Choose flooring

Best Practices for Workflow Design

✅ Do's

• Make every list a real stage. If moving a card in isn't "progress," it's a label, not a list.
• Give stuck work a home. A Blocked/Waiting lane keeps your active column honest.
• Cap your active list. A WIP limit is the single highest-leverage habit in Kanban — set one and honor it.
• Let friction guide additions. Add a Review gate or a new stage when you feel the pain, not before.

❌ Don'ts

• Don't turn attributes into lists. Priority and category are labels; keep lists to 4–6 real stages.
• Don't let a "Someday" list become a swamp. Give ideas a triaged home, not a graveyard.
• Don't let Done grow forever. Archive old cards (Butler can do it weekly) to keep the board fast.
• Don't delete to reorganize. Rename, reorder, and archive — nothing but delete is destructive.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've graduated from listing tasks to designing a workflow — the skill that separates people who use Trello from people who master it. Your board now models how work really moves, shows what's stuck, and caps what's in flight so things actually finish. That's the Kanban method working for you, not just decorating your screen.

❓ Common Questions at This Stage

🔭 Looking Ahead

Now that you can design a workflow, we'll point it at your whole life. Next lesson builds a Personal Kanban and shows how Trello maps onto the GTD method — capture, clarify, organize, review — so nothing falls through the cracks and your weekly review becomes a genuine reset.

✅ Before the Next Lesson

• Keep your redesigned board handy — you'll build on these ideas
• Notice, over the next few days, whether your WIP limit changes how it feels to work
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Trello Guide — boards, lists, and workflows
• Kanban (workflow) — WIP limits and flow
• Work in process — why limiting it helps