The 90% of Your Story the Reader Never Sees

Before your first scene, things happened.

Wars were fought. Families were formed and broken. Promises were made. Characters you'll never meet shaped the people who appear on your pages. The city your protagonist walks through was built, burned, rebuilt. The law that constrains your antagonist was written by someone with a reason.

Most of this will never appear in your story. The reader won't know about most of it. But it shapes everything they see, and they feel its absence or presence even when they can't name it.

This is the iceberg principle applied to story: what's visible above the surface gets its weight from everything submerged below.

The mistake writers make

The mistake isn't having too much backstory. It's trying to show too much of it.

A writer who has thought deeply about the history of their world sometimes feels obligated to share it. The reader should know about the war. They should understand the political structure. They should appreciate how the family arrived in this city and what they sacrificed to stay.

So the writer explains. Early chapters carry the history. Dialogue becomes a vehicle for things characters already know. The story slows while the world is introduced.

Readers feel this as drag. Not because history is boring (history can be gripping) but because it hasn't earned their attention yet. They don't know why it matters. The emotional hook isn't set.

What to do instead

Know everything. Show almost nothing.

The function of deep world knowledge isn't to produce exposition. It's to give you, the writer, the confidence to write the visible story without hedging. When you know exactly why your character behaves this way, you can let the behavior speak for itself. When you know exactly what happened here fifty years ago, you can drop a single detail that carries the weight of all of it.

The reader doesn't need to know the war happened. They need to see its shadow on the character's face in a certain kind of light.

The world before the story

Some events are too large, or too early, to appear in your scenes. They belong to the world's own timeline: the chronology of everything that shaped the story's present, stretching back as far as it needs to.

This is worth keeping somewhere. Not to eventually use it all, but because the act of working it out gives you clarity about what you're writing. A character's bitterness is more specific when you know exactly what happened to them before chapter one. A city's texture is more vivid when you know when it was built and who built it.

Most of it stays private. The reader gets the one detail that carries the rest.

Narrativ has a World Events section for exactly this. Events with their own dates on the world's chronology, linked to characters and scenes where they ripple forward, but not required to appear in the story. They're the record of what you know. The story is the record of what the reader needs to see.

The best writing feels inevitable and surprising at the same time. That quality almost always comes from a writer who has thought further back than the first page.