Flow is a state of complete, energized focus on an activity, in which people lose track of time and perform at their best. Good design protects it; poor design interrupts it.
Overview
Most people have experienced flow: being so absorbed in work, a game, or a creative task that time seems to disappear. Psychologist Mihaly Csikszentmihalyi, who named the state, found that it is not only enjoyable but also associated with high performance and satisfaction.[1][2]
Flow tends to occur when three conditions are present:[1]
- Clear goals: the person knows what they are trying to accomplish.
- Immediate feedback: they can tell right away how they are doing.
- A balance of challenge and skill: the task is demanding enough to be engaging, but not so hard that it causes anxiety, or so easy that it causes boredom.
Software can support flow by staying out of the way, or break it with delays, interruptions, unclear next steps, and unnecessary friction.
Why it matters
For people who spend much of their day in business systems, flow translates directly into productivity and job satisfaction. Every slow response, unexpected pop-up, forced context switch, or confusing step pulls people out of focus and costs time to recover.
Research on workplace interruptions found that people compensate by working faster, but at the cost of higher stress, frustration, and effort.[3]
Key takeaways
- Make goals and next steps obvious. People should never wonder what to do next.
- Respond quickly. Delays break concentration; aim for responses that feel immediate (see Doherty Threshold).[4]
- Minimize interruptions. Avoid unnecessary pop-ups, confirmations, and notifications during focused tasks.
- Keep people in context. Avoid forcing them to switch screens, systems, or windows to complete a single task.
- Support growing skill. Provide guidance for newcomers and shortcuts for experts so the challenge stays balanced as people gain experience.
- Preserve progress. Saved drafts and restored state help people return to focus after inevitable interruptions.
In practice
Common patterns in business applications, portals, and internal tools:
Designs that work with it | Designs that work against it |
|---|---|
Inline editing and actions that keep people on the same screen. | Every edit opens a new page or modal and returns to the top of a list. |
Fast responses with clear progress for longer operations. | Frequent unexplained pauses during routine actions. |
Keyboard shortcuts and bulk actions for frequent tasks. | Repetitive clicks required for each item in a large batch. |
Notifications batched or deferred during focused work. | Interruptive pop-ups for non-urgent messages. |
Work-in-progress saved automatically. | Session timeouts that discard unsaved work. |
Questions to ask in a design review
- For the most frequent tasks, how many times are people interrupted or forced to switch context?
- Is it always clear what to do next?
- How does the experience differ for a first-time user and a daily expert?
- What happens to someone’s work if they are interrupted?
Origin
Hungarian-American psychologist Mihaly Csikszentmihalyi began studying the experience in the 1960s and 1970s, interviewing artists, athletes, surgeons, and others who described being “in the flow.” He introduced the concept in Beyond Boredom and Anxiety (1975) and popularized it in Flow: The Psychology of Optimal Experience (1990).[1][5]
Flow has since influenced fields from education and sports to game design and user experience, where it informs how products balance challenge and guidance and protect focus.[2][6]
Related concepts
- Doherty Threshold — fast responses keep people engaged
- Feedback — immediate feedback is a condition for flow
- Goal-Gradient Effect — visible progress increases motivation
- Selective Attention — deep focus filters out distractions
- Zeigarnik Effect — interrupted tasks stay on people’s minds
- Cognitive Load — excess effort pulls people out of flow
References and further reading
- Wikipedia. Flow (Psychology). https://en.wikipedia.org/wiki/Flow_(psychology)
- Yablonski, J. Flow. Laws of UX. https://lawsofux.com/flow/
- Mark, G., Gudith, D., and Klocke, U. (2008). The Cost of Interrupted Work: More Speed and Stress. Proceedings of CHI 2008. https://dl.acm.org/doi/10.1145/1357054.1357072
- Nielsen Norman Group. Response Time Limits. https://www.nngroup.com/articles/response-times-3-important-limits/
- Wikipedia. Mihaly Csikszentmihalyi. https://en.wikipedia.org/wiki/Mihaly_Csikszentmihalyi
- Csikszentmihalyi, M. (2004). Flow, the Secret to Happiness. TED. https://www.ted.com/talks/mihaly_csikszentmihalyi_flow_the_secret_to_happiness
- Yablonski, J. Laws of UX (format inspiration for this series). https://lawsofux.com/