Modus calendar | Modus Institute | Personal Kanban: Mapping Work | Navigating Life
After about twenty years of working with individuals, teams, and organizations of every shape and size it is clear that people are not lazy, selfish, or broken. We want to do good work. We want to be there for our colleagues, their families, their communities. We want to improve things. I know we’ve been taught to be skeptical about this, and it is easy to be given the ‘evidence’ of the way things go down every day. But this isn’t just aspirational chatter, it is what we have observed, consistently, across thousands of people trying to navigate their days.
But work piles up. Priorities blur. The most important thing keeps getting displaced by the loudest thing. People get overloaded, distracted, and overwhelmed. The environment they’re working in makes it genuinely hard to act on what they value. They end up exhausted and behind, doing less of the right work and more of the reactive work, caught in a loop they can’t seem to break.
And that gets frustrating.
Personal Kanban was built to break that loop. Two rules (visualize your work, limit your work in progress) turn out to be surprisingly powerful levers against the cognitive and social forces that keep people stuck. We’ve watched it work for individual contributors and executive teams, for nurses and software developers, for families trying to get the dishes done. For kids learning the alphabet. For teams building airplanes.
Last week, we had the five productivity lenses. This week it is five behavioral economists. People who spent careers mapping the gap between how humans intend to behave and how we actually do. If we get even a little of this, it gives us some reassurance we aren’t the problem, and a little push to building better Personal Kanbans to help us solve these puzzles.
Five behavioral economists with different perspectives, working separately, from different directions, with different methods, have each described mechanisms Personal Kanban makes practical. Their findings are not abstract. They are an explanation of the board you’re already using, or the board you’re about to build. And together, they point toward something hopeful: the problem was never you. It was the system. And the system can be fixed.
Here is what your Personal Kanban can do.
Most people read about better work. Paid subscribers build it. Get the full essay archive, member discussions, and early access to everything Modus makes.
Daniel Kahneman and Your Need to Plan and Adjust
Daniel Kahneman spent fifty years tirelessly documenting the myriad of ways human judgment goes off the rails. His central finding is based on two cognitive systems. System 1 is fast, automatic, and associative. This is your day-to-day judgements that run on heuristics and pattern-matching. System 2 is your slow, deliberate, and effortful mode, where you actually think something through.
System 1 is overconfident, lazy, and necessary. It generates answers that feel right without doing the work to check whether they are. Left to its own devices, System 1 will manage your workload using whatever information is most easily available...the most recent request, the task with the most social pressure, the work that feels familiar. System 1 is not prepared for change or complexity. Its job is to make snap judgements and move on. One is not better than the other, you’d over analyze everything if stuck in system 2 and be completely groundless if you were stuck in system 1.
That being said, the brain wants to stay in system 1 as much as possible because it is the least exhausting.
The planning fallacy is Kahneman’s term for our universal tendency to underestimate how long tasks will take. System 1 is action oriented and when you estimate a task, you want to get to work, so you construct an optimistic scenario of smooth completion (a happy path) and ignore or at least don’t look for evidence about how similar tasks have gone before or any complexity (weird) might be in this task. This is why you consistently think this week will be the week you get everything done and...it never is.
What the PK board does: It forces a reckoning with System 1’s errors before they compound, by giving you system 2 triggers. Letting you plan better and know when System 2 is necessary. WIP limits are correct for the planning fallacy...when you can only have three (or less) things in progress simultaneously, you are forced to watch how long those three things actually take before committing to a fourth. This makes you pay attention to the what, the why, and the weird for any task you take on. The board is triggering you to watch for the right work to pull at the right time.
Over time, you will also use the Done column to spot problems. You begin to see, concretely, how long your work actually takes versus how long you thought it would. You see where you will run into complexity and avoid the availability heurisitic, Kahnemann’s tendency to judge future tasks by the most memorable past tasks.
The design pattern: The Thinking Ticket is an elegant answer to the System 1 problem. It is a card, a literal, physical card, deliberate reflection (see last week’s discussion of deep work). This schedules regular System 2 engagement rather than demanding it constantly, helping us figure out how we figure things out...and get better at it. Most productivity systems burn out their users by requiring deliberate thought at every moment. The Thinking Ticket makes slow reasoning a designed event, not a perpetual grind.
The board does not make you smarter. It makes your cognitive errors visible before they become expensive.
Richard Thaler and Your Board as a Decision Engine
Richard Thaler tells us that people’s choices are profoundly shaped by the environment in which those choices are presented. This is how social media eats your brain. We make choices not by our values, intelligence, or intentions...we decide things in the architecture of the choice itself.
He calls this libertarian paternalism and it’s nasty. You retain complete freedom to choose whatever you want, but the design of the environment nudges you toward better choices without forcing anything. A cafeteria that puts fruit at eye level and cake at the back is not restricting your freedom, it is acknowledging that what you choose first is what you see most prominently and designing accordingly. (The same obviously works for the grocery store with candy surrounding the checkouts and chips now moved to the ends of nearly every aisle).
Every kanban board is choice architecture. You just may not have designed it intentionally. (And hopefully now you will.)
The left-to-right flow, (Backlog, Doing, Done) is a nudge that makes forward progress feel natural and backward movement immediately apparent. We use the WIP limit to nudge: it creates an artificial scarcity that forces you to think before you start something new. Color coding your stickies is a nudge that puts different tickets into different contexts. Even just having a Done column is a nudge, operationalizing what Thaler calls mental accounting...our tendency to track outcomes in like transactions. Completed work gets “banked.” The Done column is the ledger.
What the PK board does: The Priority Filter (see the last article again) has a P3/P2/P1 structure with decreasing WIP limits, providing nudges theory in a very physical way. The shrinking column capacity (10 → 6 → 3) means the default path through your backlog leads to your most important work. You are not forced to work on P1 items. But the architecture ensures that P1 is what you encounter first when you look for something to pull. (Again, the word is nudge, not enforce.)
Thaler’s research on status quo bias explains why backlogs become graveyards. People irrationally prefer whatever is already in place, so weirdly, once a task is in the backlog, the status quo is to leave it there. Respecting and regularly reviewing your backlog can nudge against at least this status quo bias by making inaction a conscious, visible choice rather than an invisible default. The card doesn’t just sit there anymore. It sits there deliberately, or it gets removed.
So when you build your board it will always nudge you. Now you just have to make sure you know how you need to be nudged and get the board to work for the best version of you.
Weekly essays on work, flow, and staying human while getting things done. Paid subscribers get deeper dives, tools, and access to the conversation.
Elinor Ostrom and Your Team’s Workflow Commons
Elinor Ostrom won the Nobel Prize for proving something the economics establishment had previously declared impossible: communities can successfully manage shared resources without either privatization or top-down control. The “tragedy of the commons,” the notion that shared resources will always be depleted by individual self-interest, was not an iron law. It was a failure of institutional design.
From my background as an urban planner, collaboration, and business process, her research was the most welcome of revelations. She created 8 principles of governance that read like a manual/bible/greatest hits for team kanban.
So when you are working together, the shared resource in a team is not the board or even the tasks. It is your internal attention economy. How much energy you spend to get things done. Your team has a collective cognitive capacity, the finite pool of focus available at any given moment. When individuals on a team manage their work invisibly, without shared sight into the state of the whole, the commons gets depleted, because your work is fundamentally unmanaged and uncared for.
Yes, when you manage your tasks or your schedule, you are ignoring the actual work. Individuals in teams create value. So, when someone takes on too much and creates bottlenecks, someone else’s blocked work becomes everyone else’s problem, invisibly. Urgent work crowds out important work across the whole system, not just for one person. (again, see last week’s article.)
What the PK board does: A shared team board implements Ostrom’s principles and gives them visible structure. Clearly defined boundaries: the board defines what work belongs to this team and who is part of it. Congruence between rules and local conditions: WIP limits set by the team to reflect real capacity, not aspirational fiction. Collective choice arrangements: the team sets its own policies in retrospectives, not a manager imposing rules from above. Monitoring: the board is the monitoring mechanism, visible to all participants simultaneously, with no reporting lag.
The design pattern: Collaborative Aid shows team members having each other’s backs. They react professionally when blocked work becomes visible on the board. This is Ostrom’s graduated response principle in practice. When a card is stuck, the board signals it. The team can respond calmly and together, not as a crisis, but just reacting as a community. Ostrom found this immediate and shared response to a problem essential to sustainability. This replaces accountability (punitive) with responsibility (professional). The alternative is how we work now — each person managing their own work invisibly — and that’s a recipe for what she called free-riding and depletion.
And using a kanban board to democratize meetings with Lean Coffee, is an institutional design intervention. Collective time is a commons. It is chronically undervalued in most organizations. Too many meetings with too little results. Structuring meetings with visible cards, time-boxed contributions, and shared context is governance. It establishes rules, distributes agency, and makes the cost of the commons visible to all its participants.
Dan Ariely and Real Motivation
Dan Ariely has written a lot (a lot) of books documenting a single, inconvenient fact: humans are not rational economic agents. We are predictably irrational. Our irrationality follows systematic patterns, which means it can be studied, anticipated, and (crucially for us) designed for.
His research on motivation produced a finding that should embarrass every productivity system ever built. People are not primarily motivated by efficiency, or incentives, or logical arguments about what they should do. They are motivated by meaning, autonomy, and visible progress. The feeling that their effort matters. The evidence that something is getting done.
This information is exploited by every online shopping experience, political party, and entertainment company on earth. It’s time to take this and deploy it for something good. So, while most productivity systems optimize for throughput and ignore motivation entirely, we would like to treat humans as something other than execution engines. Personal Kanban wants more.
What the PK board does: Again, we look at the Done column which implements Ariely’s research with Teresa Amabile on the progress principle. It turns out the progress that you can see is the most powerful day-to-day motivator. More than recognition, more than incentives, more than management quality. Every card that moves to Done is a small psychological event...a completed loop, a mark of progress, concrete evidence of competence. The board generates these events continuously, structurally, without requiring anyone to remember to acknowledge them. If you look at the apps we’ve been building...all of the Modus systems show WIP ... and the results of successful work. See the system, see the success, and maintain it.
The design pattern: How Does Your Work Make You Feel? uses the Done column for specific personal reflection. This is just one example that annotates completed cards with emojis when it’s moved to done. Ariely’s research on experience utility shows a persistent gap between how we predict work will feel and how it actually does. We are bad at forecasting our own satisfaction. But if you track how completed work actually made you feel, you calibrate over time. Much of our dissatisfaction isn’t with the work, but it’s in buying into ways of working that make us turn in work we aren’t happy with.
Ariely calls this completion anxiety...the tendency to avoid finishing things because completion triggers judgment. People end up turning in work at the deadline that they know is incomplete or substandard because they never had the ability to do it right the first time. We want to see that work as it is, turned in but unloved, and then react.
Sendhil Mullainathan and the Scarcity of You.
Sendhil Mullainathan‘s research produced one of the most practically important findings in modern behavioral economics...that scarcity of your time measurably and directly taxes cognitive capacity. This is one of the first messages in the Personal Kanban book.
When we are under cognitive load (almost all the time), carrying too much in active memory, our executive function degrades. The capacity for planning, self-control, and complex decision-making is a shared resource, and scarcity depletes it whether you want it to or not. His studies showed that the cognitive impairment from carrying too much mental load is equivalent to losing a night’s sleep...or roughly thirteen IQ points.
The more that we let things stress us out, the less intelligent we become. No, we do not perform better under pressure any more than your computer works better running every program you have loaded simultaneously.
What the board does: WIP limits are a bandwidth intervention, and framing them this way is powerful. The conventional argument for WIP limits is about throughput: finish more by starting less. True, but incomplete. The deeper mechanism is cognitive (it’s you): when you have three things in progress instead of twelve, you are not just more focused...you are more physically, mentally, and emotionally capable. The mental overhead of tracking twelve open loops is gone. The decision about what to do next is already resolved by the board. The anxiety of incompleteness is reduced. All of that freed bandwidth is available for the actual work.
When we say focus and finish...you need to focus to finish.
To get there, Mullainathan coined the term tunneling for what happens under scarcity. In tunneling the mind fixates on the immediate constraint and ignores everything outside the tunnel. Overloaded workers tunnel on urgent tasks and systematically neglect important ones...not because they have poor values, but because they lack the bandwidth to see beyond immediate pressure. This is why How to Stay Focused in a World Full of Distractions describes cognitive residue that lingers between tasks...what Newport calls attention residue and what Mullainathan would call bandwidth leakage.
The design pattern: Combating Existential Overhead is a bandwidth intervention with a different name. What we call Existential Overhead is the literal cost in distraction and stress of uncompleted, unresolved commitments...is Mullainathan’s bandwidth tax. Every vague intention, every card that sits in the backlog without clarity, every commitment that hasn’t been explicitly deferred or acted on: these are bandwidth leaks. Closing them is not tidiness. It is restoring cognitive capacity.
Tonianne’s Clarity > Coffee makes the same point with satisfying directness. You don’t need more stimulants. You need fewer open loops. Clarity is the bandwidth intervention. The board is how you achieve it.
And for teams, Capacity: It’s a Matter of Content and Context extends this further: capacity is not just about how many tasks you have, but what kind of tasks...their cognitive weight, their emotional load, their context requirements. A team of five each carrying twelve open loops is not a team with sixty items in progress. It is a team whose collective bandwidth has been depleted to the point where even the important work will be done poorly.
What Five Economists Would Probably Agree On
Five researchers, working in different traditions, studying problems differently, converge on the same conclusion about Personal Kanban:
It works not by improving your willpower, but by changing your environment.
* Kahneman: it corrects System 1 errors before they compound.
* Thaler: it designs defaults that lead to better choices.
* Ostrom: it creates the conditions for healthy team culture.
* Ariely: it generates the visible progress that motivates.
* Mullainathan: it frees the cognitive bandwidth that scarcity steals.
Two rules. Five explanations. One board that is doing more than you realize every time you look at it.
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 from the Personal Kanban archive:
* Personal Kanban & Some Goodies About Your Brain
* On Working Intentionally: The Thinking Ticket
* Combating Existential Overhead
* The Priority Filter: A Tutorial
* Collaborative Aid: Element #10 of the Kanban
This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit humanework.substack.com/subscribe
