Theme vs. mechanics

Designers love to argue about whether theme or mechanics should come first. Theme is what the game is about: trading in the Mediterranean, surviving a zombie outbreak, racing camels. Mechanics are what players actually do: draft cards, place workers, roll and move. Neither answer is wrong, and famous designers sit on both sides.

Starting from theme gives you a compass. If your game is about deep-sea salvage, the theme suggests mechanics: pushing your luck as oxygen runs low, weighing heavy treasure against a slow ascent. When a rules question comes up, you can ask "what would really happen?" and often find the answer.

Starting from mechanics gives you a working engine. You know the core interaction is fun because that is where you began, and you dress it in whatever theme fits best. The risk is a "pasted-on" theme, where the story could be swapped for any other without changing a rule. Players notice, and it makes games harder to teach because nothing behaves the way the story implies.

In practice, strong games converge from both directions. The theme suggests mechanics, the mechanics reshape the theme, and after enough iterations players cannot tell which came first. If a rule fights the story, change one of them until they agree.

Choose between

Option A

Theme

Use this when it supports the experience you want players to have most often.

Option B

mechanics

Use this when the tradeoff creates better decisions for your target players.

Video tutorials

How to Write a Plot for your Story [Writer's Dice - Kickstarter Video]

This is why your board game feels like WORK!

Reference tutorials and tools

Try it in Runner

Put this concept into practice. Build your game visually and playtest it in Tabletop Simulator, no code required.

Open your dashboard