How do I give different civilisations distinct strengths and weaknesses?

Why fixed bonuses flatten civilisations

The usual shortcut is to assign each people a permanent bonus: one civilisation always builds the best roads, another always fields the finest soldiers, a third always excels at magic. The table learns that choice on day one and never needs to reconsider it, because nothing about the world explains why the bonus exists or when it stops working.

That approach also slides easily into essentialism, where ability is treated as a trait of ancestry rather than circumstance. It replaces history, geography, and institutions with a label, and it leaves the GM with few handles when the story needs to stress a strength or show a weakness in play.

A more durable alternative is to describe what a specific polity, institution, region, or network has built and can maintain. The framework can cover a state, federation, empire, cultural sphere, or diaspora, but a capability belongs to the organisation or historical system being modelled—not to every person associated with it. Describe what institutions and networks can do, not what ‘the people’ are inherently like.

Treat each profile as a snapshot in time. Capabilities can be reformed, copied, displaced, restored, or made obsolete; the same institution may work well in one province and barely reach another. A strength can have dependencies and maintenance costs without needing a neatly matched weakness, and vulnerabilities can also come from separate historical choices.

The four-link model: cause, capability, vulnerability, visible consequence

Use this chain for each major capability so it remains explainable, situational, and playable. Name the organisation or system, its scope, and the conditions where it works. One sentence per link is enough to start:

• Cause The circumstance or deliberate choice that explains why the capability developed: geography, resources, climate, a founding crisis, a lasting institution, or adaptation. Rulers may copy a rival fleet, guilds import expertise, reforms follow defeat, migrants bring techniques, a religious movement reorganises welfare, or new technology makes an old institution viable. People choose, borrow, adapt, and contest as well as respond to their surroundings.
• Capability What the organisation or network can reliably do because of that cause: move goods quickly along a river, defend a pass, administer a census near the capital, negotiate trade treaties, or preserve a particular magical tradition. Never write ‘strong Military’, ‘strong Diplomacy’, or ‘strong Knowledge’ alone; say what kind of capability, where it works, and under what conditions.
• Vulnerability What the capability depends on and what may fail when that dependency is stressed. A strong fleet depends on open sea lanes and allied harbours; a centralised bureaucracy depends on records, roads, and literate clerks; a mercantile economy depends on credit and safe passage. Name conditions, maintenance costs, and dependencies; plausible failure modes follow when they are strained. Capabilities may reinforce one another, while vulnerabilities may arise from unrelated choices.
• Visible consequence What the players can observe without being told the model: coastal cities with foreign quarters, toll stations on the only pass, terraced hillsides that feed the capital, or a college that houses its archives against fire and theft. Show internal disagreement too: merchants demand convoy spending, frontier nobles resent road taxes, provinces resist census reforms, or reformers argue that an old strength has become a liability. If the link has no sign at the table, it does not exist for the players.

Write the whole link as a single sentence when you can: trade houses copied a rival's convoy system and adapted it to the island ports, giving the Harbour League reliable river and coastal supply in fair seasons; it depends on maintained beacons and disputed harbour dues, so players see both the convoys and the council arguments over who pays when storms close the route.

Eight habits that keep strengths honest

Apply these as checks after you draft a civilisation's strengths, so the differences remain situational rather than absolute:

• Derive from circumstances, not ancestry Explain how an organisation developed a capability through its circumstances and choices. A highland confederation may coordinate grain stores because villages built mutual-aid agreements through hard winters; that is an institutional practice, not an inherent trait of its people.
• Distinguish capacity from reputation A civilisation may be famous for its legions while its actual advantage lies in logistics and roads that let those legions arrive fed. Let reputation lag behind reality, be contested, or be outright wrong; mistaken reputation is itself a source of diplomatic friction.
• Make strengths situational No strength should win everywhere. A river-borne supply system excels in the lowlands and stumbles in arid hill country; a council-based diplomacy works among peers but slows crisis decisions. Name the terrain, season, or political context where it applies and where it thins. Ask: where inside this polity is the strength strongest, weakest, or contested? Roads may be excellent near the capital and absent at the frontier; wealthy merchant houses may coexist with weak royal finances.
• Pair strong institutions with dependencies A capable administration needs archives, trained clerks, and regular communication; a renowned college needs patronage, safe travel for scholars, and copied texts. Administration is capacity: the ability to keep records and coordinate action. Legitimacy is whether people accept the authority giving those orders. Either may be strong without the other, and local institutions may remain trusted where central reach is weak.
• Let geography and infrastructure shape options Military, economic, and diplomatic choices follow roads, rivers, passes, harbours, and the maintenance they require. A walled plain can field large levies but must feed them; a scattered archipelago can raid and trade but struggles to concentrate force.
• Use history to explain present shape A past siege, famine, migration, or reform explains why a current priority exists. A society that endured a century of seasonal flooding will invest in dykes, storehouses, and collective labour even when newcomers see little point, and it will resent proposals to dismantle them.
• Make dependencies actionable A dependency is useful when the party can engage with it: negotiate around it, compensate for it, reform it, expose it, support it, exploit or defend it, reroute it, mediate over it, or replace it. They might secure a grain route, invoke a succession rule, repair a road, or help preserve knowledge outside a monopoly. The goal is playable consequence, not simply finding a weak point.
• Treat coordination as a question, not a verdict If you track social coordination or political cohesion, ask what lets different groups coordinate under strain and what makes that coordination fail. It may come from shared identity, local reciprocity, legitimacy, patronage, coercion, ritual, external threat, or federal compromise. Cultural homogeneity is not the measure of resilience; pluralism may be productive.

Eight areas where civilisations differ, with typical causes and vulnerabilities

Optional method: sketch with eight civilisation stats, then explain why

When you need a quick start or want civilisations that do not all lean the same way, use these eight stats as a generation aid. Treat them as prompts to explain, not as fixed bonuses handed to ancestry:

• Military, Logistics, Economy, Infrastructure The material and organisational base: how it fights, moves, produces, and builds things that last.
• Diplomacy, Administration, Knowledge, Social coordination The social and institutional base: how it negotiates, governs, remembers, and coordinates across groups under strain.
• How to use the numbers Treat each number as current relative capacity in your campaign context, not a global rating of a whole civilisation. Roll 1d6 or draw from a small spread for each stat, assigning 1 to 2 as notably weak, 3 to 4 as ordinary, and 5 to 6 as notably strong. For each notable result, add its scope and conditions, one place or institution where it is strongest, one where it weakens, and its trajectory if relevant: rising, stable, strained, or declining. Then note its cause, dependencies, and visible consequences.
• Why this framing matters Randomisation only establishes the starting profile. The explanation that follows is the actual design: a high Diplomacy score might mean a dispersed trading diaspora, a shared faith that sanctions oaths, or a deliberate policy of marriage alliances after a costly war. A low Infrastructure score might mean a deliberate choice to remain mobile, a recent loss of quarries, or a habit of spending surplus on patronage rather than roads. Two civilisations with the same numbers should still feel different because their causes and vulnerabilities differ.
• Keep it situational If a stat suggests superiority, narrow it: Logistics 5 might mean excellent river supply inside the basin, ordinary elsewhere, and currently strained because two bridges are out. Note its scope and conditions, where it is strongest and weakest, and whether it is rising, stable, strained, or declining. A single number never describes capacity everywhere.

This method is most useful for a future civilisation or economy generator: generate a profile, then generate the causes, dependencies, and visible signs that let a GM run the result without falling back on broad assertions about peoples.

Before these civilisations reach the table

For each major civilisation the party may deal with, confirm you can answer:

• Which two or three strengths matter most in the next few sessions, and what circumstance explains each one?
• What does each strength depend on, and what single disruption would stress that dependency?
• Where does each strength apply well, and where is it ordinary or weak?
• Is any strength merely a reputation rather than a tested capacity, and who benefits from that confusion?
• What will the players see, hear, or pay differently when the dependency holds versus when it fails?
• Which roads, rivers, passes, harbours, archives, or granaries must be maintained for the strength to persist?
• What historical event made this priority feel necessary to the people living under it?
• Where inside this polity or network is the capability strongest, weakest, or contested?
• Is the capability rising, stable, strained, or declining in the present campaign?
• Who inside it disagrees about the capability, its costs, or whether it should change?
• What can players negotiate around, compensate for, reform, expose, support, exploit, defend, reroute, mediate, or replace?

A compact capability profile

Use this short template for a polity, region, institution, or network. Fill only the fields that help you run it:

**Capability:** **Scope / where it works:** **Cause:** **Institutions / people maintaining it:** **Dependencies:** **Current state:** rising / stable / strained / declining **Failure modes:** **Internal disagreement:** **Visible signs:** **What players can affect:**