How to Think Like a Game Designer

How to Think Like a Game Designer

What is Design? If you really think about it, design is about how people use things, and how using those things should make them feel. This applies whether you’re talking about any sort of design: graphic, industrial, or, of course, game design.
But games are unique because they’re not just objects to look at or tools to use; they’re systems you interact with. Every rule, every object, every choice shapes how the player acts and, more importantly, how the player feels.
That’s why thinking like a game designer means going beyond. It’s about connecting everything into an experience. And creating one is no easy job, so the best place to begin is with the basics.

Start With a Vision

The first step is having a north star: a feeling or fantasy your game should deliver. It could be “the thrill of the unknown”, “the struggle to survive”, or “push-forward combat.” This vision acts as a compass. It will guide every decision you make and shape every element of your game.
You can also use the three core pillars method, which is a tool many studios (including the God of War team at Santa Monica Studio) use to keep their design vision focused. The idea is to define three short statements, your game’s pillars, that capture the essence of the experience.

Use the MDA Framework

The MDA (standing for Mechanics, Dynamics, and Aesthetics) methodology explains how design changes ripple into player experience:

• Mechanics: The rules, systems, what the buttons do, numbers.
• Dynamics: How those mechanics play out through player behavior.
• Aesthetics: The feelings that the player experiences.

In short, if you want to change the player’s emotional experience (how the game feels), you need to rework the underlying rules (mechanics) and then watch how players’ behavior changes (dynamics). If those new behaviors create the intended emotional response (aesthetics), you’ve made a fantastic job as a game designer.

Prototype, Test, Iterate

The only way to know if a system works is to prototype and put it in front of players. Don’t rely on what they say they want, observe what they do. Behavior reveals truth far more than feedback alone. A feature may sound appealing in theory, but sometimes the design needs to change because it just—doesn’t—work.

Redefine the Problem

Players can say many things, but the underlying problem could be something else entirely, such as pacing, resource scarcity, or encounter design. The designer’s role is to dig deeper and ask: “What is truly causing this emotion in players?” Solving the root problem usually means adjusting a different part of the system than the one players point to.

Try Bold Moves

To see and understand the real impact of your design choices, exaggerate your changes. Double a value, cut it in half, remove a system temporarily, anything that makes the effect undeniable. Once you clearly see the direction, you can refine and fine-tune. Bold experimentation provides clarity that nothing else can ever achieve.

Flip the Design

In Shovel Knight, the developers originally experimented with checkpoints that cost gold to activate. They found this punished less-skilled players who needed checkpoints the most. So instead, they flipped the system: checkpoints were always available, but players could choose to destroy them for extra gold, making the game way more exciting.

Move the Solution Elsewhere

Problems aren’t always solved where they appear. In The Last of Us, players weren’t engaging with weapon upgrades. The team could have simply made upgrades cheaper or more powerful, but that wouldn’t have solved the real issue. Instead, they tied upgrades to workbenches placed in the world, so they would feel connected to exploration and storytelling. Genius.

Solve Multiple Problems at Once

Great design solutions kill two birds with one stone. New Super Mario Bros. Wii introduced “bubble” respawns. Not only did it prevent weaker players from sitting out the fun, it also gave them a way to skip tough parts, helping both difficulty balance and accessibility all at once.

Watch Real Players

Design is about behavior, not intent. Players often say one thing but do another. A designer’s job is to study how they actually play. For example, beginners might consistently struggle with resource management or timing. The right design choice may be to quietly smooth the edges for new players without disrupting the challenge for those skilled players. What matters is preserving the intended feeling while adapting to real, concrete behavior.

Look for Ripple Effects

Every adjustment affects the larger system. Changing the strength of a weapon, the speed of an enemy, or the reward of an action rarely lives in isolation. Thinking like a designer means always asking: what else does this change affect, and how might it cascade through the experience? Sometimes the best solution is not to adjust the same system again, but to rebalance another element entirely.

Work Within Constraints

Budgets and deadlines are part of design. Limitations often push designers to be more creative. Designers can use simple mechanics, minimal assets, or even absence itself to spark tension and variety. A clever workaround can become more memorable than a high-budget solution. We must see constraints not as barriers but opportunities!

Most Importantly: Make It Clear

In the end, good design is good communication. And players should always know these three things: their purpose (what they’re trying to do), their options (what’s interactive), and the rules (what to expect from the world).