GDnD Wiki

GDnD Wiki

This site is for Ulster University students and staff. Enter the class access password to continue.

Flow

11 min read

Summary

Flow is a psychological state of complete, energised engagement first described by Mihaly Csikszentmihalyi (1990, Flow: The Psychology of Optimal Experience). In this state, self-consciousness disappears, time distorts, and intrinsic motivation is at its peak. Jesse Schell identifies flow as one of the most important psychological concepts for game designers, because games are among the most reliable flow-generating experiences humans have devised.

(Schell, The Art of Game Design, see source-art-of-game-design)

Key ideas

The flow channel

Flow occurs in a narrow band between two failure states:

  • Too easy → boredom. When challenge falls below the player’s skill level, the game becomes trivial. Engagement drops.
  • Too hard → anxiety. When challenge exceeds the player’s skill level, they feel helpless or frustrated. Engagement collapses.

The flow channel is the zone between these extremes where challenge is appropriately matched to skill. The channel is narrow — small deviations in either direction break the state.

Anxiety
  ↑
  │         ╱ Flow channel
  │        ╱
  │       ╱
  │      ╱
  │─────╱─────────→ Boredom
  └──────────────→ Skill

Flow is a moving target

The flow channel is not a fixed location — it shifts as the player’s skill increases. A mechanic that was appropriately challenging in hour one becomes trivially easy in hour ten. Maintaining flow requires continuously escalating challenge as skill grows.

This is why difficulty scaling, new mechanics, and escalating enemy behaviour are not optional polish — they are the mechanism by which a game stays in the flow channel over time.

Autotelic experience

Csikszentmihalyi calls flow “autotelic” — intrinsically motivated, pursued for its own sake rather than for external reward. A player in flow is not playing for a prize; they are playing because the activity itself is completely absorbing. This is the psychological state most associated with deep player investment and long play sessions.

Conditions for flow (Csikszentmihalyi’s list)

  1. Goals are clear
  2. Progress is measurable
  3. Feedback is immediate and unambiguous
  4. Control feels possible
  5. Distraction is minimised
  6. Self-consciousness is reduced
  7. Time perception distorts

Games can be designed to hit all seven conditions deliberately.

In practice

Difficulty scaling approaches:

  • Explicit difficulty settings — player-selected (Beginner/Normal/Hard). Simple, but removes designer control over pacing.
  • Dynamic difficulty adjustment (DDA) — system monitors performance and scales challenge accordingly. Can feel manipulative if detected. (CRE342 Lectures, see source-cre342-lectures)
  • Rubber-band mechanics — opponents or world respond to player success/failure (common in racing games). Maintains competition; risks feeling unfair.
  • Layered complexity — introduce new mechanics over time to sustain challenge as earlier mechanics are mastered. Schell’s preferred approach.

In Unity: Practical levers for flow maintenance include enemy health/damage scaling, spawn rate adjustment, projectile speed, time limits, and gating new abilities behind progression milestones.

Lens #18 (Flow): Schell’s lens asks:

  • Does my game have clear goals at every moment?
  • Is there a steady stream of gradually increasing challenges?
  • Are players at my target skill level experiencing flow, or frustration, or boredom?

Flow exhaustion and the “powerful/awesome” border (Bond)

Bond (Ch. 8) adds a critical refinement not present in Schell’s account:

Flow beyond 15–20 minutes is exhausting. Sustained peak engagement is cognitively demanding. Players need breaks from the flow channel to recover — periods of lower challenge where they can reflect on what they have accomplished and how much their skill has grown.

Bond identifies a “powerful/awesome” border between the flow channel and boredom: a zone where the challenge is below the player’s current skill level, but not so far below that it feels trivial. In this zone, the player experiences the feeling of being competent and powerful — a pleasurable contrast to the intensity of flow.

God of War (2005) is cited as a design example of this well. The game alternates intense combat sequences (flow) with traversal and environmental sections (powerful/awesome border), giving the player regular “power trips” that let them appreciate their combat mastery before returning to challenge.

Design implication: Do not design for continuous flow. Design a rhythm of flow and recovery. The recovery phases are not wasted time — they are when the player integrates their skill growth and builds investment in their character or progress.

(Bond, Introduction to Game Design, Prototyping, and Development, see source-introduction-game-design-prototyping)

Koster’s parallel: boredom as mastery (Theory of Fun, 2005)

Koster provides a cognitive underpinning for why the flow channel works. His framework is independently arrived at but structurally parallel:

  • Fun = learning new patterns. The brain rewards pattern recognition and internalisation with endorphins.
  • Boredom = mastery. When a game has been fully “chunked” (all patterns internalised), it no longer teaches, and boredom follows.
  • The six boredom failure modes all map onto positions outside the flow channel: too easy (challenge far below skill), too hard (challenge far above skill), wrong depth (player not interested in the pattern type), wrong pacing.

Where Csikszentmihalyi describes the experiential state (engagement vs. anxiety vs. boredom), Koster describes the cognitive mechanism (pattern learning vs. pattern exhaustion). Both converge on the same design implication: the game’s pattern complexity must track the player’s growing competence.

“Boredom is always the signal to let you know you have failed.” — Koster (A Theory of Fun, Ch. 3, see source-theory-of-fun)

For Koster’s full taxonomy of boredom failure modes, see fun-as-learning.

(Koster, A Theory of Fun, see source-theory-of-fun)

Evidence

“The flow channel is a delicate thing — if the challenge is too low, players become bored; if it is too high, they become anxious. The designer must carefully keep players in the channel through the whole play experience.” — paraphrase of Schell (Lens #18, source-art-of-game-design)

Schell notes that game designers had been creating flow-inducing experiences for decades before Csikszentmihalyi named the concept — the theory is a vocabulary for what skilled designers already intuited.

Implications

  • Tutorials matter: The hardest moment for flow is the beginning. Players have near-zero skill; the challenge must be near-zero too. A bad tutorial breaks flow before the game starts.
  • Failure should teach, not punish. Repeated failure means the challenge exceeds skill — but if the player can see why they failed and how to improve, the frustration converts to engagement. Failure that teaches is in the flow channel; failure that baffles is not.
  • Mastery needs to be honoured. When a player fully masters a mechanic, that mechanic must be retired or escalated. Continuing to challenge players with something they have mastered produces the boredom end of the spectrum.

Sellers’ additions: Yerkes-Dodson and structural coupling

Sellers (Advanced Game Design, 2018) provides two contributions that extend the flow framework with physiological grounding:

Yerkes-Dodson arousal curve

The Yerkes-Dodson law (1908) describes the relationship between arousal and performance as an inverted-U: performance peaks at moderate arousal, drops at both extremes. Sellers argues this is the neurophysiological substrate of the flow channel — the two frameworks are describing the same phenomenon at different levels of abstraction.

Performance
    ↑
    │       ╭─────────╮
    │      ╱           ╲
    │     ╱    FLOW      ╲
    │    ╱                ╲
    └──────────────────────→ Arousal
       (boredom)          (panic)

What this adds to Csikszentmihalyi’s model: The flow channel is not arbitrary — it corresponds to an optimal neurochemical state (dopamine and norepinephrine in the productive range, below the cortisol-dominated stress response). Designing for flow is designing for optimal neurochemical arousal. See neurochemical-engagement for the full neurochemical model.

Design implication: Flow is not just “right difficulty” — it is “right arousal level.” Monotony breaks flow from below (insufficient dopamine stimulus); overwhelming challenge breaks flow from above (cortisol-dominated stress response). Novelty, not just difficulty, is a lever for arousal.

Structural coupling

Sellers draws on Maturana and Varela’s (1987) concept of structural coupling — two systems that interact closely over time, each adapting to the other’s structure — to explain why well-designed games sustain flow:

“A game and player also form a structurally coupled relationship. If the game is systemically designed, it will have defined a sufficiently broad and diverse state-space that it can adapt to the player as the player adapts to it.” — Sellers, Ch. 2

Flow requires that the game continually provide an appropriate challenge as the player’s skill grows. In a structurally coupled system, this happens systemically rather than through explicit difficulty adjustment: the game’s state-space is broad enough that as the player masters lower-level patterns, higher-level patterns and challenges emerge naturally from the system.

This is the systemic design argument for second-order-design: a game with a rich enough state-space adapts to the player without the designer having to author each difficulty curve explicitly. Systems depth is a flow-sustaining mechanism.

(Sellers, Advanced Game Design, see source-advanced-game-design)

Hiwiller: the Fundamental Game Design Directive and casual/hardcore positioning

Hiwiller frames flow not merely as a psychological state to aim for, but as the design directive itself:

“Keep players making interesting decisions.” — Hiwiller, Ch. 9

More specifically, his “Fundamental Game Design Directive” is to keep players in a state where their skill level is a close match for the level of challenge the game presents — i.e. in the flow channel. Every other design technique — difficulty scaling, tutorial design, dynamic difficulty adjustment, new mechanic introduction — is in service of this directive.

Casual vs hardcore positioning

Hiwiller adds a practical calibration point not explicit in Schell or Bond. Different player audiences sit in different positions on the challenge/skill grid:

  • Casual players tend to require lower challenge levels relative to their skill — they become frustrated more easily. Casual games err toward insufficient challenge for their skill level.
  • Hardcore players demand higher challenge levels relative to their skill — they become bored more easily. Hardcore games err toward excessive challenge.

A game designed for one audience can actively drive away the other. This is not a failure of design but a deliberate positioning decision — understanding your target audience’s position on this axis is prerequisite to designing a flow experience for them.

Jenova Chen’s flOw and dynamic difficulty adjustment

Game designer Jenova Chen’s MFA thesis (2007, Flow in Games) applied Csikszentmihalyi’s framework directly to game design, proposing that the conditions for flow and the conditions players describe as “fun” are the same. His research game flOw (2006) implements dynamic difficulty adjustment (DDA): the game detects increasing player ability and adjusts challenge continuously, aiming to keep the player in the flow channel at all times.

Games have structurally incorporated this principle for decades through explicit difficulty curves — Super Mario Bros.’ World 1-1 provides near-zero challenge for near-zero skill (teaching basic controls through safe experimentation), escalating to complex multi-hazard environments in later worlds that require mastered skills to navigate.

Modern AAA studios apply this with data: Microsoft’s research team produced visualisation tools for Bungie’s Halo 3, mapping where players spent more time or used more ammunition — revealing bottlenecks where challenge was too high, and voids where challenge was insufficient.

(Hiwiller, Players Making Decisions, Ch. 9, see source-players-making-decisions)

Open questions

  • Dynamic difficulty adjustment systems have been criticised for feeling artificial or patronising when detected. Is transparent DDA (where the player knows the system is adjusting) better than opaque DDA?
  • Flow is an individual psychological state — a challenge level that keeps one player in flow will bore or frustrate another. How do designers balance flow across a diverse player population?
  • Some games deliberately break flow for artistic or subversive effect (e.g. Undertale, Doki Doki Literature Club). Is this a violation of flow principles, or a deliberate use of flow violation as a design tool?
  • The Yerkes-Dodson curve predicts a single optimal arousal peak. But players report enjoying both very low-arousal (relaxing games, walking simulators) and very high-arousal (horror, bullet hell) experiences. Does the model need to accommodate this range?

Graph View

Backlinks