Case Study 2: Soren Johnson and Civilization IV --- The Systems Designer as Architect

The Quiet Craft of Systems Design

If Shigeru Miyamoto represents the designer as observer and feel-crafter, Soren Johnson represents the designer as architect. Not the kind of architect who designs buildings that look interesting. The kind who designs buildings that work --- where the circulation makes sense, the structure holds under load, and the spaces produce the behaviors the architect intended.

Johnson is not a household name. He does not have Miyamoto's celebrity or Kojima's cult following. But among working game designers, he is one of the most respected practitioners in the industry. His work on Civilization IV (2005) and his own studio's Old World (2022) demonstrates what it means to be a systems designer --- someone who creates experiences not through spectacle or narrative but through the careful, deliberate construction of interlocking rules.

Civilization IV: A System of Interesting Decisions

Johnson joined Firaxis Games in 2000 and served as lead designer on Civilization IV. The Civilization series, created by Sid Meier, is the canonical example of systems design in games: you guide a civilization from the ancient era to the modern age, making decisions about technology, expansion, diplomacy, warfare, and culture. The game is a decision engine. Every turn asks you to choose, and every choice has consequences that ripple forward through the rest of the game.

Johnson's job was not to invent Civilization. The series was already established. His job was to take an existing system and make it better --- more elegant, more balanced, more conducive to interesting decisions. This is the often-invisible work of systems design: not the glamorous act of creation but the painstaking craft of refinement.

The Religion System

Johnson's most celebrated design contribution to Civilization IV is the religion system. Previous Civilization games had treated religion as a simple bonus --- a building you could construct, a modifier to happiness or culture. Johnson redesigned religion as a system that interacted with diplomacy, culture, technology, and warfare.

Here is how it works:

• Seven religions exist in the game, each founded by discovering a specific technology. The first civilization to research Meditation founds Buddhism. The first to research Polytheism founds Hinduism. And so on.
• Religions spread between cities through trade routes, missionaries, and the Holy City mechanic (the city where a religion was founded generates automatic spread).
• A civilization can adopt a state religion, which provides bonuses but also creates diplomatic effects: civilizations that share your religion are friendlier; civilizations with different state religions are hostile.
• Religious buildings (temples, monasteries, cathedrals) provide culture and happiness bonuses, but only for cities where that religion is present.

The mechanics are straightforward. But the dynamics they produce are extraordinary.

🔗 Connection: Notice the MDA framework at work. The mechanics are simple rules: religions are founded, spread, and affect diplomacy. The dynamics are emergent strategic dilemmas: adopting a religion to gain a powerful ally means alienating another civilization. The aesthetic is meaningful choice --- the player feels that their decisions have consequences that matter and persist.

Dynamic 1: The founding race. Because only the first civilization to research a technology founds the associated religion, there is a strategic race in the early game. Do you rush Meditation to found Buddhism, gaining a religion you control? Or do you invest those research turns in military or economic technologies, accepting that you will not found a religion but will be stronger in other ways? This is a classic tradeoff --- a systems design concept where choosing one path forecloses another.

Dynamic 2: The diplomacy web. Shared religion creates friendship. Different religions create hostility. This means the player's choice of state religion is also a choice about alliances. If your neighbor has adopted Christianity and you adopt Islam, your neighbor becomes hostile. If you both adopt Christianity, you become friends --- but you are now both hostile to the Buddhist civilization on the other side of the continent. The religion system turns diplomacy from a simple like/dislike meter into a web of relationships shaped by belief, proximity, and strategic interest.

Dynamic 3: Religious spread as soft power. Religions spread through trade routes without the player doing anything. This means that maintaining trade connections with another civilization gradually spreads your religion to their cities. Over time, if your religion dominates another civilization's cities, their population becomes culturally aligned with you --- even if the other leader is hostile. This is soft power. You are winning a cultural and religious contest without firing a shot.

None of these dynamics were individually designed. Johnson did not design "the founding race" or "the diplomacy web" as features. He designed a small set of mechanics (founding, spreading, state religion, diplomacy modifiers) and the dynamics emerged. This is systems design at its best: simple rules producing complex, meaningful behavior.

The Craft of Balance

Systems design is not just about creating interesting mechanics. It is about balancing them --- ensuring that no single strategy dominates, that every choice is viable in some context, and that the game remains interesting regardless of which path the player takes.

Johnson has written and spoken extensively about balance, and his perspective is illuminating:

"Perfect balance is not the goal. The goal is that the player always has an interesting decision. If one strategy is slightly stronger than another but both are viable, that's fine. If one strategy is so strong that choosing anything else is a mistake, that's a balance failure."

In Civilization IV, this philosophy manifests in the technology tree. There are dozens of technologies, and the order in which you research them defines your civilization's trajectory. Johnson's team spent months tuning the costs, prerequisites, and benefits of each technology to ensure that multiple paths through the tree were viable. Rush military technology and you can conquer neighbors early but fall behind in economics. Rush economic technology and you grow wealthy but are vulnerable to aggression. Rush cultural technology and you can win through cultural dominance but must survive long enough for culture to accumulate.

🎯 Tradeoff Spotlight: The art of systems design is creating tradeoffs, not optimal solutions. If the technology tree had one clearly best path, the game would have one strategy, and replayability would collapse. The design challenge is ensuring that each path through the tree is strong in some contexts and weak in others, so the player must read the game state and adapt. This is what Sid Meier means by "interesting decisions" --- decisions where both options have genuine merit and genuine cost.

From Civilization IV to Old World: The Art of Iteration

In 2022, Johnson released Old World, a game he designed at his own studio, Mohawk Games. Old World is, in many ways, a response to Civilization --- it takes the 4X strategy formula and asks: what if we changed the assumptions?

Two of Old World's most significant design innovations illustrate the iterative process at the career level --- a designer taking lessons from one game and applying them to the next.

Orders Instead of Turns

In Civilization, every unit can move every turn. This means that as your empire grows and you control more units, each turn takes longer. Late-game Civilization can feel like a chore because you are mechanically moving fifty units when only three of them matter.

Old World replaces the per-unit movement system with a shared pool of "Orders." Each turn, you have a limited number of Orders, and every action --- moving a unit, building an improvement, training a new unit --- costs one or more Orders. This means the player cannot do everything. They must prioritize.

The dynamic: every turn becomes a resource allocation problem. Move this army or develop that city? Explore this frontier or reinforce that border? The constraint (limited Orders) creates meaningful choice on every turn, not just the turns where something interesting is happening.

💡 Intuition: The Orders system is a perfect example of constraint as design tool. By removing the ability to control every unit every turn, Johnson added strategic depth. The player must think more carefully about each action because actions are scarce. This is the paradox of freedom through limitation that Chapter 7 will explore: less freedom to act means more meaning per action.

Characters and Succession

Civilization's leaders are immortal. You play as "Napoleon" or "Cleopatra" for the entire game, from 4000 BC to the space age. This is a convenient abstraction, but it eliminates an entire dimension of strategic depth: what happens when the leader changes?

Old World has mortal leaders. Your king or queen ages, develops traits, forms relationships with other characters, and eventually dies. Their heir inherits the throne --- with different traits, different relationships, and potentially different priorities. A warrior king might be succeeded by a scholarly queen who is better at research but worse at combat.

This creates a dynamic of planning across generations. The player must think not just about the current turn but about the succession --- who will lead next, and how will their strengths and weaknesses change the strategic landscape? The systems design (mortal leaders + trait inheritance + relationship mechanics) produces a dynamic (succession planning) that creates an aesthetic (the feeling of guiding a dynasty, not just a civilization).

The Event System: Narrative Through Systems

Old World also introduces a text-based event system that fires based on game state. Your general wins a battle? An event might offer you a choice: promote them (gaining loyalty but creating jealousy among other generals) or celebrate publicly (gaining public approval but appearing arrogant to rival nations). Your heir comes of age? An event chain determines their education, their personality traits, and their readiness to rule.

These events are not scripted narrative in the traditional sense. They are systems-generated narrative --- stories that emerge from the interaction of character traits, game state, and player choices. The event system is a mechanic. The stories it produces are dynamics. The player's feeling of guiding a living, breathing dynasty is the aesthetic.

This is systems design extending into narrative territory. Johnson did not write a story. He wrote a system that produces stories. And because the system responds to game state, no two playthroughs generate the same narrative. The player's decisions create the history, and the event system gives that history texture and consequence.

📝 Note: The event system in Old World draws on a long tradition in strategy games, from Crusader Kings's event chains to King of Dragon Pass's narrative decision points. What makes Johnson's implementation notable is how tightly the events are integrated with the mechanical systems --- events do not exist in a separate narrative layer. They emerge from, and feed back into, the same systems that govern combat, economy, and diplomacy. The narrative and the mechanics speak the same language.

Water Finds a Crack: Johnson's Design Philosophy

One of Johnson's most influential contributions to design thinking is his essay "Water Finds a Crack," published on his blog Designer Notes in 2010. The central argument: players will always find and exploit the optimal strategy in your game, so your job is to ensure that the optimal strategy is also the most fun strategy.

"Water finds a crack" means that if your game has a dominant strategy --- one approach that is clearly better than all alternatives --- players will discover it and use it, even if it is boring. In Civilization, if building a hundred cheap units is more effective than building twenty expensive ones, players will build a hundred cheap units, even though managing a hundred units is tedious. The game has cracked, and water (player behavior) has found the path of least resistance.

Johnson's solution is not to patch the cracks after players find them. It is to design systems where the cracks do not exist --- where every strategy has a counter-strategy, where every advantage comes with a tradeoff, and where the path of least resistance is the path of most fun.

This philosophy directly connects to the chapter's discussion of iteration. You cannot know where the cracks are from the design document. You can only find them by playtesting --- by watching real players interact with the system and observing where their behavior diverges from your intentions. The cracks are always there. The question is whether you find them before or after you ship.

What Johnson Teaches About Systems Design

Johnson's career illustrates several principles that are central to this chapter:

1. Elegance Over Complexity

The religion system in Civilization IV has a handful of mechanics. It is not complex. But it is elegant --- the small number of mechanics interact with each other and with existing game systems (diplomacy, culture, technology) to produce a rich web of strategic decisions. Elegance in systems design means maximizing the ratio of emergent dynamics to designed mechanics. A few rules that interact richly are better than many rules that operate in isolation.

2. Systems Design Is Invisible

When a player enjoys Civilization IV, they do not think "the religion system's diplomatic modifiers create an interesting web of alliances." They think "should I adopt Christianity to ally with Rome, or stay Buddhist to keep Asoka friendly?" The systems design is invisible. The player experiences decisions, not mechanics. This is the mark of good systems design: the player never sees the architecture, only the building.

3. Iteration Operates at Every Scale

Johnson iterated within Civilization IV (tuning the technology tree across hundreds of playtests) and across his career (redesigning turn structure in Old World based on lessons from Civilization). Iteration is not just a development phase. It is a design philosophy that applies to individual mechanics, whole games, and entire careers.

4. The Designer's Job Is to Create Interesting Decisions

Johnson once said in a GDC talk: "If the player knows the right answer before they make a choice, you have not designed a decision. You have designed a quiz." The systems designer's ultimate goal is to create situations where the player must weigh genuine tradeoffs --- where both options have real merit and real cost, and the "right" answer depends on context, strategy, and the player's own priorities.

🔄 Check Your Understanding: Think about a strategy game you have played (board game or video game). Can you identify one system that produces "interesting decisions" in the way Johnson describes? What makes those decisions interesting? What would happen if one option were clearly superior to the others?

Conclusion: The Architect's Satisfaction

Systems design is not glamorous. It does not produce viral trailers or emotional narratives. It produces spreadsheets, balance patches, and the quiet satisfaction of watching a player agonize over a decision --- knowing that the agony means the system is working.

Soren Johnson's contribution to game design is not a single game or a single mechanic. It is a demonstration of what happens when a designer treats the game as an architecture of decisions --- a structure designed so that every room the player enters offers a genuine, meaningful, consequential choice. The religion system in Civilization IV, the Orders system in Old World, the mortal leaders and succession dynamics --- these are not features. They are architecture. And like all good architecture, they work best when the people inside them never notice the design.