During our initial kick-off call, a coaching client shared how he made the “heinous mistake” of taking a sick day, only to return to his desk where he was greeted by:

• 34 unread messages in Slack;
• 9 in Teams;
• 3 “quick questions” in an inbox that was already overflowing with (other people’s) “emergencies” and requests for his attention; and
• a Google calendar tiled within an inch of its life with meetings that were only supposed to take 45 minutes to an hour. (But we all know most could’ve probably been an email.)

Somewhere behind those update alerts lived the real work that he cared about: a manuscript draft to his editor that was already late, a strategy doc awaiting his feedback, a colleague he’d been meaning to email back, but all he could see in front of him was more of other people’s emergencies.

So he did what most of us do when put in that situation: he started tackling whichever tasks screamed for his attention the loudest. “I’ll reply to my boss first, then leave a few quick comments on Slack, then between my meetings squeeze in a quick edit on the Strategy doc.” By noon he shared he was exhausted yet weirdly wired, with the sneaking suspicion that he made zero progress on anything that actually mattered to him.

If you would have asked him how his day progressed from there he likely would have said he was slammed. But if you asked him the next morning what he’d finished, he probably would have stared at you for a second, laughed nervously, and then changed the subject.

Like he totally did with me.

It’s not because he was unmotivated. Nor was it because he was disorganized. It was because he was one person facing far too much work, all arriving at once, all demanding it becomes his priority.

The problem wasn’t that he wasn’t trying hard enough. The problem was that the system around him quietly assumed he could do everything.

Overwhelm Feels Personal. It Isn’t.

Overwhelm lives in our body. It’s in the furrow of our brow, the tightness of our shoulders, the racing of our monkey minds. It manifests itself in the shallowness of our breathing and in the scatteredness of our thoughts: I should be able to handle this…Everyone else seems to be managing fine…If I just pushed a little bit harder…

It feels like a personal failing. Yet most of the time, it isn’t.

Most of us work inside systems that keep work half in tools, half in our heads; that rewards saying “yes” to everything, yet never explicitly states how much is ever enough. And it just keeps adding more.

If you worked on a factory floor and ran your machinery 24-7 until it started to smoke, you wouldn’t call your equipment weak or undisciplined. You’d say there’s too much going on with this thing, that it’s working – struggling – well beyond its capacity.

Your brain is like that machinery. It too has a finite capacity. And your current way of handling work is what’s overloading it.

This is what cognitive scientists call “cognitive load”: the total weight of tasks, worries, decisions, and “don’t forgets” your brain is carrying all at once. Too much load for too long is a known pathway to increased cortisol production, chronic stress, and burnout. The health ramifications sadly don’t stop there.

But first things first: Before you can change it, your brain needs to see what it’s up against.

Your Brain Can’t Manage What it Can’t See

When work is scattered – across tools, email, chat, in documents, while some is just floating around in your memory – you never get an honest representation of all you are carrying. So you do what humans do when faced with uncertainty: you try to close that opened loop. You fill in the blanks. You create plausible stories. You guess. You triage. You satisfy the loudest or easiest thing first. You promise your future self that you will figure it out somehow. Meanwhile, your brain is trying to track deadlines, remember who’s waiting for what, and prioritize things that were clearly defined in the first place.

This is not a mindset issue. This is a capacity issue.

Your brain wasn’t built to manage dozens of open loops in the dark. It can however, start to calm down when work becomes visible and finite.

That’s where Personal Kanban comes in.

Personal Kanban asks you to do two simple things:

1. Visualize your work.
2. Limit your work-in-progress (WIP)

If you’re already overwhelmed, this can sound like added effort you don’t have time for. But it’s not. Capturing the work isn’t extra work. It IS the work. It’s the moment you stop pretending you could do everything and start dealing with what’s actually there.

At this point, don’t worry about “doing it right.” Worry about getting out of your head.

To this end, take a board – physical or digital – and either draw or create three basic columns: Options, Doing, and Done.

Then, for a short window – say 20 or 30 minutes – pull everything out of your head and into your Options column: tasks, requests, projects, follow-ups. “I really should do… ” “One day we need to do…”

Remember, you aren’t committing to all of it. You’re simply being honest about all that is in your head. Many of us feel a spike of anxiety when we see this all in one place. That’s normal, and temporary. Because this isn’t new work; it’s simply work you’re finally visualizing. The point is not to stare at a wall of stress. The point is to start making decisions you couldn’t make when it was all invisible.

Now vs. Not Now

Overwhelm isn’t too much work ever. Overwhelm is too much work right now.

Your next move is at once brutally simple and yet deceptively challenging: decide what gets to be done now.

On your board, that means choosing a small number of items that get to live in Doing, while letting everything else stay in Options. This is the moment where most people say, “But I have to do all of it!” Guess what? You don’t. You have to acknowledge all of it, but not do all of it. You can only do a few things at a time, anyway.

If you normally juggle 10 or 15 things at once, start by allowing 3 to 5 cards in Doing. If that feels impossible, ask yourself: If I had to only move three things forward this week, which ones would make the biggest difference or relieve the most pressure?

Remember, you’re not abandoning the rest. You’re scrutinizing it. Then sequencing it. Overwhelm thrives on everything all at once. Your board is where everything becomes “this…then that…then that…” and so on.

Naming What You Are Not Doing Today

One of the quiet drivers of overwhelm is the belief that you should be touching everything, everyday. The board gives you a way to say, “These things will not move today, and that’s by design, on purpose.”

That might feel scary. But it might also feel like relief.

You can tell yourself the truth: I will not work on this today.

You can tell other people the truth: Here’s what I am doing right now. Here’s what I am not doing yet, because this is already in progress.

When the system is visible, “no” or “not yet” stop being moral failures and start being reasonable responses to a full board and finite capacity.

This Week’s Experiment

Try this for one week:

If there’s too much work and not enough you, try this experiment. One week. No perfection required. I promise.

Sometime today, sit down with a board and a timer. Give yourself 20 to 30 minutes to pull everything out of your head – projects, tasks, I really should tackle x, y, z – all of it. Put each piece of work on its own card in Options. You’re absolutely allowed to feel slightly nauseous looking at it all. That feeling is honesty arriving.

When you’re done, choose a small number of things that get to be in Doing for the next few days. Three is enough to start. Everything else stays in Options, which means not now, but not never.

For the rest of the week, don’t start a new card unless you move one to Done.

At the end of the week, stand in front of your board and quietly ask:

• What did I actually finish?
• When did I feel least overwhelmed?
• What did my WIP limit protect me from?

You’re not grading yourself. You’re learning about your real capacity. The more you learn, the more we can fine-tune your board in later posts.

When This Isn’t a Bad Week, It’s Simply Another Week

For a lot of individuals and teams, too much work and not enough bandwidth isn’t a rough patch. It’s simply a Monday. You can absolutely keep experimenting on your own with Personal Kanban, one board, one week, one small change at a time. Many people do, and it helps. And if this is your normal, not your exception, you might well want help changing more than your own habits.

That’s what Jim and I do. We help individuals, teams, and organizations make work visible so everyone can finally see what’s going on, set humane WIP limits so people stop burning out in slow motion, and build better conversations around the board instead of blaming themselves and each other.

If your days feel like there’s too much work and not enough you, you don’t need a tougher version of yourself. You need a better system supporting you.

In the next article of this series, we’ll zoom in on one part of that system you probably already rely on: your to-do list. We’ll look at why it keeps growing, why so much of it is half-done, and how turning that list into a simple Personal Kanban can start to change what actually gets finished.

If there’s been one constant among the individuals and teams we consult with or coach, it’s that people are certain that us humans are the problem.

He should be better at this by now.

I just need more discipline.

If the team could only get its act together, things wouldn’t be such a mess.

Now these are all smart, dedicated, conscientious folks. They’re working hard, they’re positively exhausted, and they feel they’re making little progress.

The more that we observe and listen, though, the clearer the issue at hand becomes: Their brains are doing exactly what human brains are designed to do under pressure.

It’s the way work is set up around them – around us –  that’s broken.

Modern Work Isn’t Built for Human Brains

Modern work asks you to:

• Track dozens of commitments in your head
• Respond to messages all day long
• Sit through and process back-to-back meetings
• Make progress on big efforts in moments stolen between interruptions

Then, when you – we – feel scattered and behind, modern work expects us to focus more, try harder, and be more “productive.”

But your brain doesn’t run on unlimited willpower. It runs on limited attention. Every “just a quick check” and every context-switch costs you a portion of that attention, until the minutes in your day quietly tick away.

At the same time, your nervous system is constantly scanning your environment for social threats and uncertainty: pending or missed deadlines, unhappy bosses and clients, the sense that you’re dropping something important. When work is invisible and unlimited, the threat system never really gets to stand down. It keeps you in low grade fight-or-flight that is exhausting over time.

You are not failing this system. This system is failing the way your brain and body are actually built.

You see, our brains evolved to deal with a visible, limited amount of work at one time. Instead, our work is often invisible, unlimited, and constantly changing. And no amount of dedication or willpower can make that feel even remotely sane.

Personal Kanban: Design Your Work to Fit the Brain You Actually Have

Personal Kanban was born from a simple observation: when you can see your work, and when you limit how much work you take on at any given moment, your brain can finally do its job.

Personal Kanban asks you to follow two fairly straightforward rules:

1. Visualize Your Work: Get everything out of your head that you’re currently doing, thinking about doing, need to do, and are responsible for doing. Now put it all on a shared board.
2. Limit Your Work-in-Progress (WIP): decide how much work you can reasonably do at one time, and respect that limit. This isn’t about color coding your way out of burnout or making more aesthetically-pleasing to-do lists. It’s about redesigning the work system around you so it stops competing with how your brain actually works.

Why This Series, and Why Now

Over the past near-two decades, we’ve watched people use Personal Kanban to:

• Stop feeling like they’re always behind
• Finish more of the work that actually matters to them
• Help instantiate healthy work behaviors and good habits
• Protect time for thinking, not just reacting
• Make better decisions about what to start, what to pause, and what to say “no” to

At the same time, we’ve watched the demands of modern work get more insistent, more aggressive, and more fragmented. So we’re launching this series – Your Brain is Fine. Your System is Broken. – to accomplish three things:

1. Name What You’re Already Experiencing
   First we’ll describe common work patterns in plain language: overwhelm, half-done work, constant interruptions, “busy all day, yet nothing gets finished,” burnout, and the quiet shame that comes with all of that.
2. Explain What’s Really Going On
   Then we’ll connect those everyday experiences to how your brain actually works – looking closely at things like attention, memory, motivation, and energy –  without jargon or navel gazing, so you won’t need a neuroscience degree to understand why your current setup feels impossible; you’ll just need your own lived experience and a little context from the research.
3. Show What to Change in Your System, Starting Now
   Finally, every article will conclude with one or two specific Personal Kanban design patterns or experiments you can try out this week. Not a five-step life overhaul, just a small, concrete, impactful change you can see on your board and act on immediately.

So, in upcoming articles, we’ll dig into questions like:

• What do you do when there’s simply too much work, and not enough you to do it all?
• Why does your to-do list never get done, no matter how many times you rewrite it?
• Why do you feel busy from the moment you sit down at your desk, yet at the end of the day you’re left wondering what you actually accomplished?
• How does overbooking your calendar quietly turn into burnout?
• Why do smart, caring people end up blaming themselves instead of the system they’re in?
• How can teams use a shared board to talk about fairness, workload, and capacity in depersonalized / non-accustatory ways?

Each article will follow a simple pattern:

• A real situation from work or life that you’ll recognize
• A clear explanation of what’s happening to your attention, memory, and energy
• A practical Personal Kanban experiment you can run on your own board or with your team

This series is for you if:

• You’re overwhelmed, and “work harder” stopped working a long – looooong – time ago
• You’re a manager or leader who knows your team is stretched well beyond their capacity, but doesn’t know what to change first
• You’ve tried all the usual productivity tricks and are tired of feeling like the problem is you
• If you are already using a board, we’ll help you tune it for the brain you actually have. If you aren’t, we’ll show you how to get started with Personal Kanban without making a giant project out of it.

If you want help changing the system, you can absolutely use this series as a self-guided path: read an article, try one experiment, see what changes, repeat.

And if you want support:

Our coaching helps individuals in small teams redesign their work systems around Personal Kanban
Our workshops and consulting bring this thinking into organizations – making work visible, setting humane limits, and building better conversations around the board.

Where We Start

But before we talk about focus, burnout, meetings, or fairness, we’re going to start with the thing almost everyone brings to us first: “There’s just too much to be done!”

Too much work. Too many people needing you. Too many “urgent” things that somehow still don’t get finished.

So the first stop in this series is the most familiar one: what to do when there’s too much work and not enough you. We will sit with what that actually feels like, and then use a simple Personal Kanban board to start turning everything all at once into this…then that..in a way your brain can finally live with.

Because your brain isn’t the problem. The way your work is set up is. And that is something we can change. Together.

Now let’s get started…

This is part of the Five Moments series — five experiences that tell you your brain needs a board. Start with The Science of Finishing Things on Humane Work.

You sit down to work. The list is right there. Fifteen items, maybe twenty. All of them legitimate. Most of them overdue. None of them obviously first.

So you open your email.

This is not laziness. This is not weakness of character. This is your brain doing exactly what it was designed to do when confronted with too many options and no clear signal: it stalls, buys time, and reaches for the easiest available action. Email is always available. Email always feels like work. Email wins.

The problem is not your work ethic. The problem is the design of your task list.

The Anatomy of a Freeze

Decision paralysis isn’t a feeling — it’s a cognitive load problem. When the number of choices exceeds the brain’s comfortable evaluation range, it doesn’t choose poorly. It chooses not to choose. Psychologists call this the paradox of choice. Practitioners call it Tuesday.

What makes it worse: every item on a flat, undifferentiated task list carries equal visual weight. The thing that’s been sitting there for three weeks looks exactly the same as the thing that’s due this afternoon. The thing that will move your most important project looks exactly the same as the thing that will make your most urgent colleague feel acknowledged.

A list with twenty items is not a system. It is a collection of clues with no signal.

When your brain can’t find the signal, it stops looking. You do email. You scroll. You do the meeting that didn’t need doing. You end the day having been busy and not having started the thing you sat down to start. You know this experience.

Why More Options Make It Worse

Here’s the counterintuitive part: adding more tasks to your list doesn’t make you more prepared. It increases decision cost. Every item on your list is a small demand on your attention just to register as something that exists. A list of forty items costs forty attention units every time you look at it…before you’ve done a single thing.

This is the hidden WIP problem most productivity advice misses. The question isn’t “how many things can I put in my backlog?” The question is how many options do you actually need visible at any given moment.

The answer is almost always: fewer than you have.

What the Board Actually Does

A Personal Kanban board doesn’t just display your work. It filters the signal from the noise.

The columns — Backlog, Doing, Done — immediately answer the first question your brain needs answered before it can act: what is in motion right now? If your Doing column has three items, the question is not “what should I start?” The question is “what should I finish?” That is a much easier question. It has a visual answer. It does not require deliberation.

The WIP limit is the board feature that most directly addresses decision paralysis. When you’re allowed to have only three things in progress, you physically cannot add a fourth until something finishes. The board enforces a constraint your willpower cannot.

And that constraint is a gift. Not a restriction — a gift. It removes the exhausting question of “what should I work on?” and replaces it with “what should I finish?” The board answers that question every time you look at it.

Pull, Don’t Pick

The design of most task lists encourages picking — scanning everything available and making a judgment about what deserves your attention. Picking is expensive. It requires evaluation, comparison, and confidence in your own judgment under uncertainty. It is also what you do every time you open a flat, unstructured list.

Personal Kanban is built on pulling. You don’t pick the highest-value item from a flat list. You work on what’s in motion. When it’s done, you pull the next item from your Backlog. Pulling is cheap. It requires one question: what’s next?

The Priority Filter turns your Backlog into a pull system. P1 items — the three things that genuinely must move today — sit at the top and get pulled first. P2 items are what you intend to accomplish this week. P3 is everything else. When you scan the board, you’re not choosing. You’re reading.

Prioritization when there is no obvious priority is one of the hardest moments in knowledge work. The Priority Filter is the architecture that replaces that judgment call with a system. You make the hard decision once, during planning. Then the board handles the rest.

When Nothing Feels Like the Right Move

There’s a specific kind of decision paralysis that happens when everything feels equally urgent. The client thing, the internal thing, the personal thing, the thing you promised last week. You’re not avoiding work. You’re genuinely uncertain which matters most. And that uncertainty is expensive.

This is not a productivity problem. This is a prioritization conversation you haven’t had with yourself yet. The board forces that conversation. When you do your morning setup and have to actually choose which three items go into P1, you have to commit. Not forever. Just for today.

That commitment is the focus practice most people skip. They want to feel ready to work before they plan. The planning is what makes you ready.

Build the board. Set the WIP limit. Put three things in P1. The rest of your day gets easier…not because the work got simpler, but because the choosing is already done.

For the team version — what decision paralysis looks like when everyone is stuck at once — see When Your Team Can’t Decide What to Work On Next at Modus Institute. For the leadership angle on the organizational cost of daily decision fatigue, see The Decision Tax Your Team Pays Every Day at Modus Cooperandi.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

Further reading:

• How Many Options Do You Have?
• Calm Down and Finish: Limiting Your WIP
• Prioritization When There Is No Priority

There’s a specific kind of task that never moves.

It’s not that you’re avoiding it, exactly. It’s not blocked by an external dependency. It doesn’t have the guilt-weight of a Stuck Loop task, the one you know you should have done two weeks ago. It’s something else — a card that sits in your Doing column not because you’re not working on it, but because you genuinely don’t know what “done” looks like.

That’s Ambiguous WIP. And it’s one of the most expensive things you can have on your board.

The Anatomy of Ambiguous WIP

Ambiguous WIP tends to arrive through one of three doors.

The first is inherited scope. Someone gives you a task with a clear title and no clear boundaries. “Improve the onboarding documentation.” “Research competitors.” “Handle the Smith account.” The title sounds complete. The task isn’t. You start it, get partway through, and realize you don’t know when you’re supposed to stop. So you keep going, or you keep deferring, or you do work that feels like progress but never reaches an end state.

The second is changing objectives. You started with a definition of done. Then the requirements shifted, the stakeholder’s needs became clearer (or murkier), or what you delivered turned out not to be what they actually needed — even if it was exactly what they asked for. Now the task is back in flight, but without the clear target the original version had. You’re redoing work without a map.

The third is self-generated ambiguity. This one is harder to admit. Sometimes we make tasks vague on purpose — or at least, we leave them vague because making them specific means committing to something, and committing means being accountable for whether you delivered. “Write the blog post” is safely ambiguous. “Write a 600-word draft by Thursday on the topic of onboarding and send it to Maren” is not. One can sit in Doing for three weeks. The other can’t.

This is one of twenty-five WIP types — each with its own cause, cost, and cure.
If you want to understand the full map, the WIP Whisperer course at Modus Institute covers all of them.
Learn to recognize every way work becomes invisible, overloaded, or toxic before it buries you.

Why It’s Expensive

The cost of ambiguous WIP isn’t just the unfinished task. It’s the ongoing cognitive tax of a card that requires active mental management every time you see it.

A clear task can be mentally set aside between work sessions. You know what you did, you know what’s next, you can pick it up again. An ambiguous task can’t be set aside — it keeps demanding attention because the open loop is conceptual, not just logistical. What does this actually mean? What am I supposed to produce? When will I know I’m done? Every time the card enters your field of vision, these questions reassert themselves.

This is one of the reasons ambiguous WIP tends to generate existential overhead disproportionate to the task’s actual size. A small ambiguous task can produce more drain than a large, clearly defined one, because the cognitive cost is tied to the lack of definition, not the volume of work.

We also see this as a category within hidden WIP — work that’s technically visible on the board but functionally invisible because neither you nor anyone else can assess its state, its progress, or its completion.

What to Do About It

Name the definition of done before the card enters Doing. This is the simplest intervention and the one most often skipped. Before a task moves from Ready to Doing, it should have a concrete, specific end state. Not “improve the documentation” — “update sections 3 and 4 of the onboarding guide to reflect the new login flow and get sign-off from Sarah.” If you can’t state the end state, the task isn’t ready to be worked.

Give ambiguous tasks their own visual treatment. Pattern matching — color-coding your cards by type or state — can make ambiguity visible at a glance. Some people use a specific color for cards that don’t yet have a clear definition of done. When you look at the board and see four orange cards in Doing, you know immediately where your planning work needs to happen before those tasks can move.

Decompose rather than defer. An ambiguous card often contains a real task and a planning task. “Research competitors” might break into “identify five competitors and document their pricing models” (real task, clear done) plus “decide what we’re actually trying to learn from this” (planning task, also clear done). Splitting them makes both workable. Leaving them merged keeps both stuck.

Create a “Clarification Needed” column. For work that arrives already ambiguous — tasks from others that don’t have enough definition to act on — a dedicated holding column before Ready keeps ambiguous work from clogging your active WIP while you chase down the information you need. The Status Column design pattern addresses a related problem: work that’s waiting on an external response before it can progress.

The Larger Pattern

In organizations, ambiguous WIP is often a systems problem wearing a personal problem’s clothing. When the people assigning work don’t define success criteria, when “done” is determined retroactively based on whatever was delivered, when scope is left deliberately vague to preserve flexibility — the person doing the work absorbs all the cost of that ambiguity. The card sits on their board, consuming their attention, while the system generates more work with the same vague specifications.

If you find that most of your ambiguous WIP comes from the same sources — the same person, the same type of request, the same phase of a project — that’s a pattern worth surfacing. Not as a complaint, but as a systems conversation: here’s what it costs when work arrives without a definition of done, and here’s what we could do instead.

The board makes that conversation possible. Without it, the cost is invisible and the pattern never changes.

This is one of twenty-five WIP types — each with its own cause, cost, and cure. If you want to understand the full map, the WIP Whisperer course at Modus Institute covers all of them. Learn to recognize every way work becomes invisible, overloaded, or toxic before it buries you.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

If you want to work through your board or your practice directly with Jim and Toni, we offer one-hour sessions — Board Review, Kanban Setup & Design, and “Am I Doing This Right?”. Visible pricing. No sales call. Book directly.

Related reading:

• Finding Hidden WIP
• Guerilla WIP: The Work You’re Doing That Nobody Knows About
• Combating Existential Overhead
• Pattern Matching: Use Your Personal Kanban to See What is Really Happening
• Design: The Status Column

Not Even You

There’s a recurring conversation we have in workshops. We ask people to list everything they’re currently working on — not their official tasks, not their job description, just the actual things consuming their time this week. The room goes quiet. Then people start listing things they’ve never said out loud to anyone. The workaround they built because the official tool is broken. The documentation they’re maintaining that nobody asked for but everyone relies on. The fix they coded on Saturday because the bug was going to cause a customer problem on Monday and their manager had said it wasn’t a priority.

That’s Guerilla WIP. Unauthorized work done for genuine, legitimate reasons — and completely invisible to the system around it.

WIP #2: Guerilla WIP – Unauthorized Work Done for Company Benefit

What Makes It Guerilla

Guerilla WIP isn’t laziness or insubordination. It’s almost always the opposite: someone who cares enough about the work to do what needs doing when the official process won’t sanction it.

The mechanism usually looks like this: you see a real problem. You try to surface it through official channels. The response is slow, dismissive, or blocked by competing priorities. The problem doesn’t go away. You fix it anyway, quietly, on the side, during off-hours or in the margins of something else. Nobody knows. The system continues to believe the problem doesn’t exist, because there’s no record that anyone worked on it.

This creates several distinct problems:

The work doesn’t appear on your board. Which means it doesn’t appear in your capacity planning. Which means you’re carrying more work than anyone — including you — is accounting for. Your WIP is higher than your board shows.

The solution is invisible. The workaround you built lives in your head or in an undocumented corner of a shared drive. When you leave, it goes with you. When you can’t remember which version was correct, there’s no record to consult.

You are simultaneously doing work and absorbing the organizational cost of the problem not being acknowledged. The cognitive overhead of doing something covert — tracking whether it’s been noticed, worrying whether it will be misread, maintaining a mental model of the official state versus the actual state — is real and draining.

This is one of twenty-five WIP types — each with its own cause, cost, and cure.
If you want to understand the full map, the WIP Whisperer course at Modus Institute covers all of them.
Learn to recognize every way work becomes invisible, overloaded, or toxic before it buries you.

The Covert Tax

When Tonianne and I wrote Personal Kanban, we talked about existential overhead — the cost in attention and stress of unfinished work that your brain is still tracking. Guerilla WIP generates a specific version of this: the overhead of hidden work. It’s not just unfinished. It’s unacknowledged. And that gap between what’s real and what’s visible on any official record creates a persistent cognitive tax.

The person maintaining a shadow system — a spreadsheet that actually works when the official database doesn’t, a script that quietly fixes the reporting error each week — is carrying that work in full while appearing to others as if they have capacity they don’t have. When they’re tapped for something new, they say yes, because officially they have room. And then they’re doing three things instead of two, and only one of them is on the board.

This is one of the reasons that finding hidden WIP in an organization tends to produce surprise. People are genuinely shocked — often including the people doing the work — by how much invisible effort is sustaining the visible operations.

Getting It on the Board

The first move is simple in concept and harder in practice: put the guerilla work on your Personal Kanban.

Not to expose yourself or invite conflict — but because you cannot manage what you cannot see, and right now you’re managing invisible work using only your memory and your worry. A card for “maintain the reporting workaround” or “weekly data cleanup” makes the work visible to you, which is the starting point for everything else.

Once it’s visible, you can make decisions. How much capacity is this actually consuming? Is this work I want to keep doing covertly, or is there a path to making it official? If I’m spending four hours a week on this, what isn’t getting done instead?

Sometimes putting it on the board is the first step toward surfacing it — showing a manager or a team that this work is real, it has cost, and it deserves either official support or an explicit decision to stop. The Kanban Setup & Design session we do with individuals often surfaces exactly this kind of invisible load. It’s not unusual to discover that a third of someone’s actual working time is in guerilla territory.

The Organizational Side

For teams and leaders: guerilla WIP is a signal. When people are doing covert work to sustain operations, it means the official system isn’t responsive to real problems. It means the approval process is slower than the pace of actual need. It means people trust their own judgment enough to act on it, but not enough to say so out loud.

The cure isn’t surveillance or stricter process. It’s legitimacy. Regular opportunities to surface shadow work without penalty — what some organizations call “amnesty” conversations, or simply a standing agenda item for “what are you working on that nobody knows about?” — turn guerilla WIP into managed WIP. The work was already happening. Now it’s visible, plannable, and improvable.

Innovation, as the saying goes, is just guerilla WIP with a budget. Most of the best process improvements we’ve seen in organizations started as someone quietly fixing something they weren’t supposed to fix. The question is whether the organization learns from that — or keeps pretending the problem doesn’t exist.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

If you want to work through your board or your practice directly with Jim and Toni, we offer one-hour sessions — Board Review, Kanban Setup & Design, and “Am I Doing This Right?”. Visible pricing. No sales call. Book directly.

Related reading:

• Finding Hidden WIP
• Ambiguous WIP: When Your Task Has No Definition of Done
• THE NEW STUFF COLUMN: What’s Just Come in?
• When Life Won’t Let You Work: Understanding Your Overload

This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.

Everyday, I go to work and I use our Modus Pomodoro to organize the things I feel are necessary for today to be successful. This includes looking at my calendar, seeing who is on it, and making sure they are in the list. We can’t rely on just willpower, we need a things to help us see the right thing to do. The next thing to do. And to do that we need to make sure we’ve designed an environment that is right. A right environment that helps us do the right thing in the right way for the right people at the right time. You’ve probably heard that willpower is unreliable. What you may not have fully reckoned with is the corollary: if willpower is unreliable, then the design of your environment is everything.

The Modus Institute Pomodoro App

Richard Thaler has built a Nobel Prize-winning career proving this…rigorously, across dozens of contexts, with empirical data rather than intuition. His central finding is that the way choices are presented shapes what people choose, often more powerfully than their stated preferences or their intentions. The cafeteria that puts fruit at eye level and dessert at the back is acknowledging that what you see first is what you choose most, and designing accordingly (and in this case helpfully…Amazon and candy aisles, not so helpful).

Your Personal Kanban is already doing this. Every time you look at it, it’s nudging you toward something. The question is whether you designed those nudges intentionally…or whether you just accepted whatever layout felt natural and let it run the show. This is why we have so many design patterns here on personalkanban.com and on our substack. There are literally infinite ways to draw a Personal Kanban board, right now, I am using several to achieve different goals. We’ll talk about that more through this post.

Every Board Nudges, Even the Bad Ones

Choice architecture is Thayler’s term for the design of environments in which decisions are made. Every feature of your right environment is choice architecture, whether it was intentional or not. The default matters. The layout matters. What’s visible and what’s buried at the bottom of a long list matters enormously.

Right environment is our term for a space and culture you create specifically to aid you in acheiving your goals (See The Collaboration Equation for more).

To be practical for both, lets’ look at your board right now.

The easy stuff: If your Backlog has forty items in it, the path of least resistance is to pull whatever catches your eye first. Probably something recent. Probably something that feels quick. Probably something with social pressure attached. Your Backlog, as currently designed, is nudging you toward reactive work (Urgent, maybe important).

The way you have built your board is likely pushing for speed (productivity) over value (effectiveness). We all do this, in fact, to be honest, I’m doing this right now. Taxes are looming, I’m typing…because I really like to type. But on my big kanban, see below, taxes are there and they are nudging me in a different way. In the main Kanban, Taxes are at the top and with icons making me pay attention to them.

A sliver of the Modus PK in Kanban Zone.

The PK Intentionally Nudges

Here are a few other types of nudges, but, honestly, any design pattern we’ve shown, whether to prioritize, manage certain kinds of work, or study what you’ve done all leads to specific feedback you might need at certain times. So, to be clear, your board is there to guide you, but you need to design it to do so.

Nudge 1: The Priority Filter makes important work the default path.

The Priority Filter structures your Backlog into tiers: P3 (everything you might do), P2 (what you intend to do this week), P1 (what must move today). WIP limits shrink as priority rises — ten slots in P3, six in P2, three in P1. When you scan for something to pull, P1 is what you see first. You’re not forced to work on it. You’re nudged there by the architecture itself.

This is Thaler’s libertarian paternalism in practice: you retain complete freedom to work on anything, but the path of least resistance leads to your most important work. The system stops working against you and starts working with you.

Nudge 2: Make your WIP limit visible and physical.

Thaler’s research on status quo bias shows that people powerfully prefer whatever is already in place. Once tasks enter your Doing column, the status quo is to leave them there — even when they’re stuck, even when something more important has arrived. A visible WIP limit (a number written on the column header, or a physical space that only holds three cards) makes inaction a conscious, visible choice rather than the invisible default.

When your Doing column is visibly full, you see it’s full. That’s a nudge toward finishing before starting — which is exactly the behavior the limit is designed to produce. Without the visible limit, you just keep adding.

Nudge 3: Color and context lanes create the right pulls at the right moments.

Color coding your cards by type — client work in blue, internal work in green, deep work in yellow — creates visual groupings that function as choice architecture. In a focused two-hour block, yellow cards become the natural pull. In a fifteen-minute gap between calls, green cards are visible at a glance. The color isn’t decoration. It’s a system that makes the right work easy to find when you’re in the right mode for it.

Your Backlog Should Be A Living Garden of Potential

Thaler’s research on status quo bias explains something most people notice but can’t quite name: backlogs accumulate. Items enter and never leave — not because they’re being done, but because removing them requires an active decision that’s more expensive than leaving them alone.

The result is a Backlog that grows without bound and nudges you toward… nothing useful. The items at the top are recent. The ones at the bottom are two years old and vaguely aspirational. None of it is priority architecture.

The backlog review is an architectural intervention: it makes passive inaction a visible, conscious choice. Schedule it weekly. Look at what’s been sitting there for more than two weeks. For each item: pull it, defer it explicitly, or remove it. Not tidiness for its own sake. You want to be able to see the nudges…reduce the noise.

The Done Column Should Be A Living Garden of Improvement

Thaler coined mental accounting for our tendency to track outcomes in separate psychological ledgers — wins and losses, progress and stagnation. A Done column operationalizes this instinct. Completed work gets banked in a visible ledger. You’re not just finishing tasks; you’re building a record that makes progress concrete and real.

This is why the Done column carries motivational weight beyond its informational value. It’s not just data. It’s evidence of forward movement.

The weekly Done review makes that evidence usable — turning Thaler’s mental accounting instinct into an actual feedback loop. Five minutes on Friday. What closed this week? What didn’t? The board already has the answers.

Design Your Environment First

The underlying lesson from Thaler’s work is both humbling and liberating: your behavior is less a function of your character than of your environment. You don’t need more discipline. You need better architecture.

Every design choice on your board — what’s visible, what’s defaulted, how columns are organized, where your WIP limit sits — is a nudge toward some behavior and away from others. Make those nudges intentional, and you’ll find that doing the right work gets easier…not because you tried harder, but because the system stopped making it harder.

For the team version of this architecture, see When Teams Stop Choosing by Whoever Spoke Last at Modus Institute. For the leadership philosophy behind it, see What Leaders Are Actually Building When They Build Culture at Modus Cooperandi.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

Photo by Bengt Nyman

Further reading:

• On Working Intentionally: The Thinking Ticket
• Combating Existential Overhead
• Personal Kanban & Some Goodies About Your Brain

PopTech, CC BY-SA 2.0, via Wikimedia Commons

This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.

People want to know they are having an impact. But when I ask people what motivates them at work and they’ll say something about purpose, or recognition, or interesting problems. But these are aspirational, and if aspirational worked we’d all be rail thin and able to lift a Volkswagon.

Dan Ariely has spent his time measuring why people do the things they do. Why we would rationally say “I’m motivated by purpose” because, to an extent we are, but that motivation isn’t sustainable. We need something more tangible.

We need visible progress. (You Can see why this would be relevant to Personal Kanban…)

We are motivated by knowing we are moving forward. We have evidence that our effort is producing results. Small, concrete, observable, rapidly reported proof that work is getting done.

Most productivity systems are aspirational or transactional, but they are rarely systemic. With Personal Kanban we want to make sure we have both the aspirations and goals of our work, the system of our work, and the learning from it all in one place. Ariely’s research tells us that is motivation infrastructure.

The Progress Principle, Ariely’s Footprint, and PK

In 2011, Teresa Amabile and Steven Kramer published The Progress Principle, a landmark study of knowledge workers’ daily inner lives that tracked mood, motivation, and engagement tracked against what workers experienced. They concluded that the single most reliable driver of positive inner work life was making progress on meaningful work, even small progress, even on a single day. Thisis what Tonianne and Jim say in the Personal Kanban book published so many years ago.

The fact that this is stilly surprising is … painful at best. But we see it all the time, people go to work to work. What upsets us all is not being able to work! More than recognition from a manager, a sense of mission, or manufactures incentives…we are setting out to make the right work happen at the right time…which is all anyone (management, customer, worker) wants.

Ariely adds is the mechanism. Ariely did this thing were participants built Lego figures that were immediately disassembled in front of them (and we’ve seen this play out in “real life” in offices many times) showed that when the fruits of effort, the products of our creativity, are erased or made invisible, motivation collapses even when pay and task remain identical. The progress principle isn’t just an observation. It is grounded in something behavioral: humans need evidence that their effort produced something durable.

Your board holds all of this. The aspirations of the options, the system of the doing, the learning and metacognition of the done. When you have a Done column that actively shows you the value of your work, you have daily access to evidence your brain needs to stay engaged with the work.

Making your PK Board’s Done Column Work Harder

We have literally dozens of posts (several at Humane Work) that show ways to design your done columns (areas) to track impact and effort, satisfaction, impact, distractions… There is so much to learn from your work.

You Should Move cards physically (or deliberately). There is something about the act of moving a card to Done that makes completion real in a way that checking a box on a list doesn’t. The card existed in Doing. It crossed the line. It is now in Done. This is a legible event, a closed loop, a moment the progress principle recognizes.

Make it a moment. Don’t just mark it done…move it…become it.

Then Annotate how the work made you feel. Ariely’s research on experience utility found a persistent gap between how we predict work will feel and how it actually does. We’re poor forecasters of our own satisfaction — which means we keep signing up for work that depletes us because we can’t clearly remember that it depleted us before.

The fix is annotation: when a card moves to Done, mark it as energizing, neutral, or draining. An emoji is enough. After a few weeks, patterns emerge that are impossible to see without the data — and those patterns tell you where to invest and where to cut.

Review Done weekly, not just at completion. The weekly Done review makes progress visible in aggregate. You finished seven things this week. The three that moved fastest were all a certain type of work. This review takes five minutes and does exactly what the progress principle describes: it makes the week’s forward movement concrete and visible.

Completion Anxiety and Not Finishing

Ariely identified a phenomenon he called completion anxiety which is a tendency to avoid finishing things because completion triggers judgment. When something is done, it can be evaluated. As long as it’s in progress, it can’t. (Note, when scientists say tendency they mean you do this all the time.)

This explains something you’ve probably observed: tasks that sit in Doing long after they’re essentially complete. The last 10% never gets done. The email gets drafted but not sent. The document gets written but not submitted.

Your board can surface this pattern. If you review your Doing column weekly and notice cards that have been there for two or three cycles without clear reason, you’re probably looking at completion anxiety. Naming it is the first step toward addressing it.

Sometimes the fix is a conversation about quality standards. Sometimes it’s just recognizing that “good enough to finish” is better than “perfect but never done.”

Meaning and Mechanics Are Not Separate

One of Ariely’s consistent findings: meaning and mechanics are not separate. The experience of work — whether it feels meaningful, whether it registers as progress, whether it connects effort to outcome — is shaped by the structure of the work system.

You don’t create meaning through better framing or purpose statements. You create it through systems that make progress visible, completions legible, and effort traceable to outcomes.

That’s what your board does when you use it well.

The Done column is not a graveyard for finished tasks. It is evidence.

Use it like evidence.

For the team motivation dynamics, see What Teams Get Wrong About Progress at Modus Institute. For the leadership perspective on meaning and work design, see Meaning at Work Isn’t a Feeling. It’s a System. at Modus Cooperandi.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

Further reading:

• Combating Existential Overhead
• Why Retrospectives?
• Personal Kanban & Some Goodies About Your Brain

Image of Daniel Kahnemann work by nrkbeta.no is licensed under a Creative Commons Attribution-Share Alike 3.0 Norway License.

This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.

Monday mornings are their own special magic. You get up, make some food, and look at your Personal Kanban and you get this brief surge of optimism, and think — yes, this is the week I get ahead. By Thursday, you’re behind on things you were certain you’d finish by Tuesday because even Tuesday was already behind.

Don’t worry, it’s not you. Well, it is you. But it’s not your “this is me” you. It’s more your “I am human” you. So it’s not a discipline problem. Or a focus problem. It is not even really a planning problem.

It’s a brain architecture problem (not helpful I know), and Daniel Kahneman spent fifty years tirelessly documenting the myriad of ways human judgment goes off the rails — including exactly this one.

Two Systems, One Workday

Kahneman’s central finding is that the brain operates in two modes. System 1 is fast, automatic, and associative and generates answers instantly using pattern-matching and shortcuts. System 2 is slow, deliberate, and effortful and does the deeper reasoning, problem solving, and reconsidering. System 1 is fast, efficient, and often subtly or grossly wrong. System 2 is important, thoughtful, and crucial for survival, but it is a lot of energy, implies more work, and feels slower, so the brain avoids it whenever possible.

Most of your workday runs on System 1. You scan your backlog, feel an intuitive pull toward certain items, make a snap judgment about what to start, and begin. System 1 is managing your workload using whatever information is most available…the most recent request, the task with the most social pressure, the work that feels familiar. Whomever is yelling the loudest.

It doesn’t check whether that’s the right thing to do right now (though it might feel right). That would require System 2, and System 2 takes effort. The result is a workday that feels reactive even when you started with good intentions.

But … spoiler … when you have a Personal Kanban set up correctly, it can trigger right actions (taking the place of system 2) or it can trigger system 2 itself (you need to think about this thing here).

The Planning Fallacy Lives in System 1

When you estimate how long a task will take, System 1 will always build a happy path. You believe in a smooth, uninterrupted path to completion. It ignores how similar tasks have actually gone before. It doesn’t account for the interruptions, the dependencies, the unexpected complexity.

It just generates a number that feels right.

Kahneman called this the planning fallacy, and it is one of the most documented cognitive biases. It affects individuals, teams, construction projects, software releases, and government programs. No one is immune, not even Jim and Toni. The only difference is whether we’ve created a system to correct for it. Because if we don’t correct for it, just compounds on yesterday’s poor plans and you get a death spiral.

So we need a PK board to change that spiral into something better, into a virtuous cycle.

The PK Board Does Patches the Holes Before We Start Sinking

A Personal Kanban board doesn’t fix the planning fallacy. Nothing does…it’s baked into how System 1 operates, and that’s just part of being human. What the board does is make the errors visible early enough to correct them. (That’s a good thing.)

WIP limits force a reckoning. When you can only have three things in Doing simultaneously, you have no choice but to notice how long those things really take before you pull the next ticket. This is called Metacognition, you are learning about how you learn. This is key to over-relying on System 1’s optimistic (undereducated) estimates and start operating on observed reality. The board makes you take time to properly plan and execute a task.

The Done column is your correction data. Every card that reaches Done carries information: how long this type of task actually takes, where it got stuck, what interrupted it. If you liked it. If people got value from it. You are building your board to give you the information you need. Review it on Fridays. Over weeks, you build a real picture of your actual throughput, and your actual effectiveness. Not what you hoped for. Again, this metacognition lets you duck the planning fallacy: not by trying to estimate better, but by anchoring estimates to what has really happened.

Retrospectives are the System 2 event. A regular look back at what the board is showing. We want to see what patterns keep emerging, what we keep missing, what complaints we hear again and again. And we want to ask … who wants what from our work? Who should we be working more closely with? This is almost always a collaboration, a conversation, and System 2.

The Thinking Ticket Schedules Deep Thinking

Most productivity systems demand System 2 constantly. Check every decision. Evaluate every priority. Think before every task. This burns people out because System 2 is expensive — using it all day leaves nothing for the work itself.

The Thinking Ticket is one smart approach. It schedules System 2 as a discrete event rather than a perpetual overhead. It’s a card on your board whose job is deliberate reflection. When you pull it into Doing, you’re not working on a task. You’re stepping back to look at the whole board: what’s actually important, what’s been sitting too long, what System 1 has been quietly mismanaging.

Slow thinking as a designed part of the system, not something that only happens when things go wrong.

The Practical Moves

If you want to put Kahneman’s research to work on your board this week:

1. Set a WIP limit of three. Not because it’s a magic number, but because watching three things move gives you far better data than watching twelve things stall.
2. Start tracking actuals. When a card moves to Done, note how long it actually took. Even a rough mark — half day, full day, three days — is vastly more useful than nothing.
3. Review Done on Friday. Five minutes. One question: was this week typical, or was it an outlier? Over time, you’ll stop being surprised by Thursday.
4. Add a Thinking Ticket. Pull it weekly. Ask System 2 what System 1 has been getting wrong.

And hopefully now you will.

For the team perspective on these patterns, see When Everyone Can See the Plan Fall Apart at Modus Institute. For the leadership view, see The Leaders Who Know When Not to Trust Their Gut at Modus Cooperandi.

Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. If you’re new here, that’s the place to begin.

For weekly essays on work, flow, and being human while getting things done, join us at Humane Work. For courses, workshops, and live events, check the Modus calendar or visit Modus Institute.

Further reading:

• Combating Existential Overhead
• What Was I Just Doing? Zeigarnik Forgetfulness
• How to Stay Focused in a World Full of Distractions
• Collaborative Aid: Element 10 of the Kanban