Backstory Dumps vs. Earned Reveals: When to Tell | Skrib

The standard note is cut the backstory. The standard advice is to sprinkle it in gradually. Between them sits a writer with three paragraphs about a character’s father and no idea which sentence to keep.

Both are treating the wrong variable. An info dump is not defined by length.

A page of history a reader is desperate for isn’t a dump - it’s a payoff, and they’ll read it at speed. Two sentences they haven’t asked for is a dump, and they’ll skim. The difference is not in the prose. It’s in whether the reader arrived at that paragraph carrying a question.

Which means the work happens before the reveal, not inside it. You don’t fix a dump by shortening it. You fix it by manufacturing the question first.

This sits under our character architecture guide, which covers building the history in the first place. This article is about what reaches the page.

What is an info dump?

An info dump is information delivered before the reader wants it. The term suggests volume, but volume is incidental - readers absorb enormous amounts of backstory happily when curiosity is running ahead of the text, and reject a single unrequested sentence when it isn’t.

The practical definition is behavioural: if the reader’s eyes speed up, it’s a dump. If they slow down, it’s a reveal.

The demand principle

Curiosity behaves like demand. It can be generated, it peaks, and it decays.

Generated: something happens that the reader can’t explain. A behaviour that doesn’t fit, a reaction out of proportion, a name that lands harder than it should.

Peaks: the reader is actively constructing hypotheses. This is the window. Backstory delivered here is not tolerated but consumed.

Decays: two ways, both bad. Either the reader stops caring, or - more dangerously - they build their own answer and commit to it. A reveal that arrives after the reader has constructed a better explanation lands as a disappointment no matter how well written it is.

The scheduling consequence: every piece of backstory has a window, and the window is opened by you. It doesn’t exist until you make it.

Three questions before any reveal

Run these on any passage of history in your draft.

1. Does the reader currently have the question? Not would this be interesting - has the text raised it? If not, either raise it first or cut the passage.

2. Does this change how they read what came before? The strongest reveals are retroactive. They don’t add information; they re-render existing information. A reveal that only explains the future is worth less than one that rewrites the past.

3. Would withholding it cost anything? Genuinely ask. Most backstory is load-bearing for the writer and optional for the reader - see below.

A passage that fails all three is a dump regardless of how well it’s written. A passage that passes all three can run for pages.

Manufacturing the question

Four techniques, roughly in order of subtlety.

The unexplained behaviour. The character does something disproportionate and the text doesn’t comment. A flinch, a refusal, a competence that shouldn’t be there. This is the cheapest and most durable method: it costs one line and generates demand that lasts chapters.

The conspicuous omission. Everyone in the scene avoids a subject. The gap is the signal. Effective because it also characterises the people doing the avoiding.

The third-party reference. Someone else mentions the history, incompletely, in front of the character. The reader learns that something exists without learning what - and gets the character’s reaction as a bonus.

The unexplained cost. The character has clearly paid for something. A limp, an estrangement, a career that stopped. Visible consequence with invisible cause is the strongest demand generator available, because the evidence is undeniable.

The rule underneath all four: show the shape of the hole before you fill it. A reader who can see the outline will read a great deal to have it completed.

Four delivery methods

Once demand exists, how the information arrives still matters.