Nothing stalls a story faster than a paragraph that stops the action to explain a character's entire history. Readers do not need a biography; they need a reason to care about what happens next. Backstory works when it arrives in small pieces, at the moment it explains a choice the character is making right now. The rule of thumb: reveal backstory only when the reader needs it to understand the present scene, and never more than the scene requires.

The most powerful technique is behaviour. A character who flinches at a raised voice, who counts the exits in every room, or who never wastes food tells the reader volumes about their past without a single explanatory sentence. Behaviour also respects the reader: it invites them to infer, and inference creates engagement. When you catch yourself writing a backstory paragraph, ask what action could show the same history instead — then write the action and cut the paragraph.

Dialogue can carry backstory, but only when the conversation has a present-tense reason to exist. Two characters who already know each other's history would never explain it to each other — the classic as-you-know-Bob problem that readers spot instantly. Instead, let backstory surface in conflict: an argument where one character throws the past in the other's face, or a stranger asking a question the character does not want to answer. The tension of the scene makes the revelation feel earned rather than delivered.

Objects and sensory triggers are the subtlest delivery system. A scar, a photograph, a song on the radio, a familiar smell — each can unlock a sentence or two of past without pausing the story. The key is brevity: one vivid image plus one line of implication beats a full page of history. A character touching a worn wedding ring before a difficult decision says more about their past than three paragraphs of marriage summary ever will.

Run a backstory audit on your draft. Highlight every passage that explains a character's past, then ask of each one: does the reader need this now, or could it wait? Could it be shown through behaviour, dialogue, or an object instead? Cut anything that fails both questions. Most drafts lose a third of their backstory in this pass and get faster, tenser, and more immersive in return. Backstory is seasoning, not the meal — use it sparingly, and your story will taste better for it.

How you deliver backstory depends heavily on your point of view, and each has its own traps. In first person, backstory arrives naturally as memory — but only when something in the present triggers it, and only in the character's own voice, with their own biases and gaps. A first-person narrator who explains their whole childhood unprompted sounds like a tour guide, not a person. In close third person, backstory can arrive as free indirect thought: a sentence that slips into the character's own phrasing mid-paragraph, revealing history without a formal flashback. In omniscient narration, you have more freedom to summarise a character's past directly, but that freedom is dangerous — it tempts you to explain everything, and readers disengage when the narrator lectures. Whatever the point of view, the same discipline applies: reveal backstory at the moment it changes how the reader understands a present choice, keep it brief, and return to the present scene as quickly as possible. Point of view changes the delivery system, not the dosage.