Teams Really Can Be Professional
Thaler's Nudge Theory Explains Why Your Team Keeps Falling Into the Same Patterns — and How Work System Design Fixes Them
This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.
"We don't have bad culture, we were just drawn that way." ~ J. Rabbit, Project Manager
Every team has a set of defaults...the way work gets prioritized when no one is actively prioritizing it, the way new requests get absorbed when no one is actively questioning capacity, the way meetings pile up when no one has designed an alternative.
Almost (and by almost I mean nearly all) teams we've worked with operate by default and call it lean, agile, safe, kanban, or something else that removes them from the critical path of responsibility over their own way of working.
We see these defaults operating the same way in every industry, country, and experience. Healthcare, software, nonprofits, manufacturing. Europe, Asia, North and South America, Africa. The patterns are remarkably consistent. The team is not failing. The team is responding rationally to the environment they've found themselves in. This is a human constant.
Richard Thaler spent his career proving that these harmful defaults are designed...just not always intentionally. They are designed by neglect, which is the erosion of human relationships.
And because they weren't designed intentionally, they almost always favor whoever is loudest, whatever is most urgent, and whatever requires the least active decision-making to accept. Thaler calls this choice architecture. We call it a right environment ... a space and culture deliberately shaped to help a team do the right work in the right way. Two terms, same insight.
The good news: defaults can be redesigned. And it's not as hard as it sounds.
Default Is Your Hands-Off-The-Wheel Way-of-Working
Thaler's central finding, developed with Cass Sunstein, is that the design of choice environments shapes decisions more powerfully than people's stated preferences. The default option...whatever requires no active decision to arrive at...gets chosen disproportionately often. This is not laziness or irrationality. It's how cognition works under real-world conditions of time pressure and limited attention.
In a team context, the defaults are the work system. When work arrives with no routing logic, it defaults to whoever responds first or whoever has the most organizational authority to demand it. When capacity isn't visible, new work defaults to "yes, we'll fit it in." When there's no structure for prioritization, urgency defaults to importance.
These aren't cultural failures. They're architectural ones. (In our experience, when a team is struggling with the same behavioral pattern week after week, the problem is almost never the people. It's the system they're operating in.)
And they're addressable through the same mechanism Thaler identifies: change the default, change the behavior.
Four Defaults Your Team Is Probably Living With Right Now
Here are four we see repeatedly. Any of these sound familiar? Good. Familiarity means it's fixable.
What gets pulled next.
In most teams, the answer to "what should I work on now?" is determined by whatever is most visible. We pull based on the most recent message, the task from the most senior stakeholder, the item with the most social pressure attached. A shared visual board with an explicit priority structure changes this default. When the board shows what's in priority order, the answer to "what next?" is structural, not social.
Teams stop choosing by whoever spoke most recently and start choosing by what the system says matters.
Whether to say yes to new work.
The default in most teams is yes, we'll fit it in. This is Thaler's status quo bias operating in reverse: the status quo is to add work, not to decline it. A visible WIP limit makes the cost of yes visible. When the Doing column is full, "yes" requires a conversation about what moves out...not just what moves in.
The board becomes the nudge without it becoming political or a personal gripe.
The WIP limit doesn't refuse the new work. It makes the tradeoff explicit. Which is exactly what a well-designed default does. We've watched teams go from constant overwhelm to actual breathing room by adding this one structural change. Same people. Same work. Different default.
How blocked work gets handled.
In most teams, blocked work disappears invisibly. The person whose card is stuck stops mentioning it after a while, routes around the blockage, or quietly deprioritizes. The team never sees the cost because there's no shared place where it surfaces.
A shared board makes blocked cards visible by default. When the whole team can see that a card has been sitting in Doing for four days, the default response shifts from invisible workaround to visible conversation. Collaborative aid where team members actively help when blocked work surfaces becomes the new default.
Whether meetings justify their own existence.
Meeting culture is choice architecture operating at its most destructive. Recurring meetings persist because canceling them requires an active decision; holding them is the path of least resistance. A team that uses visual meeting formats (visible agendas, time-boxed items, shared cards) makes the value or cost of each meeting legible in real time. That legibility is itself a nudge toward better meeting behavior.
Your Team Backlog Is Probably a Garden of Deferred Good Intentions
Most project management frameworks miss what Thaler's research on status quo bias implies for team backlogs. Items enter and stay there not because they're waiting to be done, but because removing them requires an active decision that's more cognitively expensive than leaving them alone.
Over time, a team backlog becomes a graveyard of deprioritized aspirations that nobody officially cancelled. This isn't a culture problem. It's a default problem.
A structured backlog review...regular, shared, on the calendar — changes the default question from "is there a reason to remove this?" (which favors keeping) to "is there still a reason to keep this?" (which favors honesty). Small shift. Very different outcomes.
What This Asks of Team Leaders
The implication of Thaler's work for team leaders is uncomfortable but clarifying: most of what looks like team behavior problems are actually system design problems.
The team that keeps taking on too much work isn't undisciplined. Their system has no mechanism for making the cost of new work visible. The team that holds unnecessary meetings isn't unproductive and their meeting culture has no default toward cancellation. The team that always prioritizes urgent over important hasn't failed it's just that their work system has no architecture that makes important work the path of least resistance.
Fixing these patterns doesn't require culture change campaigns or new norms documents. It requires redesigning the defaults. (This is often a relief for leaders to hear. The problem is structural, not moral.)
That's the work of choice architecture. It's also, we'd argue, the actual work of leadership...whether or not it's ever called that.
For the individual board mechanics behind these principles, see Your Board Is Already Nudging You. The Question Is Where. on the Personal Kanban blog. For the leadership philosophy behind environment design, see What Leaders Are Actually Building When They Build Culture at Modus Cooperandi.
Modus Institute helps teams and organizations work visually, limit overload, and build systems that actually improve over time. Explore our courses and live events.
For the practitioner's guide to Personal Kanban, start with the book. For weekly essays on work, flow, and being human while getting things done, join us at Humane Work.
Further reading: