Building a Personal Kanban Board That Pulls From All Your PM Tools

A personal Kanban is simple: three columns - To Do, Doing, Done. You move tasks through them.

When Done gets full, you know you're productive. When Doing has too many tasks, you know you're overloaded.

The power of Kanban is visual simplicity. Unlike complex timeline or dependency views, a Kanban just asks: what am I working on right now?

The challenge: your tasks live in five different PM tools. You can't put them all in one Kanban without abandoning your team systems.

The solution: build a personal Kanban that mirrors and aggregates your actual work across all tools.

Why Personal Kanban Is Different From Team Boards

Your team uses Asana or Jira with dozens of tasks in progress simultaneously. The team needs to see dependencies, priorities, and scope.

Your personal Kanban is just for you. You need to see the three to five things you're actively working on this week, and move them through to done. Nothing else.

This distinction matters. A team Kanban board represents the entire project.

A personal Kanban represents your focus. They're different purposes.

The Three Columns

To Do - Everything assigned to you that you haven't started. This includes tasks from Asana, Linear, Jira, email, and any other source. If you've committed to it, it goes here.

Doing - Everything you're actively working on. For most people, this should never have more than 3-5 items. When Doing is full, you can't take on new work until you move something to Done.

Done - Everything you completed. Don't delete these. They stay visible for the week so you can feel the satisfaction of completed work.

That's it. Three columns. Visual. Simple.

Where Does It Live?

Some options:

Physical board - Sticky notes on your desk or office wall. High friction to update, but very visible. Works well if you work in an office.

Notion - You can create a simple Kanban view in Notion with custom properties. Not the smoothest Kanban experience, but integrates with your other Notion work.

Trello - Designed for Kanban. Easy to use. The challenge is keeping it in sync with your other tools (it doesn't auto-sync).

Miro or Mural - Visual Kanban that's more flexible than Trello. Still requires manual maintenance.

Actual Kanban app - Apps like Kanban Flow or Taiga are specifically built for personal Kanban. They're simple and do nothing except Kanban well.

Custom dashboard - Some teams build simple web-based boards that auto-sync with their PM tools. This is the dream but requires some technical setup.

The ideal is something that automatically syncs with your team tools so you don't have to manually add and remove tasks. But even manual sync is powerful if you're consistent about updating weekly.

Getting Tasks Into Your Kanban

The first time you set this up, scan all your assigned tasks across all tools and create them in your Kanban.

Then, establish a rhythm:

Weekly - During your weekly review, pull any new assigned tasks from your team tools into your Kanban's To Do column. This happens once per week.

Daily - As you work, you move tasks from To Do to Doing. When you finish something, you move it to Done. This is the core daily practice.

This manual process seems tedious until you do your first week. Then you notice: the visual feedback of moving tasks to Done is motivating.

The constraint that Doing can only have three items forces prioritization. The accumulation of Done items by Friday gives you tangible evidence of progress.

The Weekly Workflow

Monday morning: Open your Kanban. See what's there from last week. Archive last week's Done column (move it somewhere so you can reference it but it's off the active board). Start with an empty Done column.

Daily: Move tasks through the board as you work. When Doing gets full, you resist adding more. You finish something and move it to Done before picking up new work.

Friday afternoon: Review your Kanban. See what moved to Done. Notice what's still in Doing (probably means it's complex or has external dependencies). Assess what's still in To Do. Capture anything new that came up during the week.

Repeat next week.

Limiting Work in Progress

The power of personal Kanban is in the constraint. You don't allow unlimited tasks in Doing.

For most people, two to four things simultaneously is realistic. Anything more and you're context-switching constantly. Anything less and you're probably not fully using your time.

The limit isn't about productivity. It's about focus. When you hit your limit in Doing, you stop taking new work.

You finish something, move it to Done, then pick something new. This creates rhythm.

Some people keep the limit strict: no more than three things in Doing, ever. Others are flexible: usually three, sometimes four if something is nearly done.

Handling Tasks That Span Multiple Tools

A common scenario: you're working on a feature. The design is in Figma (no task). The engineering work is in Jira.

The product spec is in a Google Doc. The client feedback is in Asana. One conceptual task, multiple tools.

Your Kanban task might be "Feature X - design to launch." It represents the whole thing, even though the actual work lives in different places.

This is where personal Kanban helps. You see the feature as one item moving through your personal workflow, even though the actual work is fragmented across tools. The Kanban gives you a coherent view of your work that matches how you actually think about it.

Connecting to Your Team Systems

At the end of the week, when you review your Kanban, you're seeing what you actually accomplished. This is data for your weekly team standup.

"This week I moved X, Y, and Z to Done. I'm in Doing on A and B. I need unblocked on C." That's your update.

You're not reading directly from tools. You're reading from your Kanban, which shows your actual workflow. This makes team standup faster and more accurate.

Beyond Three Columns

Once you're comfortable with basic Kanban, you can add structure:

Priority within To Do - Items at the top are higher priority. You pick from the top when you move something to Doing.

Tags or categories - You might tag tasks by project or context. You can then filter to see just the Asana tasks, just the Linear tasks, etc.

Estimated effort - Some people add rough estimates of how long things take. This helps with capacity planning.

But start simple. Three columns. Limit work in progress.

Update daily. You can add complexity later if you want it.

The Real Value

The real value of personal Kanban isn't the tool. It's the practice. By moving tasks through three columns daily, you're creating a personal ritual around your work.

You're making progress visible to yourself. You're creating daily wins.

This matters more than any productivity metric. When you can see what you finished, when you've moved 15 things to Done by Friday, when you literally see the visual pile of completed work - that feedback loop is motivating.

FAQ

Should my personal Kanban exactly match my assigned tasks in team tools?

No. Your Kanban might have fewer things (only what you're actively working on) or it might group differently. It's okay if they don't match perfectly. The Kanban is your view, not the team's source of truth.

What if my Doing column is always full?

That's a signal you're overloaded. Try reducing it to two items for a week and see what happens. Usually your actual capacity is lower than you think.

Can I have a Kanban for personal work and a separate one for team work?

Yes. Some people do. But most find one unified Kanban is more powerful - it shows everything you're committed to in one place.

Should I use the same Kanban for my team and for personal work?

Usually no. The team needs to see all 40 items in progress. You only need to see your three or four.

How do I keep my Kanban in sync with my team tools?

Either accept manual sync during your weekly review, or use a tool that syncs automatically (more advanced Kanban setups can integrate with APIs). Most people find weekly manual sync is sufficient.

What if I add something on Tuesday but forget to add it to the Kanban?

It'll show up in your weekly review. You'll add it then.

Perfect is the enemy of good. An imperfect Kanban that you update weekly is better than a perfect Kanban you never maintain.