Game of Thrones taught me everything I know about game design

I spent six months designing a board game based on my favorite fantasy series. It was terrible. The kind of terrible where playtesters would rather watch paint dry. Then I figured out the trick. Here's what nobody tells you about turning books into games: You're not adapting the story. You're adapting the choices. Let me show you how. --- Step 1: Find the three decisions that define your world Every great story has moments where characters make impossible choices. Those are your game mechanics hiding in plain sight. For Game of Thrones, those decisions are: - Do I trust my family or my ambition? - Do I fight honorably or survive? - Do I sacrifice the few to save the many? Write down three questions your characters constantly face. These become your core mechanics. Practical tip: Don't pick flashy moments. Pick repeated moments. Ned Stark's honor mattered because he chose it every single day, not just once. Common pitfall: Trying to include every major scene from the book. You'll end up with a bloated mess. Three mechanics. That's your limit. --- Step 2: Turn literary character traits into resource systems Here's where most people screw up. They make a character card that says "Tyrion is smart" and give him +2 to some random stat. That's not gameplay. That's a label. Instead, look at what characters control and what they lack. Tyrion controls information but lacks physical power. In your game, that translates to: "You can see hidden cards, but you can't win combat." Daenerys controls dragons but lacks stability. In game terms: "You have overwhelming force once per round, but your position is always fragile." The influence of literary characters on game mechanics is direct: their strengths become your players' tools, their weaknesses become your game's friction points. Practical tip: For each major character, write down exactly one thing they can do that no one else can. Then give them a cost that matches their story flaw. Common pitfall: Making characters too balanced. Real characters have glaring weaknesses. Your game should too. --- Step 3: Create a betrayal mechanic that actually hurts The Red Wedding worked because nobody saw it coming. Your game needs that same tension. Here's the trick: Betrayal only matters if trust has value. Design a phase where players must share resources or information. Make cooperation genuinely beneficial. Then give everyone a hidden objective that eventually conflicts. The moment one player realizes their ally is about to win? That's your Red Wedding. Practical tip: Force temporary alliances through shared threats. A neutral enemy that attacks everyone equally creates real partnerships. And real betrayals. Common pitfall: Making betrayal the only strategy. If everyone stabs everyone immediately, nobody trusts anyone, and the game becomes random chaos. Build trust first. Break it later. --- Step 4: Let the world itself be a player Game of Thrones isn't just about characters. It's about winter coming. About armies marching. About a world that doesn't care about your plans. Your game needs the same. Create a deck of event cards that trigger regardless of player actions. Some help. Some hurt. Some force impossible choices. The key: Events shouldn't feel random. They should feel inevitable. "Winter has arrived" isn't a random card draw. It's a countdown that everyone knows is coming. The question is whether you prepared. Practical tip: Make events predictable in timing but unpredictable in specific effect. Players should know something bad happens every three rounds, but not exactly what. Common pitfall: Events that just give or take resources. That's boring. Good events force players to reconsider their strategy mid-game. --- Step 5: Test with people who never read the source material This is the hard truth. If your game only works for people who love the book, it's not a game. It's a souvenir. Run your prototype with people who've never heard of your IP. Watch their faces. If they're confused, your mechanics aren't clear enough. If they're bored, your choices aren't meaningful enough. Board game design using popular IP works when the IP enhances the gameplay, not when the gameplay depends on the IP. Practical tip: After playtesting, ask one question: "What was the most painful decision you had to make?" If they can answer immediately, your game works. If they hesitate, redesign. Common pitfall: Assuming fans will forgive bad mechanics. They won't. They'll just be more disappointed. --- The one thing I wish I'd known from the start Your game isn't about the story you love. It's about making your players feel like they're living inside that story. The betrayals. The impossible choices. The moments where there's no right answer, only the one you can live with. That's what makes a game worth playing. That's what makes a world worth visiting. Now go build something that hurts.