Board game design

Board game mechanics, named properly and compared without hand-waving.

This site looks at what worker placement, deck building, area control, engine building and cooperative design actually do at the table. The point is not to crown winners. It is to explain why these mechanisms feel different, where they overlap, and which published games make each one easiest to understand.

Board game components laid out to illustrate worker placement, deck building, area control, engine building and cooperative design
Guide index

Five mechanisms, five distinct design problems.

01

Worker placement

Why blocking matters, why action spaces create tension, and why Agricola, Caylus, Lords of Waterdeep and Viticulture explain the mechanism in different ways.

Read worker placement
02

Deck building

How a weak starting deck turns into a tuned card economy, with Dominion, Star Realms, Clank! and Dune: Imperium showing the main branches.

Read deck building
03

Area control

What makes map pressure meaningful, how timing beats raw expansion, and why Risk, El Grande, Inis and Root are not solving the same map problem.

Read area control
04

Engine building

How small efficiencies snowball into larger turns, and why Splendor, Wingspan, Terraforming Mars and Race for the Galaxy reward planning in very different rhythms.

Read engine building
05

Cooperative design

How shared information, role powers and failure pressure interact, using Pandemic, The Crew, Spirit Island and Hanabi as especially clear reference points.

Read co-op design
What this helps with

Seeing the mechanism underneath the theme.

If two games both say they are about building a city, surviving a crisis or controlling a region, that does not tell you much about how decisions are made. Mechanisms do. Worker placement is about contention over action spaces. Deck building is about changing your probability mix over time. Area control is about influence on a map and the timing of commitment. Engine building is about compounding effects. Cooperative design is about information management and collective planning under pressure.

Those labels are useful, but only up to a point. Many published games mix mechanisms freely. Dune: Imperium is not “just” deck building. It uses cards to place agents into contested spaces. Root is not merely area control either; faction asymmetry changes what presence on the map means from one side to another. The useful question is not whether a game belongs in exactly one box. It is which mechanism is doing the most explanatory work.

Quick frame

Read by function, not by prestige.

AccessClear examples first, hybrids second.
FocusTrade-offs, not rankings or hype.
NamesPublished games used as reference points.
ScopeMechanism behaviour at the table.