Flow and Small Wins Are Two Halves of the Same Engine

Two pieces of advice about engaged work sit on my desk, and on the surface they contradict each other.

The first comes from Mihaly Csikszentmihalyi's flow: lose yourself in the task. Drop the self-consciousness. Stop tracking how you're doing. Let time disappear. The second comes from Teresa Amabile's progress principle: at the end of the day, step back, notice what you got done, and feel the win. One says stop monitoring yourself. The other says monitor yourself on purpose.

So which is it? Neither, exactly — flow and the progress principle aren't competing advice — they're the same engine, feedback, running on two different timescales. Flow is feedback you get during the task, fast enough to keep you absorbed. Progress is feedback you give yourself after the task, slow enough to make the work feel like it's going somewhere. They don't fight; they hand off. And the reason both matter is the same reason: neither one is powered by willpower — both are built by how the work is designed and how you choose to look at it.

The stakes are practical. If engagement runs on willpower, the only fix is to try harder and feel guilty when you can't. If it runs on two kinds of feedback, the fix is to redesign the work and how you end your day — which is something you can actually change.

If amusement and awe were the fast, fleeting half of Engagement, this is the slower one. The companion post covered those passing feelings; this one is about the deeper engine underneath them. The four-pillar overview named flow as a construct; here's what's actually inside it.

What flow actually feels like

Csikszentmihalyi spent decades at the University of Chicago studying the high-quality work of artists, dancers, poets, and medical professionals, and he broke the state down into attributes you can check against your own week:

The test Csikszentmihalyi offers is simple: have you ever been so absorbed in what you were doing that you lost track of time and the people around you, and wanted to keep going no matter what? That's the state. And in organizational data, when people feel it at work they report being happier, more alert, more engaged, and friendlier with colleagues — and the effect spills over, so a day with flow at work tends to be a better evening at home too.

That stuck with me because it inverts the usual story. We treat "deep work" as the thing we sacrifice our well-being for. The evidence runs the other way: the absorption is itself one of the better-feeling states available at work.

Flow happens more at work than at leisure

Here's the finding that turned it around for me. We picture flow as a thing for weekends and hobbies, but Csikszentmihalyi and LeFevre found it occurs more often at work than in leisure — because work, unlike scrolling on the couch, comes with clear goals and constant feedback.

Remus Ilies and colleagues put a number on it in their 2017 study in Applied Psychology. They ran a two-week experience-sampling study of 114 full-time employees, pinging them three times a day across ten workdays — 892 matched reports in all, a 78% response rate — and coded flow as the moments when a person rated both challenge and skill above their own personal average. People hit those flow-conducive conditions on 28% of sampled occasions — well within the range earlier work found across jobs, from about 16% for cashiers up to nearly 58% for skilled craftspeople.

Csikszentmihalyi's own favorite example is a welder in a dreary assembly plant who consistently found flow in monotonous work that his coworkers found unbearable. Same plant, same task, different relationship to it — which is the first hint that flow is less about the job you have and more about how the job is built and approached.

Why flow works: it feeds two basic needs

Ilies and colleagues didn't stop at counting flow — they asked why it lifts well-being, and the answer connects flow to self-determination theory's basic psychological needs. Flow predicted end-of-day positive affect and job satisfaction, and a good chunk of that ran through two needs: competence and autonomy. Adding those two needs into the model cut the direct flow-to-positive-affect link by about a third (33%) and the flow-to-job-satisfaction link by about 27% — and of the two, flow fed the sense of competence more strongly than autonomy.

The logic is clean once you see it. Flow gives you instant, task-derived feedback that doesn't depend on a boss's approval — and that feedback is what a sense of competence is made of. And because the absorption is intrinsically driven, it carries a sense of autonomy. Flow isn't pleasant in some vague way; it's pleasant because it's quietly satisfying two of the things humans need from work.

One wrinkle worth holding: Ilies found that openness to experience moderated the effect. For people high in openness, flow strongly drove the needs and the well-being. And when those same people weren't in flow, they reported lower well-being than everyone else — as if the more curious you are, the more you actually need flow to feel good at work. That's a useful thing to know about yourself.

How to build for flow

If flow is built rather than willed, the design question is: what conditions make it likely? Csikszentmihalyi's core lever is the balance between challenge and skill. Too much challenge for your skill and you get anxiety; too little and you get boredom. Flow lives in the channel where a hard-enough task meets a skilled-enough person.

Around that core, Keltner and the broader literature point to three structural conditions, and Leo Babauta's much-shared "nine steps to flow" essay turns them into something you can actually do on a Tuesday:

• Autonomy and control — when you feel you have voice and control over your work, you like it more, feel less stress, and produce work that outside raters score higher. Babauta's practical version: pick the task yourself, find your quiet, peak-energy time, and protect it.
• Expression of your strengths and values — work that lets you do the thing you're actually good at, the thing that feels like a calling, produces more flow. Babauta: choose work you love and that genuinely matters, not the easy-but-pointless kind.
• Job crafting — reshaping the tasks, relationships, and framing of the job you already have so its dimensions fit you. I went deep on this in the purpose post on building vs. finding meaning, and it does double duty here: the same crafting that builds purpose also manufactures flow opportunities.

The thing all of these share: none of them is "try harder to focus." They're all about arranging conditions so that focus becomes the path of least resistance. Which is exactly where the second half of the engine comes in — because conditions are also what make progress visible.

The progress principle: the feedback you give yourself

Flow is the in-the-moment half. The progress principle is the after-the-fact half, and it comes from one of the larger field studies in this literature. Teresa Amabile and Steven Kramer asked 238 employees across companies — in management, invention, technology, and more — to keep daily diaries about their workday, their mood, and their motivation. Over about four months they collected nearly 12,000 entries.

The headline: of every factor they examined — getting help from a colleague, encouragement, clear goals — making meaningful progress was the single strongest predictor of a good day. On days people recorded progress, they were more likely to feel happy, be intrinsically motivated, and read obstacles as challenges rather than threats, which set them up for more progress the next day.

The detail that makes this usable: progress doesn't have to be big. Amabile and Kramer are explicit that ordinary, incremental progress moves the needle — clearing an inbox, having one important conversation, closing one small loop. If it's a meaningful accomplishment to you, it counts. The afternoon habit the Greater Good course teaches is the minimum viable version: at the end of the workday, name one win that stood out and how it made you feel. A learner in the course described coming up with a name for a new product and the team adopting it — "a small thing that did not require big efforts but the satisfaction is very high. That made my day."

Why even the feeling of progress is load-bearing

The strongest evidence that progress itself — not just the output — drives motivation comes from a study by Dan Ariely and colleagues that's almost cruel in its design. Participants built Lego figures for pay that started around $2 a figure and dropped with each one, and they could quit whenever they liked. One group's finished figures were lined up on the desk, accumulating where they could see them. For the other group — the "Sisyphus condition" — the experimenter quietly disassembled each figure right after it was built, then offered the same pieces back to build again.

Same task. Same pay. The group that could see their work pile up built significantly more.

Ariely's reading is that seeing progress gives a task purpose — even a trivial task. The Sisyphus condition didn't pay less or demand more; it just erased the visible trail of what you'd done. That's enough to drain the motivation out of work people were otherwise happy to do. Which is the negative image of the progress principle: the fastest way to break someone isn't to pile on work, it's to quietly undo the work they already did where they can watch — and a lot of canceled projects and redone work do exactly that without meaning to.

Resolving the tension: two timescales, one engine

Now back to the contradiction I opened with. Flow says don't monitor yourself; the progress principle says do. The resolution is that they operate at different moments and never actually overlap. Flow and progress don't argue over you; they take shifts.

During the task, you want the fast feedback that keeps you absorbed — and self-monitoring there would break the spell, exactly the self-consciousness Csikszentmihalyi says flow removes. After the task, when the absorption is already spent, the slow feedback of noticing what you accomplished does the work flow can't: it tells you the day added up to something. Flow makes the hour feel good. Progress makes the week feel like it's going somewhere. You need both because they answer different questions — "is this absorbing right now?" and "did any of this matter?"

"Isn't tracking wins just toxic productivity?"

The obvious objection: doesn't "count your wins every day" turn into self-surveillance — the productivity-guru habit of optimizing yourself into a spreadsheet? And wouldn't that constant scorekeeping wreck the very flow the first half of this post is defending?

It's a fair worry, and the resolution above is most of the answer: progress reflection happens after the task, not during, so it doesn't compete with flow — doing it mid-task would indeed break absorption, which is exactly why you don't. But there's a sharper point in Amabile's data. The predictor wasn't activity; it was meaningful progress. Busywork tracked for its own sake doesn't lift inner work life — and Ariely's Sisyphus condition shows that demanding visible effort while erasing real progress is the thing that actually demotivates. Surveillance is the Sisyphus condition. Noticing a meaningful win is the opposite of it.

The manager version of the same distinction: the lever isn't surveillance dashboards, it's enabling progress and not destroying it — give people meaningful work, remove obstacles, and resist canceling projects, which is the organizational Sisyphus move. The honest line is that the progress principle is a tool for recognizing real progress, not for manufacturing the appearance of it.

A few things I'm taking away

• Flow and the progress principle only look like opposite advice — they're the same feedback engine on two timescales, one during the task and one after
• Flow's attributes are concrete: intense concentration, time distortion, dropped self-consciousness, little concern for rewards, intrinsic motivation — and it feels good, not just productive
• Counterintuitively, flow happens more at work than at leisure because work supplies clear goals and constant feedback — Ilies and colleagues clocked it at about 28% of work moments
• Flow lifts well-being largely by feeding two basic needs, competence and autonomy — and the more open to experience you are, the more you seem to need flow to feel good at work
• Flow is built, not willed: match challenge to skill, protect autonomy, lean on your strengths, job-craft, and clear a quiet block — none of it is "focus harder"
• Amabile and Kramer's 12,000 diary entries found meaningful progress was the single strongest predictor of a good workday — and incremental progress counts as much as the big wins
• Ariely's Lego study showed that simply letting finished work stay visible made people build far more than an identical-pay group whose work was disassembled — seeing progress gives even a trivial task purpose
• The toxic-productivity worry resolves on timing and meaning: reflect after the task, on meaningful progress — surveillance and erased progress (the Sisyphus condition) are what actually demotivate

The Sisyphus condition is the part I can't shake — same pay, same task, but the work quietly taken apart the moment it was done. It's such a small change, and it breaks people. Most of us aren't building Lego for declining wages, but a lot of work has a version of it: the report no one reads, the project canceled at 90%, the day that dissolves into pings with nothing left standing at the end. Flow is how an hour feels worth being inside. Noticing the win is how you keep the day from being disassembled behind you. Neither is willpower — both are just refusing to let good work vanish without being felt.

Sources

• Csikszentmihalyi, M. — Flow: The Psychology of Optimal Experience (1990); Keltner lecture "Do You Feel Flow at Work?", Science of Happiness at Work, BerkeleyX. Used for: the attributes of flow, its benefits and spillover, the challenge/skill balance, and the welder example
• Csikszentmihalyi, M., & LeFevre, J. (1989) — "Optimal experience in work and leisure," Journal of Personality and Social Psychology. Used for: the finding that flow occurs more often at work than in leisure
• Ilies, R., Wagner, D., Wilson, K., Ceja, L., Johnson, M., DeRue, S., & Ilgen, D. (2017) — "Flow at work and basic psychological needs: Effects on well-being," Applied Psychology: An International Review 66(1). Used for: the 28% flow frequency, the competence/autonomy mediation, and the openness-to-experience moderation
• Babauta, L. — "Nine Steps to Achieving Flow in Your Work," Greater Good Magazine (orig. Zen Habits). Used for: the practical how-to steps for arranging flow conditions
• Amabile, T., & Kramer, S. — The Progress Principle (Harvard Business Review Press) and "The Power of Small Wins," HBR. Used for: the 238-employee, ~12,000-entry diary study and the finding that meaningful progress is the strongest predictor of inner work life
• Lindsey, J. — "Do This in the Afternoon for a Better Workday Tomorrow," Greater Good Magazine. Used for: the afternoon small-wins reflection habit and the course learner's example
• Ariely, D., Kamenica, E., & Prelec, D. — Lego/"Sisyphus" experiment on meaning and labor (and Payoff). Used for: the demonstration that visible progress drives output independent of pay
• Wrzesniewski, A., & Dutton, J. E. (2001) — "Crafting a Job," Academy of Management Review 26(2). Used for: job crafting as a route to building flow opportunities
• Greater Good Science Center, UC Berkeley. Used for: the editorial framing of flow and progress as cultivable, not innate