Flow
Absorbed, effortless concentration occurs when challenge and skill are balanced, and interruptions destroy it.
Definition
Mihaly Csikszentmihalyi's term for a state of complete absorption in an activity, characterised by clear goals, immediate feedback and a balance between the challenge of the task and the skill of the person performing it.
Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.
On this plate
Reach for this when
- Designing professional tools used for long sessions.
- Deciding whether an interruption is justified.
- Setting performance budgets for interactive work.
- Designing a tool people use for long uninterrupted stretches.
Common mistakes
- Using flow to justify engagement-maximising design.
- Interrupting for anything that could be batched.
- Ignoring the skill side, leaving experts with no room to grow.
Conditions the research identifies
- Clear goals, so the person knows what they are trying to achieve at each moment.
- Immediate and unambiguous feedback on progress.
- Challenge matched to skill. Too easy produces boredom, too hard produces anxiety.
- Freedom from interruption.
- A sense of control over the activity.
What this means for tools
The most useful implication is negative: interruption is expensive and most interruptions are optional. Modals, tours, upsell prompts, notification badges and permission requests all break flow, and their cost is far larger than the seconds they occupy.
The positive implications are latency and feedback. Sub-second response keeps the loop tight enough that the tool disappears. This is where the Doherty Threshold and flow meet.
Do
- Batch non-urgent notifications and deliver them at a natural break.
- Keep response times fast enough that the tool stops being noticed.
- Preserve context across interruptions, so returning is cheap.
- Provide accelerators so skill growth has somewhere to go.
Do not
- Interrupt an in-progress task with anything that could wait.
- Use modals for information.
- Reset scroll position, selection or draft state on return.
What interrupts it, and what it costs
| Interruption | Cost |
|---|---|
| A modal that steals focus mid-task | The task state, and the thread of thought |
| A notification unrelated to the work | Attention, plus the recovery time afterwards |
| A wait long enough to switch context | The whole session, often |
| An unexpected layout shift | Trust in the interface for the rest of the session |
| A permission prompt at an arbitrary moment | The task, and usually the permission too |
In practice
- i.
Notification batching
Productivity toolsCollecting non-urgent notifications and delivering them at intervals preserves concentration while still surfacing everything. Users consistently prefer this once they have tried it.
- ii.
Context preserved on return
EditorsRestoring scroll position, selection and undo history when a user returns makes an interruption recoverable. Losing them means the interruption costs far more than its duration.
- iii.
The upsell that arrived mid-sentence
Cost of an interruptionA modal offering an upgrade appeared four minutes into a writing session. It was dismissed in under a second, and the paragraph it interrupted was rewritten twice. The conversion cost more than it was worth.
Local chart
PSY·005 · Region I · Grid B2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
Flow: The Psychology of Optimal Experience
M. Csikszentmihalyi, Harper and Row, 1990
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Explains
The mechanism underneath these entries.
- Flexibility and Efficiency of UseHEUR·007 · Heuristic
- Doherty ThresholdLAW·006 · Law
- Power Law of PracticeLAW·015 · Law
Applied through
Where this shows up as a concrete interface decision.
- Modal DialogCMP·010 · Component
- NotificationsPAT·015 · Pattern
- Optimistic UIPAT·013 · Pattern
Practical example
A worked decision where this was the deciding factor.
- Designing an AI Suggestion Feature People Would UseCASE·010 · Case study
- Reducing Notification Volume Without Losing SignalCASE·007 · Case study
Related concept
Connected closely enough to change how you apply this.
- Cognitive LoadPSY·001 · Psychology
- Selective AttentionPSY·004 · Psychology