Sources checked 27 October 2026. The programmer, her day and the slider positions below are illustrative examples, not measurements or a promise that flow will happen.
It is 9 a.m. and a programmer opens her ticket queue. Typo in a label. A button two pixels off. A broken link. She fixes each one in a few minutes, and by 11 she has looked at the clock more often than at the code. The morning feels endless.
After lunch, her lead drops a different kind of task on her desk: rewrite the billing system, alone, by Friday. She has never touched it. She opens the first file, then the second, and feels her chest tighten. An hour passes and she has changed nothing.
Then the task gets reshaped. Not the whole billing system: one function, with a test that tells her in seconds whether it works. It is harder than the typo tickets and she does not know exactly how to do it, but she can see the first step. She starts. When she next looks up, the office is dark and four hours are gone.
Most people have had an afternoon like that. Psychologist Mihaly Csikszentmihalyi spent decades studying it, and gave it the name people still use: flow.
What is flow?
Csikszentmihalyi began with a question about people who do hard things for no obvious reward: rock climbers, chess players, dancers, surgeons. When he interviewed them, they described the same state in strikingly similar words. Attention is completely absorbed by the task. Action and awareness merge. Self-consciousness drops away. There is a sense of control. And time changes shape: hours can pass like minutes, or a single second can stretch out. [1] [2]
He called it flow because so many of the people he interviewed used the image of being carried by a current. In his 1990 book Flow: The Psychology of Optimal Experience he described flow as one of the most enjoyable experiences people report, even when the activity itself is difficult or tiring. [1]
The important word in that sentence is difficult. Flow is not relaxation. People rarely report it while watching television. They report it while doing something that asks a lot of them.
Why easy tasks bore us and impossible ones freeze us
Csikszentmihalyi's first model, in Beyond Boredom and Anxiety (1975), put two things on a chart: how big the challenge is, and how much skill you bring to it. [2] When the challenge is far below your skill, you get boredom. When it is far above, you get anxiety. Between them runs a narrow diagonal band where the two are roughly matched. He called it the flow channel.
The model also explains why flow does not last forever on its own. As you practise, your skill grows. A task that put you in flow last month starts to drift into boredom. To get back into the channel, you raise the challenge. If you raise it too far, you slide into anxiety and need to build skill to catch up. Growth, in this picture, is a zig-zag up the channel.
Illustrative model after Csikszentmihalyi (1975) and Massimini & Carli (1988). The zone borders are a teaching sketch, not measured thresholds.
Later researchers refined the picture. Fausto Massimini and Massimo Carli, working with Csikszentmihalyi, noticed that a perfectly matched easy task (low challenge, low skill) does not feel like flow at all. It feels flat. So they redrew the map relative to each person's own average: flow is most likely when both challenge and skill are above your usual level and roughly in balance. When both are below average, the state is closer to apathy. [3] That is why the simulator above treats the bottom-left corner differently.
The three conditions
Across many studies, Csikszentmihalyi and his colleague Jeanne Nakamura describe three conditions that make flow more likely. [1] [4]
Clear goals. You know what you are trying to do in the next few minutes, not just this year.
Immediate feedback. The activity tells you, as you go, whether you are getting closer. A climber feels the hold; a programmer sees the test turn green.
A balance between challenge and skill, ideally stretching you a little.
Look back at the programmer's afternoon. "Rewrite billing by Friday" had no near goal and no quick feedback, and the challenge was far beyond her current skill. "Make this one function pass this test" had all three conditions. Nothing about her changed. The shape of the task did.
Illustrative story from the video. The felt-time bars show the pattern people describe, not data from a study.
Can you create flow on purpose?
Most of the early evidence came from interviews and from the experience sampling method, in which people carry a pager or phone and report what they are doing and feeling at random moments of the day. In one well-known study, 78 working adults were sampled for a week. Surprisingly, most of their flow moments came at work, not in their free time, even though they said they would rather have been doing something else while at work. [5] That gap between what people enjoy and what they think they want is one of the more interesting findings in the field.
Sampling studies show associations, not causes. Johannes Keller and Herbert Bless ran an experiment to test the cause directly. [6] Participants played a Tetris-like game in one of three versions: one that stayed too easy, one that sped up beyond what they could handle, and one that adjusted its speed to each player's skill. The adaptive version produced more of the core flow experience. Later accounts of the study also describe players in that version judging the session as passing faster, which is the time distortion people talk about.
A meta-analysis by Carlton Fong, Diana Zaleski and Jennifer Leach pooled 28 studies and found the link between challenge–skill balance and flow to be real but moderate. Clear goals and a sense of control mattered about as much. [7] Balance helps. It is not a switch.
Each answer is drawn from the sources listed at the end of the article.
What "just beyond your ability" really means
You will often read that flow needs a challenge "just beyond" your current ability, sometimes with a precise percentage attached. Treat that as a rule of thumb, not a law. The research supports a balance, with a slight stretch helping to keep attention engaged; it does not support any exact number. [1] [4] [7] People differ, days differ, and the same task can feel different after a bad night's sleep.
There is also a caution worth keeping. Flow feels good, and things that feel good can be overdone. Csikszentmihalyi himself noted that people can find flow in activities that do them no good, and gamers can lose hours to a game tuned precisely to keep them in the channel. Flow describes how engaged you are, not whether the activity is worth your time.
Tune your next task
You cannot order flow, but you can set the stage. The most useful move is to notice which side of the channel you are on and adjust the task, not your willpower.
If you are bored, raise the bar: add a constraint, a deadline for the next 25 minutes, a quality target, or a harder version of the same problem.
If you are anxious, shrink the next step until you can see how to start it, and give it a quick way to tell you whether it worked.
In both cases, make the goal concrete for the next few minutes and remove what interrupts feedback, such as notifications.
A thinking aid built on the three conditions of flow. It makes flow more likely, not guaranteed.
The question to keep
Flow is not about working harder. The programmer did not try harder in the afternoon than in the morning; she was given a task of the right size, with a clear target and fast feedback. Next time a morning drags or a project freezes you, ask: is this too easy or too hard for me right now, and what is the smallest change that would put it just within reach?
Sources
[1] Mihaly Csikszentmihalyi, Flow: The Psychology of Optimal Experience (Harper & Row, 1990). The popular synthesis of the research programme: the qualities of flow, its conditions (clear goals, immediate feedback, challenge matched to skill) and the change in the sense of time. A book for general readers, built mostly on interview and sampling studies rather than experiments.
[2] Mihaly Csikszentmihalyi, Beyond Boredom and Anxiety (Jossey-Bass, 1975). The first flow model: boredom when skill exceeds challenge, anxiety when challenge exceeds skill, flow in the channel between. Based on interviews with climbers, chess players, dancers, surgeons and others; qualitative.
[3] Fausto Massimini & Massimo Carli, "The systematic assessment of flow in daily experience", in M. Csikszentmihalyi & I. S. Csikszentmihalyi (eds.), Optimal Experience (Cambridge University Press, 1988). Redefined flow relative to each person's average challenge and skill (the quadrant and octant models). Italian samples; correlational.
[4] Jeanne Nakamura & Mihaly Csikszentmihalyi, "The concept of flow", in C. R. Snyder & S. J. Lopez (eds.), Handbook of Positive Psychology (Oxford University Press, 2002). A review of the conditions and characteristics of flow, written by the field's founders.
[5] Mihaly Csikszentmihalyi & Judith LeFevre, "Optimal experience in work and leisure", Journal of Personality and Social Psychology 56(5), 815–822 (1989). 78 adult workers, experience sampling for one week; most flow moments occurred at work, yet motivation was higher in leisure. A later reanalysis argues the work–leisure contrast is less sharp than often told.
[6] Johannes Keller & Herbert Bless, "Flow and regulatory compatibility: An experimental approach to the flow model of intrinsic motivation", Personality and Social Psychology Bulletin 34(2), 196–209 (2008). A Tetris-type game in boredom, overload and skill-adaptive versions; the adaptive version produced more flow. One task in a lab with student participants; the time-perception result is reported here from secondary descriptions of the study.
[7] Carlton J. Fong, Diana J. Zaleski & Jennifer K. Leach, "The challenge–skill balance and antecedents of flow: A meta-analytic investigation", The Journal of Positive Psychology 10(5), 425–446 (2015). 28 studies; the link between challenge–skill balance and flow was moderate and varied with context and measurement; clear goals and sense of control were comparably strong.
Watch the episode
One email when we publish. Research, product decisions, and what teams report back.
