An achievement is a formal record that a game has recognized a specific action. It sits in a profile, a trophy list, or a platform overlay. An experience is the unrecorded residue of play: the failed run that taught you a route, the quiet hour spent learning a system, the moment a mechanic clicked. Game design has spent two decades blurring these categories. The result is a player base that often knows what it has collected but cannot say what it has learned. This article examines how achievement systems shape play, why they reward completion over comprehension, and what designers lose when they treat a checklist as a substitute for a memory.
How Achievement Systems Became the Default Layer
Microsoft standardized achievements on the Xbox 360 in 2005. Sony and Valve followed with trophies and Steam achievements. Nintendo held out longer, then introduced its own version. The pattern is now so common that a game without a meta-progress layer can feel incomplete. Achievements are cheap to implement, easy to market, and useful for platform retention. They also create a second scoring system that runs parallel to the game’s own rules.
The design logic is simple. A player performs an action. The system detects the action. A notification appears. A number increases. The player feels a small spike of recognition. Over time, that spike becomes the reason to continue. The game’s internal goals—survive, solve, explore—become secondary to the external goal of filling a list.
The Checklist Replaces the Question
Consider a game like Hollow Knight. Its world is built around incomplete information. The player stumbles into areas without knowing what they will find. The map is a tool, not a guide. The game’s achievements, however, list specific tasks: defeat a certain boss, collect a certain number of charms, finish the game in under five hours. A player who opens the achievement list before playing has already been told what the game contains. The mystery is reduced to a set of boxes.
This is not a flaw unique to Hollow Knight. It is a structural property of achievement design. The list must be legible. It must name its targets. In doing so, it converts exploration into errands. The player is no longer asking, “What is over there?” but “Which box does that area check?” The difference is subtle in the moment and large in the aggregate.
The Speedrun Achievement as a Case Study
Speedrun achievements are the clearest example. A game like Celeste asks the player to finish a chapter quickly. The intended experience of Celeste is about persistence, failure, and learning the movement system. The speedrun achievement reframes that experience as a time trial. The player stops experimenting and starts optimizing. The game’s own advice—”be proud of your death count”—is contradicted by a reward for minimizing attempts.
Some players enjoy this. The achievement gives them a reason to master the mechanics. But the mastery is now measured by a clock, not by understanding. A player can finish a chapter quickly by copying a route from a video. They have collected the achievement. They have not necessarily learned why the route works. The experience has been replaced by a performance of experience.
The Profile as a Public Ledger
Achievements are social objects. They appear on profiles, friend feeds, and comparison sites. This creates a pressure to perform completion. A player with 12% of a game’s achievements may feel that they have not really played it, even if they spent twenty hours inside its world. The percentage becomes a proxy for legitimacy.
This pressure is not neutral. It changes which games players choose. A long, slow game with few achievements may be skipped in favor of a shorter game with a dense list. A game with missable achievements may be played with a guide open, because the player fears locking themselves out of a trophy. The guide becomes the primary interface. The game becomes a series of instructions to follow.
Missable Achievements and the Death of Spontaneity
Missable achievements are the most direct attack on unplanned play. A game like Persona 5 Royal ties achievements to specific social links, dates, and dialogue choices. A player who wants the platinum trophy must follow a schedule. The game’s calendar system, which is designed to create tension between competing activities, becomes a spreadsheet. The player is no longer making choices. They are executing a plan written by someone else.
The irony is that Persona 5 Royal is a game about the value of time. Its story repeatedly asks the player to consider what matters. The achievement system quietly tells the player that what matters is a list of tasks. The two messages cannot be reconciled. The player must either ignore the achievements or ignore the game’s themes.
What Achievements Measure, and What They Miss
Achievements measure discrete, detectable events. A boss dies. A collectible is picked up. A level is completed. These events are easy to track. They are also the least interesting part of play. The interesting part is the process: the failed attempts, the improvised solutions, the moments of confusion that resolve into clarity. None of that is recorded.
A player who beats a difficult boss on the first try has a different experience from a player who beats it after fifty tries. The achievement is identical. The profile shows the same icon. The system cannot tell the difference between a struggle and a breeze. It can only record that the boss died.
This is not a technical limitation. It is a design choice. Achievements could be designed to reward process: die ten times to a boss, discover a hidden room without a guide, complete a level using only the basic weapon. Some games do this. But the majority of achievements are completion markers. They reward the end state, not the path.
The Hidden Achievement as a Partial Fix
Hidden achievements are an attempt to preserve mystery. The achievement exists, but its description is obscured until the player unlocks it. This prevents the player from reading the list and learning the game’s secrets. It is a partial fix. The problem is that hidden achievements are still achievements. They still appear on the profile. They still create a completion percentage. A player who wants the full list will eventually look up the hidden requirements. The mystery is delayed, not preserved.
Some games use hidden achievements well. Outer Wilds hides most of its achievements because the game is built on discovery. The player is not supposed to know what they are looking for. But even in Outer Wilds, the achievement list is a map of the game’s secrets. A player who checks the list after finishing the game will see the names of things they missed. The experience of not knowing is over. The list has filled in the blanks.
The Completionist Trap
Completionism is a player behavior, not a game mechanic. It is the drive to see everything, collect everything, and finish everything. Achievement systems feed this drive. They give it a number. A player who would never collect all 900 Korok seeds in The Legend of Zelda: Breath of the Wild might do it for the achievement. The achievement is the excuse. The collection is the work.
The trap is that completionism often outlasts enjoyment. A player who is tired of a game will keep playing because the list is not finished. The game has become a job. The achievement system is the boss. The player is not having fun. They are clearing a backlog.
This is not a moral failing. It is a predictable response to a system designed to exploit the human desire for closure. The achievement list is a set of open loops. The brain wants to close them. The game designer knows this. The platform knows this. The player is the one who pays the cost.
The Difference Between a Goal and a Checklist
A goal is chosen by the player. A checklist is imposed by the system. A player who decides to beat every boss in Dark Souls without leveling up has set a goal. A player who collects every ring in Dark Souls because the achievement list says so is following a checklist. The actions may be identical. The meaning is different.
Good game design creates space for player goals. It gives the player tools and lets them decide what to do. Achievement systems often close that space. They tell the player what to do and reward them for doing it. The player’s own goals become secondary. The system’s goals become primary.
The Platform’s Interest in Your Time
Platforms benefit from achievement systems. A player who is chasing achievements is a player who is logged in. The platform can show that player to advertisers, sell them DLC, and keep them inside the ecosystem. The achievement is a retention tool. It is not a gift to the player. It is a hook.
This is not a conspiracy. It is a business model. Microsoft, Sony, and Valve are companies. They want players to spend time on their platforms. Achievements are a cheap way to encourage that. The player feels a sense of progress. The platform gets engagement. The game designer gets a player who is less likely to quit.
The cost is subtle. A player who is chasing achievements is not necessarily playing the game. They are playing the meta-game. The meta-game is owned by the platform. The player’s time is being spent on a system that has nothing to do with the game’s design. The game is just the field on which the meta-game is played.
What Designers Can Do Instead
The alternative to achievement systems is not to remove all tracking. It is to design tracking that supports the game’s own goals. A game about exploration should track places discovered, not boxes checked. A game about mastery should track techniques learned, not bosses killed. A game about story should track choices made, not endings seen.
Some games already do this. Kentucky Route Zero has no achievements. Its story is the reward. Disco Elysium uses its thought cabinet as a form of internal achievement, but the thoughts are tied to the game’s themes, not to a platform list. Rain World tracks survival, not completion. These games trust the player to find meaning without a number.
The risk is that players will feel lost. A game without achievements can feel aimless. The solution is not to add a checklist. It is to design the game so that its own systems provide direction. A map that fills in as you explore. A journal that records what you have learned. A character who reacts to your choices. These are the experiences that achievements are supposed to represent. They are better when they are part of the game, not a layer on top of it.
The Journal as an Alternative
A well-designed journal is a record of experience, not a checklist. The Longing uses a simple notebook to track the player’s discoveries. The notebook is written in the character’s voice. It does not say “collect 10 mushrooms.” It says “I found a strange mushroom today. It glowed in the dark.” The difference is the difference between a database and a diary.
Journals are harder to design than achievements. They require writing, art, and integration with the game’s systems. They cannot be generated by a platform API. But they create a record that is personal to the player. A player who finishes The Longing has a notebook full of memories. A player who finishes a game with 50 achievements has a list of icons. The notebook is the experience. The list is the receipt.
The Player’s Responsibility
Players are not passive victims of achievement systems. They can turn off notifications. They can ignore the list. They can play a game without checking the achievements first. The problem is that this requires effort. The system is designed to be noticed. The notification pops up. The profile shows the percentage. The friend compares their score.
The player who wants to preserve their experience must actively resist the system. They must decide that the game’s internal goals matter more than the platform’s external goals. This is not easy. It is a skill. It is the same skill required to read a book without checking how many pages are left, or to watch a film without pausing to check the runtime.
The skill is attention. Achievements are a tax on attention. They pull the player out of the game and into the meta-game. The player who can ignore them is the player who can stay inside the experience. That is the player who will remember the game, not the list.
FAQ
Are achievements always bad for game design?
No. Achievements can be useful when they are designed to support the game’s own goals. A game about exploration can use achievements to mark hidden areas. A game about mastery can use achievements to reward difficult techniques. The problem is not the achievement itself. It is the default pattern of using achievements as a completion checklist that runs parallel to the game’s design.
Why do players feel compelled to collect achievements they do not enjoy?
The compulsion comes from a combination of social pressure and the human desire for closure. Achievements are public. They appear on profiles and friend feeds. A low completion percentage can feel like a judgment. The list itself is a set of open loops. The brain wants to close open loops. This is a well-documented psychological pattern, not a personal weakness.
Can a game have achievements and still preserve the experience?
Yes, but it requires careful design. Hidden achievements can delay the spoiler effect. Achievements tied to process rather than completion can reward the right behaviors. The key is to ask what the achievement is teaching the player. If the answer is “check the list,” the achievement is working against the game. If the answer is “notice this detail,” the achievement is working with the game.
What should I do if I want to stop chasing achievements?
Start by turning off achievement notifications. The notification is the trigger. Without it, the achievement is just a line in a menu. Then play a game without opening the achievement list. Let the game’s own systems guide you. If you find yourself bored, ask whether the game is boring or whether you are missing the meta-game. The answer will tell you something about the game’s design.
The Next Step for This Site
This article is the first in a series on how external systems shape play. The next piece will examine the difference between a game’s internal economy and a platform’s external economy, using Destiny 2 and Warframe as case studies. If you have a game whose achievement list changed how you played it, send a note through the contact page. The best examples will be included in a follow-up column on player-submitted design failures.
