What Teams Get Wrong About Progress
Dan Ariely's Research on Motivation Reveals the Structural Failure Behind Team Burnout
This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.
There's a particular kind of team exhaustion that doesn't show up in workload metrics. The team is busy — genuinely busy — but there's a flatness to the energy. Nobody is checking out, but nobody is energized either. The work gets done, mostly, but it feels like labor rather than progress.
We see this constantly. In tech teams and healthcare teams and nonprofit teams. In teams whose leaders are genuinely trying. The problem is almost never effort or intent.
Dan Ariely has spent his career studying why motivation at work is so different from how we expect it to be. Teresa Amabile and Steven Kramer have done the same, from a different direction. Where Ariely's experiments expose the underlying mechanism, Amabile and Kramer's research — tracking hundreds of knowledge workers' daily lives in what became The Progress Principle — documented the pattern: teams that can see their progress feel more motivated, more engaged, and more resilient than teams doing equivalent work that can't.
Not teams that are praised more. Not teams with a stronger sense of mission. Teams that can see — visibly, concretely, day-to-day — that the work is moving forward.
The Progress Principle at Scale
Amabile and Kramer's research tracked the daily work lives of hundreds of knowledge workers — mood, motivation, and engagement against what actually happened each day. The result: on days when people perceived they had made progress, even small progress, their inner work life was significantly better.
Progress didn't have to be dramatic. It didn't have to be recognized by anyone else. It just had to be perceivable. The worker needed to be able to see that something had moved.
Ariely's experiments explain why this holds so stubbornly true. In a series of studies, he found that when the output of effort was immediately discarded or went unacknowledged — even when the work itself was identical and the pay unchanged — motivation dropped sharply. People don't just want to produce work; they need to see it persist. The progress principle isn't an observation about morale. It is a finding about how the human brain processes effort. (We have seen the office equivalent of Ariely's Lego disassembly more times than we'd like — work completed and immediately de-prioritized, decisions made and reversed, deliverables submitted and never acknowledged. The mechanism is identical. The motivation drain is real.)
In a team context, this has two implications. First, the team's collective progress needs to be visible — not just to a manager who summarizes it in a status report, but to the team members themselves, in real time. Second, individual contributions to that progress need to be traceable — not for attribution, but so each person can connect their effort to the outcomes the team is producing.
Most team systems fail both tests.
The Structural Motivation Failure
Most project management systems are designed for reporting up rather than visibility across. Status reports flow from team members to managers. Dashboards are configured for executive audiences. Progress gets aggregated into percentages and milestones that obscure what actually happened this week and what each person contributed.
This wasn't accidental. These systems were built by people who needed to report progress, not by people who needed to feel it. The information architecture reflects that priority.
The people actually doing the work — the ones whose motivation depends on seeing progress — often have the worst view of it. They know what they personally finished. They don't know what the team finished, what's blocked, what moved.
This is a structural motivation failure. The team is working in the dark about its own progress, while the people furthest from the work have the clearest aggregate view.
A shared visual board inverts this. Every card in Done is visible to every team member, in real time. The week's progress is not a number in a report — it's a column of completed cards that everyone can see growing. The team's work life is better because its progress is legible.
Completion as a Team Event
One underused practice: treating card completion as a brief, visible team event rather than a silent administrative step. When a significant card moves to Done — a milestone reached, a thorny problem resolved, a piece of work that had been stuck for weeks — the team acknowledges it. Not a formal celebration. Just a moment of recognition that the work is done.
This is both a motivation practice and a governance practice. It reinforces the shared board as the place where work becomes officially complete — not just individually finished. It creates a rhythm of completion that counteracts the chronic forward-pull of the backlog.
Retrospectives serve a related function at a longer time scale. A retrospective that opens by reviewing what the team completed — not what it failed to complete — activates the progress principle before it gets into problem-solving mode. Teams that start retrospectives from their wins have a different energy for examining their challenges.
The Emotional Data Problem
Ariely's research on experience utility — the gap between how we predict work will feel and how it actually does — has a team-level application that's rarely discussed.
Teams make collective decisions about what kinds of work to take on and how to structure their processes. These decisions are shaped by the team's collective sense of what work feels like. But that sense is almost never calibrated against data. The team thinks certain project types are energizing. Are they?
A shared board with emotional annotation — cards marked at completion for energy level — creates team-level data on this. Over a few months, patterns emerge: certain project types consistently energize the team; certain clients consistently drain it. This data is useful in ways that no status report captures.
Completion Anxiety as a Team Dynamic
Ariely's completion anxiety — the tendency to avoid finishing things because completion triggers judgment — operates at the team level too, in ways that are often harder to see. (Note: "tendency" here means this shows up in nearly every team we've worked with, across sectors and seniority levels. It is not a dysfunction. It is a predictable human response to the way most organizations evaluate work.)
Teams avoid closing out projects that are "basically done" because closure means evaluation. Post-mortems feel exposing. So work lingers in a state of near-completion that feels like activity but produces no progress signal.
A visible board makes this pattern legible. Cards that have been in Doing for two or three cycles without clear reason are the team's completion anxiety made visible. A retrospective that names this pattern — without blame, with curiosity — creates the conditions for the team to work through it together.
The alternative is that the pattern continues invisibly, the motivation drain accumulates, and the team never knows why the energy feels flat.
For the individual board mechanics, see The Done Column Is Not a Graveyard. It's the Point. on the Personal Kanban blog. For the leadership perspective on meaningful work design, see Meaning at Work Isn't a Feeling. It's a System. 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:
What is Online Learning?