Game Mechanics & Systems Thinking

Summary

Joe Baxter Webb explains how systems thinking can help game designers understand what mechanics do and how they combine to create an experience. He distinguishes three related ideas:

• Rules are the underlying logic of a game: “when this happens, then this happens.”
• Mechanics are the actions and goals available to players—the game’s verbs, such as jumping, collecting, attacking, or investigating. The game’s AI or other opposing forces can use mechanics too.
• Systems are larger groups of rules that organize mechanics and the things they act upon. Interfaces and the way the game communicates its rules are part of those systems.

A mechanic’s implementation affects how it feels. Because feel is central to a game’s character, designers should test core interactions early and be willing to make large changes rather than fine-tuning assumptions that may be wrong. Systems can often be faked or mocked up during early prototypes; building complex systems—such as procedural generation—before the game’s core interactions are proven can waste effort.

The video treats a game as a machine designed to produce an experience. Mechanics combine during play to create emotional results, such as fear, excitement, or the satisfaction of solving a puzzle. This perspective can help designers prioritize what the player should feel instead of pursuing realism for its own sake. For small teams in particular, Webb recommends finding satisfying interactions first, then building the setting and presentation around them.

Webb also warns against copying or combining mechanics without understanding their purpose in the original design. A mechanic may depend on other parts of its system: for example, in many deck builders, discarding a hand helps cards cycle through the deck and return in new combinations. Removing that rule can disrupt the larger design. Genres similarly act as familiar packages of mechanics; changing or removing a convention works best when the designer understands what it contributes and provides an effective alternative.

Design and Development Takeaways

• Learn a genre by playing games in it, not only by working in a game engine. Playing develops an understanding of how its conventions create particular experiences.
• When experimenting with a genre, start from a small game you understand, reproduce its structure, add a twist, and evaluate whether the twist works.
• Match a project to the skills and interests of the developer or team. Different studios are better equipped to make different kinds of games.
• Consider gameplay as both the player’s inputs and the context they respond to: levels, scenarios, stories, and other systems. Starting small makes it easier to develop and test those pieces.
• Don’t overlook expressive mechanics—optional actions such as petting an animal, customizing an appearance, or interacting playfully with the environment. They may not help the player win, but can make a game feel distinctive, memorable, and inviting.
• Think about cognitive mechanics as well as button presses. Observing, remembering, judging, and deducing are meaningful player actions, especially in narrative, strategy, and puzzle games.

The video closes by framing its ideas as prompts for design thinking rather than a formula or a list of guaranteed steps.

People, Games, and Sources Mentioned

• Joe Baxter Webb, the presenter.
• Sid Meier, quoted on making large changes when testing a game variable.
• MDA theory, and a 2004 paper discussing mechanics, dynamics, and aesthetic experience.
• Roger Caillois, whose spectrum of play is described as running from ludus (rule-bound play) to paidia (more free-form play); the subtitles render his name unclearly.
• Blood Thief, cited as an example of a stylized game whose decisions are driven by how its mechanics feel.
• Other illustrative examples include deck builders, roguelikes, walking simulators, visual novels, dating sims, strategy games, chess, I Spy, soccer, and board games.