Chapter 4 Exercises: The Player

Exercise 1: Motivation Self-Assessment

Type: Reflective / Analytical
Time: 25-30 minutes
Deliverable: 1-page written analysis

Take the Quantic Foundry Gamer Motivation Profile (free at quantic.games). After receiving your results:

1. Write down your top three and bottom three motivation scores. Note the percentile for each (the survey tells you how your score compares to the broader gaming population).
2. List the last five games you played for at least five hours each. For each game, identify the primary and secondary Quantic Foundry motivations it serves. Use the six-cluster model: Action (Destruction, Excitement), Social (Competition, Community), Mastery (Challenge, Strategy), Achievement (Completion, Power), Immersion (Fantasy, Story), Creativity (Design, Discovery).
3. Compare your profile to your recent play history. Do they align? Are there motivations you score high on that your recent games don't serve? Motivations you score low on that you keep playing anyway? If so, why? What is the game providing that your motivation profile doesn't predict?
4. Identify one motivation in your bottom three and name a critically acclaimed game that primarily serves that motivation. Write three sentences about what the millions of people who love that game are probably experiencing that you are not. Try to describe their experience without condescension --- this is practice in empathy, not judgment.
5. Look at your progressive project's design concept document. Which of your top three motivations does it serve? Be honest: did you design it for your player or for yourself?

What this teaches you: Your motivation profile is not the same as your player's. By making your own biases explicit, you begin to see where your instincts will mislead you as a designer. The gap between your motivations and your target audience's motivations is the gap you need to bridge through research, empathy, and playtesting.

Exercise 2: SDT Diagnosis

Type: Analytical
Time: 30-40 minutes
Deliverable: 1-page written analysis

Choose a game you quit playing before finishing. Not one you disliked from the start --- choose one you wanted to like, that you played for several hours before abandoning. Using Self-Determination Theory, diagnose why you stopped:

1. Autonomy: Did you feel like your choices mattered? Were you railroaded into specific paths? Did the game respect your time and preferences, or did it demand that you play on its terms? Were there moments where you wanted to do something the game wouldn't let you? Did mandatory tutorials, unskippable cutscenes, or forced mechanics undermine your sense of agency?

2. Competence: Was the difficulty appropriate for your skill level? Were you bored (too easy, no growth) or frustrated (too hard, no progress)? Did the game teach its mechanics effectively, or did you feel lost? When you failed, did you understand why you failed? Did you feel yourself getting better over time, or did improvement feel random or invisible?

3. Relatedness: Did you feel connected to anyone --- other players, NPCs, a community, the game world itself? Or were you alone in a way that felt empty rather than peaceful? Did the game give you reasons to care about its characters, or were they interchangeable quest-givers? If it was multiplayer, was the community welcoming or hostile?

Write a one-page analysis. Identify which of the three needs was most poorly served, and propose two specific design changes --- concrete, implementable changes, not vague suggestions --- that would have addressed the problem without fundamentally altering the game's identity.

Stretch: Do the same analysis for a game you loved and finished. What did it do right in SDT terms? Which need did it serve most strongly? Can you identify a moment where each of the three needs was satisfied simultaneously?

Exercise 3: Bartle Breakdown

Type: Analytical
Time: 20-30 minutes
Deliverable: 1-page analysis with feature table

Choose a multiplayer game you have significant experience with (any multiplayer game --- not limited to MMOs). Create a four-row table with the columns: Player Type | What the Game Offers | How Well It's Served (Strong/Moderate/Weak) | Evidence.

For each of Bartle's four types, fill in:

1. Achiever: What progression systems, collectibles, leaderboards, completion targets, and quantifiable goals does the game offer? How much endgame content exists specifically for players who want to "finish everything"?
2. Explorer: What hidden content, system depth, secrets, emergent interactions, and discoverable lore does the game contain? How does the game reward curiosity --- or does it?
3. Socializer: What communication tools, cooperative content, shared spaces, social events, guilds/clans/groups, and relationship-building systems exist? Can a player whose primary reason for logging in is social interaction find enough to do?
4. Killer / Competitor: What PvP systems, ranking ladders, competitive modes, and ways to demonstrate superiority exist? How well-balanced and rewarding is the competitive loop?

After completing the table: - Identify which type the game serves best and which it serves worst. - Describe how the underserved type affects the community. Do those players leave? Complain on forums? Create mods or unofficial content to fill the gap? Adapt their playstyle? - Design one specific feature the game could add to better serve the weakest type without undermining the experience for the strongest type. Explain why this is difficult --- what tension exists between the two types that makes this a genuine design challenge?

Exercise 4: Design for Your Opposite

Type: Design challenge
Time: 40-50 minutes
Deliverable: 1-page game concept

This is the hardest exercise in this chapter. It tests your ability to design empathetically for a player you are not.

Look at your Quantic Foundry results from Exercise 1. Identify the motivation cluster where you scored lowest. Now design a one-page game concept that primarily serves that motivation.

Your concept must include:

• Title and one-sentence pitch (the sentence a player would read on a store page)
• Core mechanic (what does the player do moment-to-moment?)
• Primary player fantasy (what does the player feel?)
• One target persona (a three-paragraph persona following the format from Section 4.7: name/age/context, motivations, frustration triggers)
• Three specific features that serve your target motivation cluster, described concretely enough that another designer could implement them
• One feature you deliberately excluded that you would personally want but that would undermine the target motivation (this is the hardest part --- it requires you to recognize your own bias and override it)

The constraints: you must design something you genuinely believe the target audience would enjoy. Not something ironic. Not something that smuggles your own preferences in through the back door. Not something condescending. If your lowest motivation is Creativity, design a game that creative players would love. If your lowest is Action, design something that adrenaline-seeking players would choose over the ten other action games they could be playing.

What this teaches you: Empathy is a design skill. If you cannot design for a player type you don't share, you will always be limited to designing for yourself. This exercise pushes you outside your comfort zone deliberately. It should feel uncomfortable. That discomfort is the feeling of your design perspective expanding.

Exercise 5: Persona Stress Test

Type: Design thinking
Time: 30-40 minutes
Deliverable: Decision matrix (table with 3 personas x 5 decisions)

Take the three player personas you wrote for the progressive project and stress-test them against five specific design decisions. Create a table with your three personas as columns and the five decisions as rows.

For each cell, write 1-2 sentences about what that persona would prefer and why:

1. Tutorial design: Should the game have a guided step-by-step tutorial, a contextual tutorial (teaching through play with pop-up hints), or no tutorial at all (drop the player in and let them figure it out)? What would each persona prefer? What would each persona find condescending? What would each find confusing?

2. Boss difficulty: Should the mid-game boss take the average player 3 attempts, 10 attempts, or 30 attempts to defeat? For each persona, which number serves their motivation? Which number would cause them to quit?

3. Cutscene duration and frequency: Should story beats be delivered through 30-second in-engine sequences, 3-minute cinematics, or purely through environmental storytelling with no explicit narrative delivery? Which approach serves each persona? Would any of them skip cutscenes?

4. Navigation system: Should the world have an objective marker and minimap system, a hand-drawn in-game map the player must consult, or no map at all (the player navigates by landmarks and memory)? Which approach serves each persona's fantasy? Which would frustrate them?

5. Save system: Should the game auto-save frequently (every room), use manual save points spread across the world, or use a checkpoint system with significant distance between saves? Which system serves each persona's session context and frustration tolerance?

After completing the matrix, highlight the cells where your personas disagree. Each disagreement is a design tension. For each tension, write one sentence about how you would resolve it, given that your primary persona takes priority. Then write one sentence about what you would add (an option, an assist feature, an alternative path) to mitigate the impact on the losing persona.

Exercise 6: Accessibility Audit

Type: Analytical / Experiential
Time: 40-50 minutes
Deliverable: 1.5-page accessibility report

Choose a game you currently have installed. You will play it three times for five minutes each, under three different constraints. Do these sequentially, not simultaneously.

Round 1: No sound. Mute the game entirely (not just music --- all audio). Play for five minutes. As you play, note every moment where you miss information: an off-screen enemy attack you didn't hear, a notification chime you missed, dialogue you couldn't follow, ambient cues (footsteps, environmental audio) that normally guide you. After five minutes, write answers to: Could you still play effectively? What percentage of the game's information was delivered through audio? What substitute (visual indicator, subtitle, haptic feedback) could replace the audio cue?

Round 2: Simulated color blindness. If your display has a grayscale or colorblind simulation mode, enable it. (Many modern monitors and operating systems offer this in accessibility settings. If not, squint and try to evaluate which UI elements depend solely on color.) Play for five minutes. Note: Can you distinguish health bars from mana/energy bars? Can you tell allied indicators from enemy indicators? Can you read the minimap? Are interactive objects visually distinct from non-interactive ones without color? After five minutes, write: What gameplay-relevant information was communicated through color alone? What would need to change?

Round 3: One hand. Play using only your non-dominant hand on the controller or keyboard. (If using a controller, hold it in one hand and see what you can reach.) Play for five minutes. Note: Which actions become impossible? Which buttons can you not reach? How quickly does your hand fatigue? After five minutes, write: What is the minimum number of simultaneous inputs the game requires? Could it be reduced without losing functionality?

For each round, conclude with: - Two accessibility features the game already has (check the settings menu carefully --- many games have options you've never opened) - Two features that are missing - One specific, implementable feature (described concretely) that would address the single biggest barrier you identified

What this teaches you: Accessibility barriers are invisible to players who don't face them. Five minutes of simulated constraint teaches you more about accessible design than any amount of reading about it.

Exercise 7: The Curse of Knowledge Test

Type: Practical / Observational
Time: 30-45 minutes (requires a partner)
Deliverable: 1-page observation report

This exercise requires another person --- a friend, classmate, roommate, or family member who does not play the same games you do. Ideally, someone with limited experience in the genre of the game you choose.

Setup: 1. Choose a game you know extremely well --- something you have played for at least 20 hours. Preferably a game with some complexity (not a simple mobile game). 2. Before the session, write down three things you predict the other person will struggle with. Be specific: "They won't understand the crafting menu," not "they'll find it hard." Also write three things you predict they will figure out easily. 3. Give them the controller or sit them at the keyboard.

During play (15 minutes): - Do not explain anything. Do not say "try pressing X" or "you need to go left." Do not make faces when they do something wrong. Sit on your hands if necessary. - Take notes on: What do they try first? Where do they hesitate? What do they ignore that you consider important? What do they focus on that you consider unimportant? When they get stuck, what do they try before figuring it out (or giving up)?

After play (10-minute interview): - Ask: What was the game about? (Their answer may surprise you.) - Ask: What was confusing? What was clear? - Ask: What did you enjoy? What frustrated you? - Ask: Would you keep playing? Why or why not? - Ask: What did you think you were supposed to do? (Compare this to what you, the expert, know they were supposed to do.)

Write-up: Compare your predictions to reality. Where were you right? Where were you wrong? Identify three specific moments where the Curse of Knowledge created a gap between what you expected them to do and what they actually did. For each moment, explain: What did you know that they didn't? How could the game have communicated that knowledge without your help?

What this teaches you: This is the single most important exercise in this chapter. Watching someone else struggle with something you find obvious is the fastest way to develop empathy for the first-time player experience. Do this exercise again in Chapter 31 when you playtest your own game. The discomfort you feel while sitting silently is the feeling of the Curse of Knowledge being broken.

Exercise 8: Player Fantasy Mapping

Type: Analytical
Time: 25-30 minutes
Deliverable: Completed table with analysis paragraph

Choose five games from different genres. You may use the suggestions below or substitute your own:

For each game, identify and write one sentence for each:

1. The primary player fantasy (power, mastery, exploration, social, expression, relaxation)
2. A secondary player fantasy that the game also serves
3. One specific mechanic that directly delivers the primary fantasy --- not a theme or aesthetic, but a thing the player does that produces the fantasy feeling
4. One specific aesthetic choice (visual design, sound design, music, camera behavior, UI style, or tonal choice) that reinforces the fantasy without being a mechanic
5. One moment where the primary and secondary fantasies reinforce each other (they work together) and one potential moment where they could conflict (they pull in opposite directions)

After completing the table, write a paragraph about your progressive project: What is its primary fantasy? What is its secondary? Can you identify a specific mechanic that delivers the primary fantasy and a specific aesthetic choice that reinforces it? If you cannot answer these questions clearly, your game's identity may need sharpening.

Exercise 9: Demographic Assumption Check

Type: Reflective / Research
Time: 20-25 minutes
Deliverable: Assumption table and reflection paragraph

Without looking anything up, write down your assumptions about the typical player of each of the following five games. For each, note the age range, gender distribution, and experience level you imagine:

• Candy Crush Saga
• Call of Duty: Modern Warfare III
• Animal Crossing: New Horizons
• Fortnite
• The Witcher 3: Wild Hunt

Now research the actual demographic data. Start with the Entertainment Software Association's annual "Essential Facts About the Video Game Industry" report. Supplement with publisher-released data, Newzoo reports, or player surveys specific to each title. (If exact data for a specific title is unavailable, use genre-level data.)

Create a comparison table: Your Assumption vs. Actual Data for each game.

Write a reflection paragraph addressing: - Where were your assumptions most wrong? - What underlying beliefs drove the incorrect guesses? (Be honest --- this is a bias exercise.) - How would designing for the actual audience differ from designing for the audience you imagined? - What does this tell you about the danger of designing for an assumed audience without data?

Exercise 10: The Session Context Exercise

Type: Design thinking
Time: 25-30 minutes
Deliverable: Three brief design documents (one page total)

Design the same core mechanic --- a simple tile-matching puzzle (think Bejeweled or Tetris Attack --- match three or more adjacent tiles of the same type) --- for three different session contexts. The core mechanic stays the same. Everything else adapts.

Context A: The commuter. Plays on a phone for 3-5 minutes on the subway. One hand. Frequent interruptions (their stop is coming). Cannot use sound. May not have internet.

Context B: The evening player. Plays on a console for 60-90 minutes after a long day at work. Full attention. Headphones on. Wants to decompress --- not think hard, not be stressed, but also not be bored.

Context C: The weekend marathoner. Plays on PC for 4-6 hours on a Saturday. Deep focus. Looking for depth, long-term progression, and the kind of engagement that makes you forget to eat lunch.

For each context, specify: - Interruption handling: How should the game handle sudden stops? (Auto-save? Auto-pause? Lose progress? Resume exactly where you left off?) - Progression system: What keeps this player coming back? (Daily rewards? 100-level campaign? Ranked ladder? Unlockable themes and customization? Persistent stats?) - Difficulty curve: How should challenge escalate? (Per-session ramping that resets? Persistent difficulty that increases over days and weeks? Player-chosen difficulty? Adaptive difficulty?) - Session ending: What is the ideal session-ending moment? (Natural stopping point after a set of levels? Cliffhanger that pulls them back? "One more round" hook? Gentle wind-down?) - Monetization hint: How would the business model differ? (Ad-supported? Premium purchase? Season pass? Cosmetic shop? No monetization?)

What this teaches you: The same mechanic can produce radically different experiences depending on session context. Many design decisions that feel like matters of taste ("should the game be hard?", "should there be a story?", "how long should a session be?") are actually driven by when, where, how long, and in what state of mind the player is playing. Session context is not metadata --- it is a primary design input.

Exercise 11: Implicit Contract Analysis

Type: Analytical
Time: 30-35 minutes
Deliverable: 1-page analysis

Play the first 15 minutes of a game you have never played before. (Use a free-to-play game, a demo, a game from a subscription service like Game Pass, or borrow one from a friend. The point is that you have no preconceptions from prior experience.)

During those first 15 minutes, pause every 5 minutes and write down every assumption the game has led you to make about:

1. What genre is this? What kind of game do I think I'm playing?
2. How hard will this be? What skill level does it expect?
3. What is the tone? Serious? Funny? Dark? Whimsical? Atmospheric?
4. What am I supposed to do right now? Is that clear or confusing?
5. Who is this game for? What kind of player would love this?

Then play for another 30 minutes. Pause again and revisit your earlier assumptions: - Which assumptions were confirmed? - Which were subverted? Was the subversion intentional (the game clearly meant to surprise you) or accidental (the game seems confused about its own identity)? - At any point, did you feel betrayed --- not surprised in an interesting way, but genuinely misled about what the game was going to be?

Write a one-page analysis structured around the concept of the implicit contract. What contract did the game's opening establish? Did the game honor that contract? If it violated it, was the violation effective (a creative twist) or damaging (a design failure)? What would you change about the first 15 minutes to set more accurate expectations?

Exercise 12: Community Ethnography

Type: Research / Observational
Time: 45-60 minutes
Deliverable: 1-page community profile

Choose a game with an active online community. Good options include any subreddit with over 100,000 members, an active Discord server, or a forum with daily posts. You need a community large enough to show patterns, not just individual opinions.

Spend 30-45 minutes reading posts, threads, and discussions. Do not post anything --- you are an observer, not a participant. Read at least 30 different posts or threads.

As you read, categorize every post you encounter into one of the following buckets:

• Achievement --- showing off accomplishments, asking how to complete X, sharing progress milestones, requesting help with challenges
• Social connection --- looking for teammates, sharing experiences, organizing community events, celebrating shared moments, guild/clan recruitment
• Creativity / Expression --- sharing builds, designs, screenshots, fan art, custom content, fashion/transmog, island/base tours
• Mastery / Strategy --- strategy discussions, optimization guides, tier lists, build theorycrafting, difficulty debates, speedrun sharing
• Complaints --- negative feedback, frustration posts, "the devs need to fix X" threads, "this ruined the game" declarations
• Other --- memes, off-topic, meta-community, developer communication

Tally the results. Then write a one-page community profile that answers:

1. What is this community's dominant motivation profile? Which Quantic Foundry clusters does the community over-index on?
2. Compare the community's profile to what you would have guessed based on the game's genre and marketing. Are there surprises? Does the community care about things the game's marketing does not emphasize?
3. What are the complaints about? Categorize them using SDT: are players complaining about lack of autonomy, lack of competence satisfaction, or lack of relatedness? Or something else entirely?
4. What does the community create that the game does not provide? (Guides, tier lists, fan art, mods, alternative rules, social events.) These player-created additions reveal unmet needs --- things the community wants that the game does not offer.
5. If you were the game's lead designer reading this community for the first time, what is the single most important insight you would take away? What would you change, and what would you protect?