Maybe backstory isn’t so bad after all

I know what you’re thinking: I’ve finally lost it. For most of the last two years, I’ve used this blog to rail against the use of excessive backstory, advising writers to kill it whenever it occurs, preferably with fire. I’ve pointed out that characters in a novel are interesting because of their words, deeds, and decisions over the course of the narrative, not because of whatever they might have been doing or thinking before the story began. I’ve argued that backstory violates the principle that a good story should consist of a series of objectives, and that character is best revealed through action. I’ve pointed out, stealing an observation from the great William Goldman, that heroes must have mystery, and that to explain away a character through digressions into his past or psychology—at least in most forms of popular fiction—only serves to diminish him. And I’ve often referred to examples of characters who become more interesting the less we know about them, like Forsyth’s Jackal, and those who have been progressively ruined by excessive backstory, like Hannibal Lecter.

I still believe all these things. Recently, however, I’ve found myself writing reams of backstory for two different projects. One, Eternal Empire, is the concluding novel of a series that can’t be entirely understood without additional information about the earlier installments, which is something that I didn’t really appreciate until reading over the most recent draft. The other is a long, self-contained novel I’ve been working on for years, and whose protagonist’s actions make somewhat more sense with a slightly more detailed backstory. In both cases, I added backstory after both novels were finished, in an attempt to address specific narrative problems, namely a lack of clarity that was preventing readers from getting lost in the story. And although I’ve begun to tactically incorporate backstory where it seems advisable, my earlier convictions haven’t changed. For most writers, I’m convinced that less backstory is preferable to the alternative, and that implication and suggestion are more powerful tools than extended passages of introspection. But there are times, looking back at a story that is otherwise complete, when I’ve found that a few scraps of backstory have their place.

If this seems inconsistent, it’s only because the rules of writing, like most laws, operate under an informal hierarchy, and it’s often worth stretching a minor rule so as to preserve a major one. (Or, as the rabbis say, it’s better to break one sabbath in order to keep many sabbaths.) You can debate which rules are more important than others, but it’s hard to argue with John Gardner’s observation that for most writers, the primary objective is to preserve the fictional dream: the illusion, in the reader’s mind, that these events are actually happening. Anything that tears the reader out of the dream without good reason needs to be examined and, usually, corrected. And one issue that can break the illusion is unintended ambiguity. If the reader puts down the book to wonder about a detail in a character’s past that the author didn’t mean to leave unresolved, it’s probably worth introducing this information, solely for the sake of maintaining momentum. And my reluctance to spell things out has occasionally confused readers in ways I didn’t intend. This led to some trouble with my recent Analog story “The Voices,” and also seems to be an issue in The Icon Thief. (Given the chance, I think I’d insert a few more paragraphs about Duchamp and his place in art history to avoid sending readers to Wikipedia.)

That said, backstory needs to be introduced judiciously, and at the proper point. In particular, it’s often best to save it for a moment when the story can afford to slow down. Such flat moments, which serve as a breather between points of high action, provide a convenient place for filling in the background, as long as it makes sense within the structure of the novel as a whole. The two projects I’m writing now both happen to have a convenient opening in the exact same spot: at the beginning of the second section, which currently picks up immediately from a cliffhanger at the end of the previous chapter. Inserting a flashback here, with the tension of the previous scene unresolved, both extends the suspense and allows me to fill in necessary background in reasonable security that the reader will read on to see what happens next. This sort of thing can be taken too far, of course: I keep such departures as short as possible, afraid that I might conclude what T.E. Lawrence did after rereading a chapter intended as a “flat” in Seven Pillars of Wisdom: “On reflection I agreed…that it was perhaps too successful.” So most of my earlier points still stand—even, or especially, when I’m forced to break them.