
compare three games’ core design elements with evidence from play and argue why one succeeds more fully with its audience.
Instruction
This project asks you to do what professional critics, designers and hiring managers do: look closely at games and explain, with evidence, why they work. The question is simple: which of these three games best achieves what it sets out to do for its audience, and why?
Choosing the games. Pick three that are comparable in some way, perhaps the same genre, the same audience or the same core verb, and at least one of them non-digital. A card game, a phone puzzle game and a console platformer are fine if you can explain what they share. Choose games you can play for at least thirty minutes each and that are appropriate for your age and approved by a parent or guardian. Free games are fine; you never need to buy anything.
Evidence from play. Keep an observation log while you play: time stamps, what you did, what happened, what you felt. “12 min: died to the same jump three times; the checkpoint put me back two minutes; frustrated, not challenged” is evidence. “The controls are bad” is not, until you explain what happened. Your log is part of your submission.
The analysis. For each game, identify the formal elements, draw the core loop and name the main aesthetics in MDA terms. Then compare how story, mechanics and visuals each contribute to engagement. The argument is the heart of it: make a claim about which game succeeds most fully, support it with at least three specific pieces of evidence, and answer the strongest case for another game. Success must be defined against the game’s own goals and audience, not your personal favorite genre. A preschool counting game can succeed brilliantly.
Structure. Introduction with your claim; a short profile of each game; a comparison section organized by design element rather than game by game; the counter-argument and your answer; and a conclusion on what the comparison teaches about design. 700-900 words, with the games (title, developer, year, platform) listed at the end.
The presentation. Five minutes, recorded. Show, don’t just tell: a short clip, a screenshot with an annotation or a diagram of the core loop does more than a paragraph.
Building the deck. Use presentation software that is free and needs no account. LibreOffice Impress (free, open source, works offline) is the default route; a slide program already on your computer, such as PowerPoint or Keynote, works the same way. Six to eight slides is enough: title and claim, one slide per game, the comparison, the counter-argument, the conclusion. Import your evidence: take screenshots of digital games with your computer’s screenshot tool, photograph non-digital games on a plain background, save them as .png or .jpg in your project folder, and bring each onto a slide with Insert > Image; then crop it and add one label that says what to notice. Import your core-loop diagram the same way. Keep the working file (.odp or .pptx) in the project folder, and when the deck is final use File > Export as PDF, so anyone can open it exactly as you designed it. Record the talk with free screen-recording software such as OBS Studio, or with a phone pointed at the screen, while you advance the slides.
The career profile. Revise the draft from Lesson 1.4 into a one-page digital poster and add it to your portfolio folder. It is scored for accuracy and sourcing.
📖 Read for this lesson
The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
Which sentence is the strongest evidence in a game analysis?
Write your claim in one sentence and list the three strongest pieces of evidence from your logs that support it. Then write the strongest case for one of the other games in a sentence its fans would accept.
Missouri standard: MM.PRS.1, MM.PRS.4, MM.PRS.6
In LibreOffice Impress, you bring a screenshot saved as a .png onto a slide with Insert > . When the deck is final, you save a copy anyone can open, exactly as designed, with File > Export as .
How confident are you that you can argue with evidence from play why one game succeeds more fully than others?
Unit 1 checkpoint
Do this before you start the task. It covers the whole unit and tells you what to review first.
In a game of marbles, which formal element is the ring drawn on the ground?
Which of Caillois’s kinds of play is a game of make-believe?
In 1976 the Fairchild Channel F, developed by a team led by engineer Jerry , pioneered interchangeable programmable game .
Pressing the up arrow makes Input.get_vector return (0, 1) in Godot 2D.
A sprite moves at 240 px/s. At 60 frames per second (delta ≈ 0.0167 s) it moves about pixels per frame, and it crosses the 1152-pixel window in seconds.
Which backup is a complete, checked copy?
Players in a racing game start blocking the narrow shortcut. In MDA terms this is…
A core loop that is tedious in thirty seconds can usually be rescued by a good story.
Which feedback note follows the course’s critique norms?
A team member builds the combat numbers and progression. Which role?
A salary figure is good evidence only when it comes with the year it describes and the source it came from.
Submit: Game Analysis (700-900 words) + 5-minute recorded presentation + deck (PDF) + career profile
Task: Compare three games (at least one non-digital) using the formal elements, the core loop and MDA, and argue with evidence from your observation logs which one best achieves its goals for its audience. Add your revised career profile to your portfolio.
Submission workflow
- Stage 1 — Plan. The three games with a reason for grouping them, observation logs from at least thirty minutes of play each, and a claim with three pieces of evidence.
- Stage 2 — Self-reviewed draft. Set the draft aside for at least a day, then check every claim for evidence and test your counter-argument with the self-review sheet in the reading; submit the completed sheet and your revision plan. A family member may read the counter-case and tell you whether it sounds fair, if you want an outside view.
- Stage 3 — Final analysis. 700-900 words, organized by design element, with the games listed (title, developer, year, platform) and the logs attached.
- Stage 4 — Presentation. Five minutes, recorded, built in free slide software with at least one imported, annotated screenshot or diagram; submit the deck exported as PDF, and end the recording by answering two questions you expect a viewer to ask. The career profile poster is submitted with it.
How it is scored
| Criterion | What proficient looks like |
|---|---|
| Design analysis (AME.D2) | Formal elements, core loop and MDA applied accurately to all three games. |
| Evidence and judgment (AME.D5.2) | Claim about success judged against each game’s own goals and audience, supported by specific logged evidence. |
| Counter-argument (WHST.9-10.2) | Strongest alternative stated fairly and answered with evidence. |
| Game history and vocabulary (AME.D1) | Accurate terminology; games placed in context of genre and platform. |
| Presentation (SL.9-10.4) | Clear line of reasoning, imported visual evidence, deck exported to PDF, confident answers to two anticipated questions. |
| Career profile (MM.WRS.7) | Accurate, sourced with dates, and tied to the student’s interests. |
Game Analysis Presentation: The Full Brief, Criteria, an Exemplar and the Self-Review Sheet
SLS original; exemplar and log invented for teaching · SLS original
Why this reading. The project asks you to compare three games with evidence and argue one succeeds most fully. This is the full brief, four-level criteria, an exemplar built from three games whose rules are written out in Reading 1.1, an observation-log excerpt, a slide-deck checklist and the self-review sheet. The exemplar and its log are invented for teaching; no real player wrote them.
The task
- Choose three comparable games, at least one non-digital, and play each 30 minutes. Keep a log with time stamps.
- Analyze each: formal elements, core loop, MDA aesthetics.
- Write 700 to 900 words arguing which game best achieves what it sets out to do for its audience, with at least three pieces of evidence and the strongest case for another game.
- Record a five-minute presentation from a slide deck built in free software, with your screenshots imported, and export the deck to PDF. Add your one-page career profile to the portfolio.
Criteria (four levels)
| Beginning | Developing | Proficient | Advanced | |
|---|---|---|---|---|
| Evidence | Opinions only | Some log entries, vague | At least 3 specific log entries tied to design choices | Entries show cause and effect and compare across games |
| Analysis | Elements missing | Elements named | Elements, loop and aesthetics correct for all three | Uses a one-rule change to show why an aesthetic occurs |
| Argument | No claim | Claim, favors own taste | Claim judged against the game’s own audience | Answers the strongest counter-case fairly |
| Communication | Unclear | Understandable | Organized by design element; clean 5-minute talk | Visuals (loop, clip, annotation) carry the argument |
Exemplar excerpt (SLS original, invented)
Claim. For children aged 7 to 9 playing a ten-minute lunch game, mancala succeeds more fully than Nim or tic-tac-toe.
Evidence 1. Tic-tac-toe: at minute 6 my second game ended in a draw again, and after four draws I stopped choosing carefully. Both players can always prevent a loss, so the objective stops producing tension. Evidence 2. Nim (13 stones): at minute 9 my older brother learned to leave 12, and I lost five times in a row. A dominant strategy removed decisions. Evidence 3. Mancala: at minute 14 a chain of two extra turns swung a 5-seed deficit into a lead, and we both said “whoa.” Rules that let planning pay off made surprise possible.
Counter-case. Tic-tac-toe teaches turn-taking in under a minute, which suits the youngest players. I answer that the audience is 7 to 9, old enough to be bored by a solved game.
Observation log excerpt (invented)
| Time | What I did | What happened | How it felt |
|---|---|---|---|
| 6:10 | Blocked the corner | Draw, third in a row | Flat |
| 9:40 | Took 2 from 9 | My brother left me 4 | Trapped; no move helps |
| 14:25 | Sowed pit 5 into store | Extra turn, then capture | Excited; laughed |
Slide-deck checklist
- Built in free software that needs no account (LibreOffice Impress, or a slide program already on your computer).
- Six to eight slides; each game has at least one imported screenshot or photo (.png or .jpg) with one label.
- Core-loop diagram imported as an image.
- Working file (.odp or .pptx) saved in the project folder; final deck exported with File > Export as PDF.
Self-review sheet (Stage 2, after a day away)
- Underline the claim. Does it name the audience?
- Count the evidence entries. Is each specific, with a time or an event?
- Find the counter-case. Would that game’s fans accept how it is stated?
- Is the comparison organized by design element?
- One thing that worked; one thing to change; one question a viewer might ask.