← Back to list

Stop Juggling Tasks. Start Moving Them

A method from a 1940s car factory that still fixes overloaded to-do lists.

Yana Nikulinskaya · 2026-05-05 02:43 · 0 claps · 5.7 min read
#kanban #kanban-board #productivity #product-management
Open on Medium ↗
Wiki topics: BIZ · Business Strategy 📋 · Product Management ⏱️ · Productivity 🏀 · Basketball

Stop Juggling Tasks. Start Moving Them

A method from a 1940s car factory that still fixes overloaded to-do lists.

Ever open your task list, scroll through it, and close it without doing a single thing?

You looked at fifteen items marked “in progress,” three of them from last week. You could start any of them — but that would mean picking one and ignoring the other fourteen. So you scrolled, felt vaguely guilty, and went to check your messages instead.

Research on task switching explains what just happened: every jump between tasks costs your brain a small but real chunk of processing power. Stack enough of those jumps in a day, and the total cost can reach up to 40% of your productive time. The American Psychological Association is direct about it: what we experience as “multitasking” is actually rapid switching, and every switch has a measurable cognitive cost.

So the problem isn’t laziness, and it isn’t poor prioritization. The problem is having too many open loops at once. There’s a method that solves exactly this — it was born on a factory floor in Japan, and it comes down to one rule.

Step 1. Three Columns: “To Do” → “Doing” → “Done”

Sticky notes on a wall. A whiteboard. Columns in a notebook. The format doesn’t matter — what matters is that every task has exactly one place, and you can see all of them at a glance.

This is the core of a method called Kanban. In the late 1940s, Toyota engineer Taiichi Ohno noticed how American supermarkets worked: shelves got restocked only when they emptied. Nobody stockpiled a thousand parts “just in case.” Ohno adapted this for car manufacturing — each part got a physical card (kanban means “signboard” in Japanese) that moved across a board through stages: waiting → in work → done.

In 2007, David Anderson took the same idea and adapted it for knowledge work — for people managing projects, writing code, running campaigns. The principle stayed identical: make all your work visible, and move it through stages. Your three columns are that board.

Step 2. Put Every Current Task on the Board

Each task gets its own card. Sort them into columns based on reality, not aspiration.

If you’re used to juggling ten things at once, don’t pretend they’re all “in progress.” A task you haven’t touched in two weeks isn’t in progress. Move it back to “To Do” or take it off the board entirely. This part can sting — but a board full of honest cards is far more useful than a board full of wishful thinking.

Once everything is laid out, you’ll probably notice something: the “Doing” column is overflowing, while “Done” is nearly empty. That picture alone explains why your days feel busy but unproductive. And it leads directly to the next step.

Step 3. Set a Limit on “Doing”

This is where Kanban stops being a pretty list and becomes a system.

WIP limit — Work In Progress limit — is the rule that makes the whole method work. You write a number on your “Doing” column: say, five. No more than five tasks there at any time. Want to start something new? First, finish or drop something that’s already there.

This was Ohno’s original insight at Toyota: if the “in work” column is full, you stop pulling in new cards. You finish what’s there first. Without this rule, a Kanban board is just a to-do list turned sideways.

The first few days, the limit feels restrictive. You see a task you want to grab, but your column is full, and you have to finish something before you can. Then, after a week or so, something shifts: tasks that used to sit half-done for weeks are actually getting completed. Your evenings stop ending with that familiar “I was busy all day but finished nothing” feeling. You’re not working more — you’re just not scattering anymore.

This works at scale, too. Vanguard, one of the world’s largest investment management firms, evolved from Scrum to Kanban and saw a 4x improvement in delivery throughput. Same teams. Same workload. Different rule about how much can be in flight at once.

Step 4. Check Your Board Every Morning

Once the board is set up, you need a habit to keep it alive. Here’s one that works: every morning, before you dive into anything, look at your board and ask three questions. What moved since yesterday? What’s stuck? What can I drag to “Done” right now?

That’s it. Not a planning session. Not a rethink of your whole week. Just a scan — the kind that takes less time than making coffee.

The real value shows up after a few days. You start noticing patterns. Maybe the same task sits in “Doing” all week without moving. That’s a signal worth paying attention to: is the task too big? Is the next step unclear? Are you waiting on someone? Each stuck card is telling you something, and the morning scan is how you hear it.

Step 5. Use the Board for Your Day, Not Just Projects

Kanban works for projects, but it works just as well for a single day.

Picture your “Today” view as a separate board: in the morning, your tasks for the day sit in “To Do.” As you work through them, you move cards across. By evening, you can look at the “Done” column and see everything that actually happened — instead of staring at a half-checked list that still somehow feels like not enough.

The daily board stays independent from your project board. If you move a task to “In Progress” on your Today board, it doesn’t shift in the project. Think of it as a snapshot of your day — a way to see your progress in real time, without messing up the bigger picture.

There’s something quietly satisfying about a “Done” column that fills up as the hours go by. A to-do list only ever shrinks. A Kanban board grows on the right side.

Step 6. Once a Week — Spot What’s Stuck

The steps above will get your board running. This one makes it better over time.

Once a week, look at your board and ask: which tasks keep getting stuck? If the same kind of card stalls every week — say, anything that requires someone else’s input — that’s not bad luck. That’s a bottleneck.

Kanban calls this approach “incremental change”: you don’t overhaul the whole system — you notice one thing that’s not flowing, try a small adjustment, and see what happens. Maybe a recurring stuck task needs to be broken into smaller pieces. Maybe it needs a different column. Maybe it shouldn’t be on the board at all.

The weekly review is what separates people who try Kanban for a week from people who actually keep using it. The board is a mirror — the review is when you look into it.

When Kanban Is the Wrong Tool

Kanban is built for managing a continuous flow of tasks. That makes it great for ongoing work — but not ideal for everything.

A project with a hard deadline and a fixed scope needs a plan that ties tasks to specific dates. Kanban doesn’t track countdowns — it manages streams. If you need to ship a feature by a specific date with an exact list of deliverables, a timeline will serve you better.

A situation where you depend entirely on other people’s responses won’t work well either. Cards will pile up in “Doing” through no fault of yours, and a board full of stuck cards gets demoralizing fast.

The flip side: when your work is a continuous stream — requests coming in, tasks piling up, priorities shifting — Kanban gives you something no calendar or to-do list can: a clear picture of what’s moving, what’s stuck, and where the real bottleneck is.

As Snigdha Bora, an engineering lead at Microsoft Digital, put it: Kanban works by removing artificial time boundaries. But sometimes the structure of sprints and regular reviews is exactly what a team needs to stay aligned. It depends on the type of work.

Tomorrow Morning

Don’t build the whole system. Just try the board.

Grab a piece of paper. Three columns. Put your current tasks in the right one. Write a number on “Doing” — that’s your limit. Then go about your day, and see what it feels like to finish something before you start something new.

We built Kanban boards into SingularityApp — in projects and in the “Today” view — because sometimes tasks need movement, not more planning. But paper works just as well. Three sticky notes is enough.


메타데이터
post_id
ea9ebeb7a18a
slug
stop-juggling-tasks-start-moving-them-ea9ebeb7a18a
url
https://medium.com/@y_nikulinskaya/stop-juggling-tasks-start-moving-them-ea9ebeb7a18a
canonical_url
https://medium.com/@y_nikulinskaya/stop-juggling-tasks-start-moving-them-ea9ebeb7a18a
author_url
https://medium.com/@y_nikulinskaya
status
ok
fetched_at
2026-06-09 15:37:30