Designing a board game rarely starts with a complete ruleset, a perfectly balanced system, or a brilliant idea that simply needs to be written down. More often, it begins with something much smaller: an experience you want players to have, a mechanism you find interesting, a theme you want to explore, or even a problem you noticed while playing another game.

The difficult part is turning that starting point into something that actually works at the table. That means researching what already exists, deciding what matters most in your idea, building a prototype, testing it, making changes, and gradually discovering what the game really wants to be.

This guide gives you an overview of that journey: what happens at each stage, why it matters, and where beginners most often get stuck. It will not give you a complete formula for designing a game. There isn’t one. But it should give you a clear map of the process and help you understand what you need to learn next.

Start With Inspiration and Research

Every game needs a starting point, but that starting point does not have to be a complete concept. It may be a theme you want to explore, a particular interaction between players, a mechanism that interests you, or simply the thought: “What if this worked differently?”

Start With Something Worth Exploring

At this stage, you do not need to know exactly how the game will work. An idea is enough to give you a direction.

What matters is identifying what attracted you to it in the first place. Is it the theme? A certain decision you want players to face? A particular feeling or type of interaction? That initial spark will probably change during development, but it gives you something to start exploring instead of waiting for the entire game to appear in your head.

See What Already Exists

Once you have a direction, look at how other games approach similar ideas. Board game design does not happen in a vacuum. Existing games can show you which solutions are already common, where problems tend to appear, and how differently the same basic idea can be interpreted.

Research is not about finding something to copy. It gives you reference points. The more games you understand, the easier it becomes to recognise what is already familiar and where your own design may have room to offer something different.

Define the Experience and Turn the Idea Into a Prototype

An idea becomes much easier to develop once you know what you want players to experience. Are they supposed to feel clever, tense, competitive, curious, in rush, or perhaps constantly suspicious of one another? The answer does not need to be perfectly defined, but it gives you something more useful than “I want to make a game about pirates.”

If defining that experience feels difficult, the 8 Types of Fun can provide a useful vocabulary for thinking about what players should actually enjoy during the game.

Once you have that direction, choose mechanisms that support it. Hidden information may encourage uncertainty and bluffing, while open information may shift the focus towards planning and calculation. The mechanism is not the goal itself. It should help create the experience you want and gradually form the core of the game.

At this point, do not try to solve everything. Once you have enough of an idea to test the intended experience, move it onto the table.

How to Prepare Your First Prototype

Your first prototype does not need to look impressive. It needs to give you something you can actually play and change.

A useful early prototype should be:

• Playable. It contains enough of the game to test the basic idea.
• Readable. Players can understand what the cards, pieces, spaces, or symbols represent.
• Easy to change. Paper, a printer, markers, spare cubes, and borrowed components are usually more than enough.

This is not the moment for 200 cards, six asymmetric factions, and finished artwork. The first version will probably change (sometimes dramatically) after only a few tests.

The purpose of an early prototype is not to impress anyone. It is to give you something you can test quickly and revise just as quickly.

Test Early and Learn Through Iteration

Once you have something playable, testing becomes part of the design process. You are no longer asking whether the game in your head sounds good. You can finally see what actually happens when it reaches the table.

The first tests should focus on the basics. Does the central idea create interesting decisions? Does the game flow? Which part feels promising? What works completely differently from what you expected?
Problems appearing during a test are not evidence that the design has failed. They are the reason the prototype exists.

A test gives you observations and feedback. Those lead to conclusions, conclusions lead to changes, and those changes create the next prototype.

Not every loop ends with a small improvement. Sometimes you adjust one rule. Sometimes an entire mechanism needs to change. Occasionally, the best conclusion is that an idea is not worth developing further. But that does not mean the time was wasted. What you learned moves into your next project.

This iterative process is where much of board game design actually happens. Wojtek “Łosiu” Wiśniewski explores the full cycle (and why learning to repeat it matters more than perfecting your first idea) in Board Game Design Process: Why Iteration Matters.

Discover and Strengthen the Core

Early prototypes often contain more ideas than the game actually needs. As development continues, some parts begin to prove their value while others turn out to be distractions. This is where you start discovering what the game is really built around.

It helps to separate three things:

• Core - the interaction, decision, or system that creates the experience worth preserving.
• Content - cards, powers, factions, scenarios, objectives, and other elements that add variety around that core.
• Balance - the work of making sure the available choices and strategies function fairly once the main systems are stable enough.

A common beginner mistake is moving too quickly from an interesting idea into producing content. But twenty more cards cannot rescue a central interaction that simply is not enjoyable.

Before asking “What else can I add?”, ask “What part of this game is actually worth building around?”

Once the core works reliably, content has something solid to build on. Detailed balancing comes later, when the underlying systems are stable enough that adjusting the numbers is actually worth the effort.

We explore this distinction further in Core, Content, Balance: A Practical Framework for Board Game Design.

Learn to Interpret Feedback and Question Your Solutions

Playtesters are very good at showing you where something feels wrong. They are not always equally good at telling you how to fix it.

A player may say that a card is too strong, a turn takes too long, or a rule should be removed. Treat that as useful evidence, but not necessarily as the final diagnosis.

Instead of immediately defending the game or explaining what you intended, try to understand the reaction:

• Where exactly did the problem appear?
• What was the player trying to achieve?
• What did they expect to happen instead?

The better you understand the cause, the better chance you have of solving the right problem. Listen carefully to the problem. Be cautious with the proposed solution.

This also means questioning your own ideas. A mechanism may be elegant on paper or personally important to you, but if repeated tests show that it works against the intended experience, it may need to change or disappear.

We explore why feedback needs to be interpreted rather than simply followed in Playtest Feedback Is Lying to You.

Refine, Simplify and Balance the Game

By this point, the question has changed. You are no longer asking whether there is a game here, but how to make the experience stronger, cleaner, and more balanced.

That may mean:

• removing rules or content that create complexity without improving the experience;
• refining pacing, interactions, and decisions that already work;
• balancing strategies so that one path does not become the obvious answer every time.

More is not automatically better. Every card, ability, exception, or subsystem should have a reason to exist. If you cannot explain what something adds to the experience, it may not need to be there.

Balance also does not mean making every option equally powerful in every situation. It means giving players meaningful alternatives without one strategy consistently making the others irrelevant.

Scoring deserves particular attention because it does more than determine the winner. It tells players what the game considers successful. Ideally, the final score should help players understand why their strategy worked or failed, not simply show who collected the most points.

That relationship between scoring, strategy, and player feedback is explored further in Why Scoring Systems Aren’t Enough in Board Game Design.

Make the Game Work Without You

At some point, your game needs to stop depending on you.

Early playtests are usually guided by the designer. You explain unclear rules, answer questions, correct misunderstandings, and sometimes even remind players what they can do. That is useful at first, but it can also hide problems.

The next step is to let other groups play with less help, and eventually with no designer at the table at all. If players misunderstand an action, use terminology differently than you expected, or repeatedly ask the same question, the problem may not be with them. It may be with the game’s communication.

Rules, icons, terminology, component layout, and examples therefore become part of the design itself. A good game is not only playable when its creator explains it well. It should communicate clearly enough to survive on its own.

At this stage, the questions start to change. You are no longer only asking whether the mechanisms work, but whether players can understand and use them as intended.

Understand When a Game Becomes a Product

A game can work brilliantly at the table and still be difficult to publish. Once you decide to approach publishers, the question changes from “Is this a good game?” to “Is this a product someone can realistically bring to market?”

Publishers are evaluating more than whether the prototype is fun:

• Who is it for?
• What will be the manufacturing cost?
• At what price can it sell?
• Does it fit the publisher’s portfolio?
• Is there a market for it?

A design may be enjoyable but too expensive to manufacture, too similar to something a publisher already sells, or simply aimed at an audience they do not serve.

Expect the Game to Change Again

That does not mean you should design around market expectations from the first prototype. Your priority is still to build a strong game with a clear core and purposeful content. But once a publisher becomes involved, you should expect the game to change again.

A publisher may adjust components, complexity, theme, playtime, production cost, or even parts of the design to better fit its audience and portfolio. That is not necessarily a rejection of your work. It is part of turning a game into a product. A designer needs to know what is essential to preserve, but also be ready to let other parts evolve.

For a closer look at what publishers evaluate, why promising prototypes are often rejected, and how a game may continue changing after submission, see Inside a Publisher’s Inbox: Why Most Board Game Prototypes Never Get Published.

Conclusion

Understanding the board game design process gives you the map. Learning how to navigate it requires practice, tools, and a structured method.

A game grows through repeated cycles of exploring an idea, defining the intended experience, building, testing, learning, simplifying, and refining. The goal is not to make every decision correctly at the beginning. It is to learn what to look for as the design develops.

Want to Go Deeper?

Knowing the stages is one thing. Learning how to move through them with purpose is another.

Board Game Design Fundamentals: A Step-By-Step Guide takes that next step, guiding you from the first idea and prototype through testing, iteration, and the decisions that turn an early concept into a game ready for serious development. Make your way to a published game shorter.