A Simple Way to Create Suspense

Do you know who Jack Reacher is? We mean the real, hulking, shit-kicking giant of a hero of 17 novels, not the miniature wimp played last year by Tom Cruise.

Lee Child, author of the following article, is the creator of the real Jack Reacher. And now that we’ve read this we’re going to forgive him for the film and pop over to Amazon.Com for at least one of the books.

Gotta love that ticking clock!
Gotta love that ticking clock!

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?)

Readers are human, and humans seem programmed to wait for answers to questions they witness being asked. I learned that fact in my first job. I worked in television production from 1977 until 1995, and the business changed radically during that time, mainly because of one particular invention. It was something that almost no one had in 1980, and that almost everyone had in 1990, and it changed the game forever. We had to cope with it. We had to invent a solution to the serious problem it posed.

(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.)

Read it all (because you can’t help yourselves, right?)

 

We're looking forward to your comments!

This site uses Akismet to reduce spam. Learn how your comment data is processed.