The “Origin Story Problem” comes from the fact that it is very easy to obsess too much about the discovery phase of the neat idea, whatever it is. It becomes tempting to spend half a book exploring all the ramifications about the black box, before realizing “hey, there needs to be a conflict here.” Then, suddenly out of nowhere, we get a whole series of new characters and plot developments to threaten our hero. The pattern is a staple of bad TV pilots.
To address the “Origin Story Problem,” and make the story seem a cohesive whole, the main conflict of the story needs to become an integral part of all the story. i.e. The vampire hunters that are threatening to stake our newly-undead heroine need to be present before page 300. Or, more broadly, the story problems resolved in the climax need to be at least implicit in the beginning of the story.
There are several ways to do this convincingly:
- Start the main conflict before the “gosh-neato” stuff shows up. In Iron Man, Tony Stark develops the suit as an attempt to solve the problems that begin the movie.
- The main conflict is inherent in the “origin” itself. See Stephen Kings’ Firestarter for a primer on every shadowy government experiment gone awry. See the Bourne Identity for a more low-key variation on the theme.
- The “gosh-neato” bits directly, and quickly, cause the source of the conflict. See most one-way time-travel stories from Lest Darkness Fall to 1632.
- The “gosh-neato” bit is actually the real status quo, dropping the protagonist into some larger over-arching conflict; learning about the cool stuff is really part of surviving in a different world. The first volume of Zelazny’s Amber series is a good example. See also Poul Anderson’s The High Crusade.
What you don’t want to happen is have a story that spends half its time with the protagonist learning and experimenting with some new toy. Readers will say, “that’s cool” for a chapter or two. Then they’ll start wondering when something is actually going to happen.
No comments:
Post a Comment