What Grim Fandango’s 1996 Puzzle Document Teaches About Game Design

Open the Grim Fandango puzzle document and the first surprise is not a puzzle at all. It is the architecture beneath the jokes. Dated April 30, 1996, the document moves from a cast list to a location map, then to cut-scene beats and detailed solutions. It reads like a screenplay, a level plan, and a production checklist sharing one desk.

That mixture makes the document valuable to anyone studying adventure game design. A game design document, often shortened to GDD, is a shared plan that explains how a game should work before and during production. The Grim Fandango puzzle document is especially revealing because it treats puzzle order as a designed experience. What can a 1996 game design document teach us about puzzle progression? Quite a lot: freedom works best when the player has first learned the rules that make freedom meaningful.

A blueprint, not a walkthrough

A walkthrough tells the player what to do. A design document tells the development team what the player must be able to do, why that action belongs in the story, and what needs to exist for the solution to function.

The Year One structure uses a dependency graph, a map showing which tasks unlock or depend on other tasks. Boxes such as Hire Driver, Fake Work Order, and Reap Soul are not merely a list of scenes. They describe a chain of prerequisites. Before Manny can leave in the company car, he needs a driver. Before the car can be modified, he needs authorization. Before the next story problem can begin, the earlier obstacle has to be resolved.

That distinction matters during production. An arrow between two puzzles implies more than plot order. It may require a location, an object, a conversation, an animation, and a particular game state. A state is the current condition of the world: who is available, which door is open, what Manny is carrying, and which conversations have already happened. Mapping those dependencies early helps a team find missing pieces before they become expensive bugs.

The first puzzles teach the game’s verbs

The document begins with a tightly controlled sequence. Linear progression means the player solves one problem, then receives the next. That structure can sound restrictive, but early restrictions are useful because they teach the game’s basic verbs without turning the opening into a lecture.

Manny’s first obstacle is finding a driver. Glottis is not a random key hidden in a room; he is a mechanic who desperately wants to drive, yet has been excluded because his enormous body does not fit the company car. Manny’s solution involves turning on a shop fan and reminding Glottis what it feels like to have wind rushing past him. The puzzle teaches the player to inspect a character’s desires and connect them to the environment.

The fake work order builds on that lesson. Manny cannot get permission from Don Copal directly, so he observes the office, discovers a rope made from neckties, reaches the boss’s room, and interferes with a machine that plays prerecorded responses. The office becomes an interface the player can manipulate. No tutorial box needs to say, “Look for an alternate route into the room.” The environment demonstrates that possibility.

Together, these puzzles form gentle onboarding. Onboarding is the early process of teaching players the actions and expectations they will use for the rest of the game. The sequence introduces talking, observing, travelling, using objects, and changing the world, one obstacle at a time.

Nonlinearity arrives as a ramp

The document then makes its most important structural move: it deliberately increases nonlinearity. Nonlinearity means the player has more than one valid order in which to solve problems. Grim Fandango does not throw every puzzle into a heap at the beginning. It opens the gates in stages.

The difference can be sketched like this:

Linear:
A → B → C

Parallel:
A ─┐
B ─┼→ D
C ─┘

Any order:
A, B, and C can be solved in any order → D

The document describes early puzzles as linear, then introduces groups that can be worked on side by side, and later allows several tasks to be completed in any order. Those are different experiences, even though all three may eventually lead to the same story beat.

They also create different technical demands. In a linear chain, designers can predict the player’s state. In a parallel section, each branch may alter an object, a conversation, or a character, so every other branch must still make sense afterward. The rising nonlinearity is therefore not only a pacing decision. It is also a testing plan.

The map prevents puzzle soup

The Year One location layout lists offices, hallways, the garage, a roof, a basement, a street, and the route toward the petrified forest. That map is more than background information. It shows how the player will circulate through the world.

Backtracking means returning to an earlier location after gaining a new item or piece of information. Adventure games depend on backtracking, but too much unexplained travel can make a puzzle feel like a scavenger hunt through disconnected rooms. A spatial map lets designers notice when the player is crossing the same territory repeatedly, when a new shortcut is needed, or when two puzzles are competing for attention in the same space.

The map also connects story and mechanics. Manny’s route through the Department of Death is not an abstract sequence of menus. It is a physical journey through offices, service areas, rooftops, and streets. The player’s understanding of the institution grows because the player moves through its machinery.

Character logic becomes a hint system

One of the document’s strongest ideas is that characters can explain puzzle solutions before the player recognizes them as clues. Glottis’s personality, job, body, and frustration all point toward the solution to the driver puzzle. His problem is not an arbitrary lock placed in front of Manny. It is a consequence of who Glottis is.

This is where affordance becomes useful. An affordance is a visible clue about what an object or character can do. A fan affords movement and wind. A rope affords climbing. A machine with prerecorded responses affords manipulation once the player notices how it works.

A diegetic clue, meaning a clue that exists inside the story world, often feels more satisfying than a generic hint prompt. The player is not being told that an answer is nearby. The world is quietly explaining itself. The document’s strange names, from balloon twisters to bone beavers, also give the team memorable hooks for the spaces and problems they are building.

The lasting lesson for game designers

The document is full of jokes, character sketches, map labels, and puzzle explanations. It is not polished like a finished manual, and that is part of its value. A working design document does not need to sound elegant. It needs to give a team a shared vocabulary and a reliable picture of the player’s journey.

Modern designers can borrow several ideas from its structure:

• Draw dependencies before writing every line of dialogue.
• Keep the earliest puzzles narrow enough to teach the game’s rules.
• Add parallel objectives only after players understand the basic verbs.
• Make locked doors and blocked routes follow from character or world logic.
• Use a location map to check pacing, backtracking, and player attention.

The most valuable thing in the Grim Fandango puzzle document is not a lost character or a clever solution. It is the shape of the journey: constraint first, competence next, choice after. Puzzle design is not a pile of riddles. It is the craft of deciding when the player knows enough to be trusted with a wider world.