How Jonathan Blow Designs a Puzzle

Jonathan Blow has described the design process behind Braid as less like inventing something arbitrary and more like discovering things that already existed. More ideas came out of development and ended up in the final game than he had deliberately put in at the start.

That idea points to a specific design philosophy used across Braid and The Witness. Rules and puzzles were found through programming and playtesting, rather than imposed from a finished top-down plan.

The designer starts with a mechanic, explores what it naturally implies, and then turns the surprising consequences into puzzles. The game is not filled with arbitrary obstacles. It becomes a series of discoveries about its own little universe.

Braid began with a simple, powerful mechanic: the ability to rewind time by a practically unlimited amount. Once that was coded, new ideas appeared. If every object in the world could be rewound, then some objects could also be made immune to rewinding. A rule was born.

After the rule existed, the important work was to play with it and look for consequences that were not obvious at first. If a moving platform is immune to time manipulation, the player can rewind their own position to a moment when that platform is no longer beneath them. As soon as time resumes, the character falls.

That is not just a gimmick. It is an interesting fact about Braid's world. A puzzle can then become an illustration of that fact, letting the player discover the same strange consequence the designer found while building the system.

The Witness uses a similar process with the mechanic of drawing lines on a grid. During playtesting, Blow noticed that drawing a line often partitions cells. That observation could become a rule.

From there, a puzzle type begins to form. One panel may be easy to solve by looping a path around a section of the grid. A nearly identical panel can then move the exit, making the same solution cut the player off from finishing. The player has to understand the consequence of partitioning, not just trace a line by habit.

In that example, the mechanic inspired a rule, the rule created a consequence, and the consequence became the puzzle. The puzzle came from asking small questions very early in development, not from declaring in advance that the game needed a specific kind of challenge.

This does not mean the designer has nothing to do. The first job is to explore the ramifications of each change as fully as possible.

In The Witness, that means asking how every part of the game can be twisted: the grid, the cells, the line, the environment, and the panel itself. In Braid, it means asking how each rule change affects every object in the game.

When Braid introduces objects that are immune to rewind, the idea is not used once and thrown away. Enemies, keys, doors, clouds, platforms, and even the player character can all be given that property. Each variation tests what the rule means from another angle.

The second job is presentation. The puzzle needs to give the player the best possible setup to discover the interesting fact at its center.

Misdirection can help. In Braid's puzzle Hunt, the player is told to kill all the monsters, and the monsters are arranged so the most obvious order does not work. That failed obvious move is not just a trick. It shows why the real rule matters and stops the player from brute-forcing the answer without understanding it.

Sequences, pairings, and reprisals do similar work. A simple puzzle about unlocking two doors with one key can prepare the player for a more substantial version later. A familiar layout can return in another world with different rules, making the player see how the consequence has changed.

The designer can also subvert expected behavior. In one level, the correct realization is that the player must not use rewind at all. In another, a strange time rule means only one of two gates can be opened. These puzzles are not just asking for steps; they are asking the player to notice what the world is really doing.

The final job is curation. Mechanics, rules, and puzzles need to be cut if they lack surprise, overlap too much with other ideas, or fail to say anything interesting.

Both Braid and The Witness grew out of earlier projects that were shelved because their main mechanics did not create a rich enough space to explore. Blow also removed rules, such as a strange turn-based world in Braid, when their consequences were not surprising or the rule felt contrived.

The interesting twist is that curation does not always mean keeping only what is conventionally fun. Some odd or awkward pieces may stay because they are interesting, surprising, or necessary to make the universe feel complete. A puzzle where a key moves around on its own can be strange, but it may still express a meaningful consequence of the game's rules.

For this style of design, a puzzle is not just a puzzle. It is a communication of an idea from designer to player. Solving it is the player's way of saying, "I understand."

That is different from "I finally figured it out." Many puzzle games lean on arbitrary steps, intricate sequences, red herrings, or obscure mechanisms. The player can eventually win without feeling that the puzzle revealed something coherent.

Braid and The Witness feel fairer because their harder puzzles are usually about understanding the consequences of known mechanics in new layouts, combinations, and setups. The elements are introduced up front. Introductory puzzles teach them quickly. Later puzzles ask the player to see the same rules more deeply.

Many of the puzzles are also compact. They often explore one idea, keep the stage small enough to hold in mind, and avoid unnecessary red herrings or execution-heavy steps. Once the player sees the solution, performing it is usually straightforward.

Solving this kind of puzzle is not like grinding through a Rubik's cube or guessing the answer to a riddle. It feels like seeing something that was there all along. The answer was in front of the player the whole time, if only they knew the right way to look at the world.

That is why the aha moment can feel so strong. It is not just the relief of assembling enough steps or finally guessing what the designer wanted. It feels like the world has become clearer.

The more a puzzle is about something specific and real inside the game's rules, and the less it is about arbitrary challenge, the more meaningful that epiphany becomes. The design process may start with exploration, but the finished puzzle gives that discovery to the player in its cleanest possible form.