The Working Writer's Bundle

Grab the special pricing

Obsidian Tavern
Obsidian Tavern
Worldbuilding Creation: Build the Load-Bearing Decision First

Worldbuilding Creation: Build the Load-Bearing Decision First

By Updated

Most worldbuilding advice hands you a checklist. Geography, history, cultures, magic, religion, politics. Fill in each box and you have a world.

You do not have a world. You have a pile of boxes.

The problem with the checklist is that it treats every decision as equal and independent. In a real world nothing is independent. The mountains decide where the rain falls, the rain decides where the farms are, the farms decide where the cities grow, and the cities decide who fights whom. Build those as separate boxes and the reader feels the seams.

So the first move in worldbuilding creation is not to build everything. It is to find the one decision everything else hangs on, and build that.

Start With the Load-Bearing Decision

Every world that feels real has a foundation the rest of it stands on. Usually it is one of two things: the geography, or the one central rule that makes the world unlike ours.

For Herbert's Dune the load-bearing decision is a desert planet with no free water. Everything else falls out of that. The stillsuits, the water discipline, the Fremen culture, the worms, the spice, the empire that fights over it. You could reverse-engineer most of Arrakis from the single fact that water is the scarcest thing on it.

For Le Guin's Earthsea the load-bearing decision is that magic works by knowing the true name of a thing. The wizard schools, the caution around speech, the balance you have to respect, all of it grows from that one rule about how the world is wired.

Pick the decision that, once you make it, forces a hundred other decisions for you. That is the one you want first. If a decision does not force anything else, it is decoration, and decoration can wait.

Let Everything Cascade From It

Once you have the load-bearing fact, you do not brainstorm the rest. You derive it.

Ask what that one fact does to the people living inside it. Where does it put the food, the money, the power, the fear. Follow each answer to the next question and keep going until the questions run out.

When I built The Bottom, one of my own worlds, I set one fact and refused to add a second until I had wrung that one dry. The entire world is a single vertical city, ten thousand years tall. From that, altitude just becomes class. The sky districts get sunlight, the deep city runs on bioluminescence, and the Administration charges people ventilation fees for the air moving down the shaft. I did not decide the tax structure. The height decided it, and I wrote down what it told me.

That is the difference between building and deriving. A pile of lore is a hundred choices you made. A world is one choice, followed honestly to its consequences.

A Build Order That Actually Cascades

Here is the order that keeps the cascade intact. Each layer answers the layer above it and feeds the one below.

Step Layer The question it answers What it feeds
1 Load-bearing decision What one fact makes this world unlike ours? Everything
2 Physical constraints What does that fact do to land, resources, survival? Where people live
3 Economy and power Who controls the scarce thing? Class and conflict
4 Culture and belief What do people tell themselves to live with it? Values and religion
5 History How did this arrangement get built and challenged? Grudges and institutions
6 The present conflict Where is the pressure about to break? Your actual story

Notice that magic systems, maps, and pantheons are not their own steps. They are outputs. A magic system is step 1 if magic is your central rule, or it is a consequence of step 2 if it is not. Same with religion. People do not invent gods at random. They invent gods that explain the thing they cannot control, which means your belief systems come from your constraints, not from a separate box.

If you want the cause-and-effect spine drawn out explicitly, this is where worldbuilding history and a working worldbuilding timeline do their job. Both are just the cascade run forward through time, one event forcing the next.

Geography Is Usually the Cheapest Foundation

If you are stuck on what the load-bearing decision should be, start with the map.

Geography is the easiest foundation because it forces so much for free. Put a mountain range down the middle of a continent and you have already created two climates, two peoples who developed apart, a trade route through the one pass, and a war over that pass. You did not invent any of that. The mountains did.

Tolkien built this way. Middle-earth reads as old because the geography came first and the history was layered onto real terrain, so the rivers and ranges feel like they were there before the stories. That is why the map in the front of the book is doing narrative work, not decoration.

Draw coastlines, mountains, and rivers before you name a single kingdom. Then ask where you would live if you were poor, where you would live if you were powerful, and where the two would collide. The political map draws itself on top of the physical one.

Consequences Are Where the World Earns Belief

A world is only as believable as the costs it is willing to show.

A rule the reader never sees enforced is a rule the reader does not believe. Somebody has to break the taboo, pay the price, and have the rest of the world react. That reaction is where your institutions, your laws, and your grudges come from.

Sanderson is precise about this on the magic side, where the limits and costs of a system matter more than its powers, because a cost is what turns a rule into a choice a character has to make. The same logic runs through the whole world, not just the magic. Show what it costs to live under your central fact and the reader stops questioning whether the fact is real.

This is also the line between two ways of running a world. In hard worldbuilding you document the rules and pay them off on the page. In soft worldbuilding you imply the costs and let the reader feel a system they never see fully explained. Either works. What does not work is a rule with no consequence attached, because that reads as an author who has not decided if the rule is true.

Common Ways the Cascade Breaks

The pile-of-lore problem usually comes from a few specific mistakes. Most of them are the same mistake wearing different clothes: adding a second load-bearing decision before the first one is spent.

Two central rules that do not talk to each other will always feel bolted together. If your world has both a naming magic and a separate god-granted magic and neither one constrains the other, the reader files them as two worlds sharing a cover.

Culture invented for flavor is the other big one. A festival, a food, a custom that does not trace back to a constraint is just set dressing, and readers can tell the difference between a tradition that means something and one that is there to look foreign. For the practical moves that keep culture tied to cause, worldbuilding tips is the closer-range version of this whole argument.

The fix for both is the same. Every time you want to add something, ask what forced it. If the honest answer is nothing, you are decorating, and the world does not need it yet.

FAQ

Where do I start when building a world from scratch? Start with one load-bearing decision, the single fact that makes your world unlike ours. Usually that is the geography or the one central rule of how the world works. Build that fully before adding anything else, then derive the rest from it.

Should I build geography or magic first? Build whichever one is your load-bearing decision. If magic is the central rule of your world, it comes first and everything cascades from it. If magic is just one feature, build the geography first, because geography forces the most other decisions for free.

How detailed does a world need to be before I start writing? Only as detailed as your story touches, plus one layer underneath. You need the load-bearing decision and its main consequences solid. The corners the reader never visits can stay blank until a scene demands them.

How do I keep a world from feeling like a pile of disconnected lore? Derive instead of brainstorm. Every element should trace back to your central fact through a chain of consequences. If a custom, city, or rule does not answer to anything above it, it is decoration, and decoration is what makes a world feel assembled rather than grown.

What is the difference between hard and soft worldbuilding? Hard worldbuilding documents its rules and pays off the costs on the page, so readers can predict what magic and society can do. Soft worldbuilding implies the rules and lets consequences be felt rather than explained. Both work as long as the costs are real underneath.

More from this Category

Obsidian Worldbuilding: The Complete Guide

Obsidian Worldbuilding: The Complete Guide

Traditional worldbuilding scatters your fictional world across a dozen Word documents that slowly contradict each other. Obsidian stores your world the way you actually think about it: as a web of linked characters, places, events, and systems where changing one thing shows you everything it touches. This guide covers vault setup, the templates worth keeping, linking discipline, Maps of Content, daily workflows for writers and game masters, and the traps that quietly kill vaults before the world ever gets built.