Research from the OECD shows that visual workflow systems improve coordination and productivity in remote environments.
Because they create a shared source of truth.
When everything lives in someone’s head or scattered across Slack threads, your team has no idea what’s happening. They don’t know what to work on. They don’t know what’s blocking other people.
A visual board fixes this.
Your VA in Manila can check the board at 9am her time.
See exactly what needs to be done. Start working.
Update the board when she’s done.
All without a single synchronous message.
How Kanban Boards Actually Work
Kanban is simpler than you think.
It’s columns representing stages of work. Tasks move left to right as they progress.
For a basic VA team, you might use:
Backlog – Tasks that need to be done eventually
Ready – Tasks that are fully defined and ready to start
In Progress – Tasks being actively worked on
Waiting – Tasks blocked by something
In Review – Tasks waiting for quality check or approval
Done – Completed work
Each task lives on a card. The card moves through the columns as work happens.
What WIP Limits Actually Mean
WIP stands for Work In Progress.
A WIP limit is the maximum number of tasks allowed in a column at one time.
If your “In Progress” column has a WIP limit of 3, only 3 tasks can sit there. When someone wants to start a fourth task, they can’t.
Here’s what happens without WIP limits:
Your VA starts Task A. Then Task B looks urgent, so she starts that too. Then Task C comes in from a client. Now she’s juggling three half-finished tasks.
Nothing gets completed. Everything takes longer. Context switching kills productivity.
WIP limits force finishing over starting.
When the column is full, you have two options. Finish something already started. Or help someone else finish their work.
Setting Up Your First Kanban Board for VAs
Start simple.
Pick a tool. Trello, Asana, Monday, ClickUp. Pick what your team will actually use.
Create your columns. Start with these five:
Ready → In Progress → Waiting → In Review → Done
Add your current tasks as cards. Put them in the appropriate column based on their actual status right now.
Assign each card to the person responsible. Add due dates if needed.
Choosing Starting WIP Limits That Actually Work
For the “In Progress” column, start with 1-2 active tasks per person.
If you have 3 VAs, set your WIP limit to 4 or 5. Why not exactly 3? Because sometimes collaboration makes sense. Two people working together on one complex task.
For “In Review,” set a lower limit. If you’re the only person reviewing work, maybe limit this column to 2-3 items. Otherwise it becomes a bottleneck.
These are starting points. Run with these limits for two weeks. See what happens. Adjust based on reality.
How to Actually Enforce WIP Limits
When a column hits its limit, that’s a signal.
The signal means one of three things:
Finish something. Can someone on the team wrap up a nearly-done task?
Help someone else. Can you swarm on a blocked task to get it moving?
Renegotiate priorities. If everything truly can’t wait, have an explicit conversation about what gets delayed.
What you don’t do is silently add more work.
Some tools let you set “hard” limits that physically prevent adding cards beyond the limit. Use that feature if your tool has it. If not, treat the limit as a rule your team agrees to respect.
Designing Columns for Async Handoffs
The “Waiting” column is critical for async teams.
Your VA finishes a task but needs your feedback to continue. Instead of DMing you (you’re asleep), she moves the card to Waiting. She adds a comment explaining what she needs. She tags you. Then she pulls the next Ready task and keeps working.
You wake up. See cards in Waiting. Provide feedback. Move them back to Ready or In Progress.
Work continues without anyone waiting around for responses.
For this to work, every card needs clear information:
Who owns it right now
What’s blocking it (if anything)
What specific input is needed to unblock it
When it needs to be done
This lets anyone on the team understand the status without asking questions.
Using Swimlanes to Manage Multiple Clients or Priorities
Swimlanes are horizontal rows on your board. They let you separate different types of work while using the same columns.
For VAs working with multiple clients, create swimlanes by client. Client A’s tasks flow through the columns in the top row. Client B’s tasks in the next row down.
Or organize by priority:
Urgent/Client-Facing in the top swimlane
Internal/Can Wait in the bottom swimlane
This helps VAs know what to pull next when they start their day. They look at the high-priority swimlane first. Pull from Ready. Start working.
Making Cards Actually Useful for Async Work
A card should be self-contained. Someone should be able to pick it up and understand what to do without asking questions.
Here’s what to include:
Clear title that describes the actual deliverable
Description with context and requirements
Checklist of specific steps if the task is complex
Due date if there’s a real deadline
Links to relevant documents, designs, or previous work
Comments for questions, updates, or handoffs
The more complete your cards, the less back-and-forth you need.
Common Mistakes Teams Make with WIP Limits
Setting limits too high. A WIP limit of 10 for a 3-person team isn’t a limit. It’s permission to multitask. Start lower than feels comfortable.
Only limiting “In Progress.” If In Progress has a limit but In Review doesn’t, work piles up waiting for approval. Limit every column except Done.
Treating limits as guidelines. If limits are optional, people will ignore them under pressure. Limits work when the team agrees they’re rules.
Never adjusting. Your first WIP numbers won’t be perfect. Review monthly. Lower limits if work is flowing too slowly. Raise them if artificial constraints are creating problems.
Tracking What Actually Matters
Visual boards give you data without extra reporting.
Look at cycle time. How long does a typical task take from Ready to Done? If it’s increasing, something’s wrong.
Maybe WIP limits are too high. Maybe tasks are poorly defined.
Look at where cards accumulate. Is Waiting always full? You have a feedback bottleneck. Is In Review overflowing? You need more review capacity or clearer quality standards.
The board shows problems visually. You don’t need complicated metrics.