A Simple Way to
Create Suspense
By LEE CHILD
How do you create suspense? I’m asked that question often, and it seems that every writers’ symposium has a class with that title. It’s an important technical issue, and not just for so-called suspense novels. Every novel needs a narrative engine, a reason for people to keep reading to the end, whatever the subject, style, genre or approach.
But it’s a bad question. Its very form misleads writers and pushes them onto an unhelpful and overcomplicated track.
Because “How do you create suspense?” has the same interrogatory shape as “How do you bake a cake?” And we all know — in theory or practice — how to bake a cake. We need ingredients, and we infer that the better quality those ingredients are, the better quality the cake will be. We know that we have to mix and stir those ingredients, and we’re led to believe that the more thoroughly and conscientiously we combine them, the better the cake will taste. We know we have to cook the cake in an oven, and we figure that the more exact the temperature and timing, the better the cake will look.
So writers are taught to focus on ingredients and their combination. They’re told they should create attractive, sympathetic characters, so that readers will care about them deeply, and then to plunge those characters into situations of continuing peril, the descent into which is the mixing and stirring, and the duration and horrors of which are the timing and temperature.
But it’s really much simpler than that. “How do you bake a cake?” has the wrong structure. It’s too indirect. The right structure and the right question is: “How do you make your family hungry?”
And the answer is: You make them wait four hours for dinner.
As novelists, we should ask or imply a question at the beginning of the story, and then we should delay the answer. (Which is what I did here, and you’re still reading, right?)
(You notice I haven’t told you what the invention was yet? I implied a question, and didn’t answer it. You’re waiting. You’re wondering, what did almost no one have in 1980 that almost everyone had in 1990? You’re definitely going to read the next paragraph, aren’t you? Thus the principle works in a micro sense, as well as in a macro one. Page to page, paragraph to paragraph, line to line — even within single sentences — imply a question first, and then answer it second. The reader learns to chase, and the momentum becomes unstoppable.)
What almost no one had in 1980 and almost everyone had in 1990 was a remote control. Previously, at the end of a segment or a program, we could be fairly sure the viewer wouldn’t change the channel on a whim, because changing the channel required the viewer to get off the sofa and cross the room. But afterward, changing the channel was easy, which was very dangerous for an audience-hungry station.
So how did we respond? (Notice the structure here? Wait for it!) We started asking questions before the commercials, and answering them afterward.
For instance, heading toward a movie review program, I remember we asked: Who was the studio’s first choice for the Harry Callahan role in “Dirty Harry”?
We knew most viewers would be intrigued. (What, Clint Eastwood wasn’t the first choice?) But — and this was the lesson — the success of the tactic didn’t depend on intrigue. Even viewers with no interest at all stuck around to find out. Humans are hard-wired. They need to know. Even viewers who knew the answer for sure stuck around, in order to be gratified. The gap was bridged, and the danger averted. (It was Frank Sinatra. You waited, right?)
We need to bring the same simple principle to our books. Someone killed someone else: who? You’ll find out at the end of the book. Something weird is happening: what? You’ll find out at the end of the book. Something has to be stopped: how? You’ll find out at the end of the book.
Like the old cartoon of the big fish eating a smaller fish eating a very small fish, you’ll find out the big answer after a string of smaller drip-drip-drip answers. The big answer is parceled out slowly and parsimoniously. I remember doing that in “Killing Floor,” my first novel featuring Jack Reacher, a drifter and ex-military policeman. Something weird is happening in a small Georgia town. O.K., great, but what? Well, it seems to be something to do with money. Fine, but what exactly? Well, it seems to be about getting hold of perfect blank paper for counterfeiting purposes. Wonderful, but where the heck are they getting it?
(I’m not going to tell you. Read the book.)
In my latest Jack Reacher novel, “A Wanted Man,” it’s clear on the first page that a mysterious person has been murdered. Who was he? Why was he killed? He has appeared so early that the reader has no emotional investment in him. He doesn’t even have a name. Even so, the questions nag, and they aren’t completely answered until the last page.
Trusting such a simple system feels cheap and meretricious while you’re doing it. But it works. It’s all you need. Of course, attractive and sympathetic characters are nice to have; and elaborate and sinister entanglements are satisfying; and impossible-to-escape pits of despair are great. But they’re all luxuries. The basic narrative fuel is always the slow unveiling of the final answer.
So don’t bake cakes. Make your family hungry instead.
No comments:
Post a Comment