Dan Ariely (credits at the bottom of the article)
Dan Ariely's Research on Motivation Reveals Why Purpose Statements Don't Work — and What Actually Does
This is part of the Behavioral Economists series. Start with The Science of Finishing Things on Humane Work.
You have probably sat in the room where someone presented the engagement survey results. Maybe you've run that meeting. The scores are down. Or they're up, but turnover is still up too. They are inconclusive.
Or you talk to people, they say they believe in the mission or the strategies, which the genuinely do, but but energy is flat and the best people are quietly updating their resumes. Because they don't know where they fit.
The answer the consulting industry sells is more purpose. Better mission framing. Stronger culture. The culture decks promise it. The all-hands meetings invoke it. And then six months later you're back in the same room with the same data.
But no one has made mission, strategy, or culture defined in a way where people can just act. And they all want to act.
Dan Ariely measured why this keeps happening. His findings are useful and uncomfortable. The average consultant isn't thrilled with them because they require thought. Not one-size-fits-all.
Purpose matters, yes. But it is not the primary driver of day-to-day motivation and engagement. The primary driver — more powerful than purpose, more powerful than recognition, more powerful than compensation — is the daily experience of making visible progress on meaningful work.
Not believing you're part of something meaningful. Not being told your work matters.
Actually seeing, concretely, that something moved because of your effort.
That finding comes from Teresa Amabile and Steven Kramer's landmark research, published as The Progress Principle, which tracked the daily inner work lives of hundreds of knowledge workers across industries. What Ariely's behavioral experiments add is the mechanism: when the output of effort is erased or goes unseen, motivation collapses...not because people are fragile, but because human motivation is built on evidence, not belief.
This distinction has profound implications for how leaders design (which they rarely do) work environments. This is also why most attempts to improve engagement through purpose-building fail to produce lasting change.
The Measurement Problem With Purpose
Purpose operates at the narrative level. It answers the question "why does this work matter?" When people have a compelling answer, they're more willing to invest effort, more resilient under difficulty, more likely to find satisfaction in the work.
But purpose is not self-replenishing. It needs to be constantly renewed by the lived experience of work...by evidence, accumulating over days and weeks, evidence that a person's effort is producing results. When that evidence is absent or invisible, purpose drains regardless of how compelling the narrative is.
This is why engagement survey scores can be high in organizations where people are depleted and burned out. People can believe in the mission and still find the daily experience of work exhausting and demotivating. The mission is intact. The experience of progress is absent.
And it is the experience of progress...as both Amabile and Kramer's research and Ariely's experiments show...that runs the engine.
We Are Predictably Wrong About Our Own Experience
Ariely built his career on documenting the gap between how people intend to behave and how they actually do...and the systematic patterns in that gap. We are not randomly irrational. We are predictably irrational, in ways that can be anticipated and designed for.
One pattern is particularly relevant for leadership: we are poor judges of our own experience utility. We consistently misjudge what work will feel like, how much we'll enjoy what we expect to enjoy, how much we'll be depleted by what we expect to handle easily. (This is a primary reason we created Personal Kanban.)
We have watched leaders — good leaders, attentive leaders — ask their teams "how are you doing?" and get the answer "fine" and believe it. Not because they're naive, but because "fine" is what people say when they're managing, and leaders are wired to hear it as a data point rather than a social reflex. It is almost never a data point.
For leaders, this means that teams will consistently misreport their own capacity and experience unless there are structural mechanisms for capturing actual data. A team that says "this is manageable" is expressing a prediction, not a measurement. A team whose shared board shows cards consistently flagged as draining over three weeks is providing a measurement.
These are different things. Leaders who confuse them make systematically bad decisions about workload and team health — and feel blindsided when the burnout eventually surfaces.
Completion Anxiety at the Organizational Level
Ariely identified completion anxiety — the tendency to avoid finishing things because closure triggers judgment — as a significant source of motivation loss at the individual level. At the organizational level, it manifests in ways that are harder to see and more expensive.
Organizations avoid closing out projects that are "basically done" because closure means evaluation. They avoid honest retrospectives because honest retrospectives surface uncomfortable truths. They maintain perpetually-in-progress initiatives because in-progress is safer than done-and-evaluated.
The result is organizations chronically full of almost-finished work. Teams perpetually carrying the cognitive and emotional weight of incomplete commitments. Leaders who feel busy but can't point to what's actually been delivered.
Retrospectives are the organizational mechanism for breaking this pattern — but only if they're structured to create safety for completion and closure. A retrospective that evaluates outcomes without blaming people for results outside their control is a psychological safety intervention. It makes finishing safer.
And making finishing safer is a precondition for the progress principle to operate.
What Leaders Actually Control
The discomforting implication of Ariely's research: leaders control less than they think about their teams' motivation — and more than they think about their teams' environment.
Leaders cannot reliably produce motivation through exhortation, recognition programs, or culture initiatives. Motivation is produced by the daily experience of work, which is shaped by the structure of the work system. Leaders can design that structure.
What does a team whose daily experience includes regular visible progress look like? It has shared boards where the work is visible to the people doing it — not just dashboards for executives, but actual real-time visibility for the team itself. It has WIP limits that prevent the depletion of perpetual multitasking. Crucially, it is a team that is structurally permitted to finish things — that has organizational cover to close loops and bank completions, rather than always pivoting to what's next before the last thing landed.
Most teams don't have that permission. They're rewarded for starting, not for finishing. For being responsive, not for being complete. The leader who wants to change this has to redesign the incentives, not just the rhetoric.
This is not a soft aspiration. It is an environmental design specification.
And unlike culture, it is something a leader can actually build in a quarter.
The Return on Experience Design
Ariely's broader body of work is based on understanding how the experience of work shapes behavior, performance, and wellbeing points toward an investment thesis that most organizations don't make explicit: the experience of work is a productivity variable.
Teams that experience their work as meaningful, progressive, and connected to results are not just more engaged...they are more effective, more creative, and more likely to surface problems before they become crises. Simply because they can see the work and act quickly. (It's easier to avoid a problem you can see.)
This reframes the question for leaders from "how do we make people feel better about their work?" to "how do we design work systems that generate the experiences that make people more effective?" The first question is soft. The second is technical. And most leaders have been trained for the first question while the second is what actually needs answering.
Ariely's answer (and Amabile and Kramer's, from a different angle) is the same...make progress visible, make completion real, make the experience of the work something the system captures and responds to. That is not a culture initiative. It is an architecture decision.
The frustrating thing, after nearly two decades of teaching this, we know how simple the starting point is. A shared board where work can be seen moving, in real time, with real time feedback...by the people doing it, every day. Not a report. Not a dashboard. The actual work, visible, moving, finishing.
That's the environment. Leaders build environments. Build this one.
For the individual board mechanics, see The Done Column Is Not a Graveyard. It's the Point. on the Personal Kanban blog. For the team dynamics of progress visibility, see What Teams Get Wrong About Progress at Modus Institute.
Modus Cooperandi is where we write about the human side of work — leadership, culture, and the behavioral science behind how teams thrive. For courses and live events, check the Modus calendar.
Personal Kanban: Mapping Work | Navigating Life is the book that started the movement. For weekly essays, join us at Humane Work.
Photo by PopTech, CC BY-SA 2.0 , via Wikimedia Commons