I stared down at my meeples and I almost cried.
So I re-read all my cards,
Thought of decisions I could choose,
And I knew,
That I was probably gonna lose…
On Wikipedia: “Analysis paralysis is an anti-pattern, the state of over-analyzing (or over-thinking) a situation so that a decision or action is never taken, in effect paralyzing the outcome.”
In the field of boardgames, analysis paralysis describes a situation in which decisions are too complex, choices are too numerous, or the consequences that may result from decisions are too difficult to evaluate. So the player… thinks… and thinks… and starts to move… and then changes their mind… …and does nothing. They’re paralyzed by analysis. The other players at the table begin taunting and complaining, further exacerbating the situation, while also secretly fearing that the same fate awaits them on their turn.
Who is to blame for this analysis paralysis epidemic? Sometimes, of course, analysis paralysis results from a player’s inexperience, a mismatch of skills with the game, or excessive use of narcotics.
Sometimes, the blame is on us, the designers who created that situation, because WE failed to make certain decisions when we designed the game in the first place.
Life is already complicated enough. As Psychologist Barry Schwartz discusses in Ted Talk and book The Paradox of Choice, our lives are far more stressful because of the overabundance of unnecessarily complex decisions we have to make: choosing cell phone plans, cable packages, dietary choices, etc. Decisions were simpler in the good old days, when we’d get up in the morning and ask ourselves, “Hunt or starve?
So, with such complicated modern lives, why would anyone sit down at a table around a board and 100 components to play a game that consists of countless difficult decisions?
Because we love that stuff!!! These aren’t the decisions we need, these are the decisions we deserve. We don’t want to think about day care or health care, we want to be super heroes, railroad barons, and starship captains.
A table top game, at its core, is a structure for making decisions, with a feedback system for rewarding those decisions.
When we play a game, we engage our cerebral cortexes in a variety of processes: gathering and synthesizing information, making predictions, and finally making game decisions. The rewards for these decisions are game successes; we occupy territories, blow up space ships, collect gold, and earn victory points. Best of all, we crush our opponents.
Even when luck is involved, we like to believe that our successes are the result of the decisions we have made.
When designing games, we need to shoot for a level of complexity that matches the needs of our target audience. In my next installment on this topic, I’ll discuss how specific mechanics can contribute to or prevent analysis paralysis. Until then, consider these principles, with the understanding that they do not apply to all types of games.
- 1) Optimize the number and complexity of decisions. Good games limit the choices players can make, so they are not overwhelmed, but still let them feel like they’re in control.
- 2) Optimize the amount of information. Players need sufficient information to take deliberate actions toward the goals of the game, but not so much information that there is always a perfect move to be found.
- 3) Ensure variation in value. Some moves/resources/cards in the game should be better than others, and the advantages they confer should be visible. Varying value facilitates efficient decision making.
- 4) Be consistent. Creating consistent mechanics that are uniformly applied throughout your game allows players to evaluate options more easily, and concentrate their mental energy on strategy, rather than procedure.
- 5) Provide clear goals. If a game’s objective is too vague, players may not be able to see how useful their various options are. Provide visual cues, reference cards, or other means to let players know how well they are doing. This feedback will help them see the value of their choices, or lack thereof.
See Part 2!
Game designer by night, and middle school science and pre-engineering teacher by day. He lives in Santa Maria California with his amazing wife and two unrealistically well-behaved children.
Latest posts by Luke Laurie (see all)
- Ten Things I Learned in my First Five Years as a Game Designer – November 10, 2016
- How to Playtest – Part 3, Being a Good Playtester – August 24, 2016
- Why do gamemakers go to GENCON? – August 8, 2016
3 Readers CommentedJoin discussion
What a nice first installment, looking forward to the next entry!
And by the way, a good easy entrance to your blog – I’m so RSS’ing this 😉
Best regards Emil
Thank you! I hope you like the next installment and other articles from the League!
I’m just getting into game design and working on my first game. This was something I was struggling with in my game and our group discussed it last week, very good article, thanks for writing it, now on to part 2.