Engagement-Led Design
Summary
Engagement-Led Design is Oscar Clark’s framework for structuring a game’s experience so that players are continuously motivated to start, continue, and return. The framework — developed in Games as a Service (Clark, 2014, see source-games-as-a-service) — borrows its vocabulary from serial narrative (TV drama, film, comic books) and applies it to game session structure. Four core techniques are named: Bond Opening, Flash Gordon Cliffhanger, Never Seen Star Wars, and Columbo Twist. Together they address the beginning of a session, the end of a session, the long arc across many sessions, and the structural surprise that deepens engagement.
The framework does not replace mechanics design — it describes when and how to deliver the emotional beats that sustain the relationship between player and game across the player-lifecycle.
Key ideas
1. Bond Opening
Named after the pre-title sequence convention in James Bond films: throw the player into high action and clear reward before any explanation. The Bond Opening establishes:
- Immediate agency — the player is doing something, not watching.
- An early win — a clear success state within the first 60–90 seconds that proves the core mechanic can be fun.
- Emotional investment — a moment, character, or mystery the player wants to follow up on.
Clark argues the first minute of play is the critical onboarding window (Clark, Games as a Service, see source-games-as-a-service). If a player achieves no meaningful reward in the first minute — through bad pacing, excessive tutorial text, or slow environmental storytelling — they will churn before forming any investment.
Anti-pattern: Long unskippable tutorials, full story exposition before any action, or complex menus before the first gameplay moment all violate the Bond Opening principle.
2. Flash Gordon Cliffhanger
Named after the episodic serial convention of ending every episode on a cliffhanger that made the next episode feel essential. The goal is to ensure that every session ends with the player wanting more — not feeling satisfied and complete.
Techniques:
- End the session mid-objective (a quest incomplete, an enemy almost defeated).
- Use a timed mechanic that the player wants to return to collect (resources that accumulate offline, energy that has refilled).
- Present a choice or reveal at session close that creates anticipation: “What happens if I pick option B?”
- Use notification systems to deliver the cliffhanger resolution even when the player is not actively playing.
Clark notes that the challenge here is counterintuitive: satisfaction is the enemy of return. A player who finishes a session feeling fully resolved and satisfied has no pull back to the game. The Flash Gordon Cliffhanger deliberately leaves tension unresolved. This must be distinguished from frustration — the player should feel excited about what is coming, not punished for stopping (Clark, Games as a Service, see source-games-as-a-service).
The technique connects to rhythm-of-play and the Rhythm of Play concept: the game’s pacing should oscillate between tension and resolution, with each session designed to end in a tension state.
3. Never Seen Star Wars
Named for the experience of someone who has never seen Star Wars encountering repeated references to it in culture — there is a growing awareness of something they are missing, a desire to catch up, to be part of the shared experience. Clark uses this as a model for foreshadowing and aspiration within a game (Clark, Games as a Service, see source-games-as-a-service).
The technique involves:
- Showing players content or possibilities they cannot yet access, in order to build desire.
- Letting high-level or experienced players be visible to newer players — their achievements, items, and status serve as a long-term aspiration.
- Using narrative hooks that are referenced early but only resolved much later (Chekhov’s gun applied to engagement arcs).
This technique is closely related to the foreshadowing mechanic in game-loops and to the aspirational tier of f2p-monetisation-design (showing premium items to free players who can see but not yet own them).
The risk: if the gap between “seeing” and “obtaining” is too large, the never-seen-Star-Wars effect turns into helplessness or resentment — the player concludes the aspiration is not for them. Balance requires that the path to the desired state is visible, achievable, and clearly rewarded as it is progressed.
4. Columbo Twist
Named for the TV detective show’s structural convention: the audience knows who committed the crime from the start — the interest comes from how Columbo will figure it out. The Columbo Twist in games is the moment where the player’s understanding of the game is reframed — they discover that what they thought was the objective was only part of the picture (Clark, Games as a Service, see source-games-as-a-service).
In practice this manifests as:
- A late-game reveal that recontextualises earlier events (used in narrative games).
- An unlocked “true game” that becomes visible only after the player has mastered the introductory layer — the metagame that was always present but not initially legible.
- The moment when a player stops playing the game the designer intended and starts playing their own strategy within the game’s systems.
The Columbo Twist is the bridge between the Engaging and the deeper layers of engagement. It is not a single moment but a structural principle: design so that understanding the game keeps deepening the longer a player engages with it. This is closely related to the concept of the metagame in Clark’s Anatomy of Play model.
The “so-what” question
Clark returns throughout the book to the question “so what?” as a design test for each of these techniques (Clark, Games as a Service, see source-games-as-a-service). For every opening beat, every session-end hook, every aspirational display: if a player asks “so what?” and you cannot answer with a clear emotional or mechanical reason to continue, the technique is not working.
In practice
These techniques apply at three scales:
| Scale | Bond Opening | Flash Gordon Cliffhanger | Never Seen Star Wars | Columbo Twist |
|---|---|---|---|---|
| First session | First 60–90 seconds of play | End of first session hook | Early glimpse of end-game content | Hint that there is a deeper layer |
| Per session | Quick re-engagement reward for returning | Unresolved tension at session close | Progress towards visible long-term goal | A mechanic interaction that wasn’t obvious |
| Long-term arc | The game’s opening act (first 1–3 days) | Season/event cadence | Long-term meta-progression | True game reveal (prestige system, NG+) |
Unity implementation considerations:
- Bond Opening: the first scene loaded should be the game scene, not a menu. Use
SceneManager.LoadSceneto go directly into a short contextual gameplay moment before showing the main menu. - Flash Gordon Cliffhanger: an
OnApplicationPause/OnApplicationQuithook can record the player’s in-progress state and trigger a scheduled local notification for return (Unity Notifications package). - Never Seen Star Wars: locked UI elements with preview thumbnails (shown but non-interactable) give players a visual aspiration map. A progression unlock system that reveals the existence of content before making it accessible is the standard implementation.
- Columbo Twist: this is a design and narrative architecture problem, not a code problem — plan the metagame reveal during high-level game design, not during implementation.
Evidence
Clark draws on serial TV drama (Bond, Flash Gordon, Columbo, Doctor Who, Dallas) and film structure as analogies throughout this chapter (Clark, Games as a Service, see source-games-as-a-service). The techniques are practitioner-derived from Clark’s production experience and are not presented as empirically validated experimental findings. The underlying psychology — variable reward schedules, anticipation, goal-gradient effects — has substantial support in behavioural psychology literature (Skinner, Kahneman referenced throughout Games as a Service).
Notable game examples cited: Assassin’s Creed (Bond Opening through historical narrative hook), Plants vs Zombies 2 (Never Seen Star Wars for locked worlds), The Walking Dead (Columbo Twist through episodic revelation), Candy Crush Saga (Flash Gordon Cliffhanger through energy mechanics and level cliffhangers).
Implications
- Onboarding redesigns should audit the first 60 seconds of play against the Bond Opening checklist before addressing any other retention issue.
- Session design should explicitly plan both the entry state and the exit state of every session — not just the middle.
- The relationship between Flash Gordon Cliffhanger and dark patterns is real — using guilt, coercion, or false urgency to manufacture the cliffhanger effect crosses into manipulative design. The tension should come from genuine desire, not manufactured anxiety (see dark-patterns).
- Columbo Twist is why progression systems succeed — the moment a player discovers the prestige system, the achievement hunting layer, or the min-maxing meta, they effectively restart their engagement arc at a new level of depth.
Open questions
- How do these narrative techniques transfer to games with very short average session lengths (under 2 minutes, common in hypercasual)? The Flash Gordon Cliffhanger seems structurally difficult when the session itself is shorter than the setup time for a cliffhanger.
- The Never Seen Star Wars model may conflict with accessibility principles — is there a version that delivers aspirational pull without making locked content feel exclusionary?
- Does the Columbo Twist model apply to games designed for a single playthrough (narrative adventure, walking simulator) rather than ongoing service design?