Showing posts with label Structure. Show all posts
Showing posts with label Structure. Show all posts

Tuesday, February 28, 2012

Drawing Attention to Things

I've read a bunch of short stories in the last couple of months, and over the last week, I've had the interesting experience of editing a bunch of short stories all written by different people. One thing I've noticed is that many writers have the same technical difficulties.* That's not surprising, considering that we're all trying to do more or less the same thing (writers like Lydia Davis notwithstanding).

I've noticed particularly that writers are having difficulty emphasizing passages in their stories, and I've seen similar techniques attempted to draw attention to things, techniques that don't quite work. There are two ways writers tend to accent passages: set the line off typographically, or turn up the amplitude on the prose.

Typographical emphasis:
What I mean by this is when a writer makes a sentence or a sentence fragment into a paragraph of its own. You've seen it before, I'm sure. The story is going along, blah blah blah blah blah blah blah blah.

And then there's this sentence.

The story then continues, blah blah blah blah blah. This tactic generally fails, for two reasons. The first reason is that we've all seen this done a bunch of times before. It's a cliché and so it doesn't surprise us (and therefore doesn't move us emotionally). The second reason this fails is because it likely doesn't solve the real problem in the story's structure. More on that in a minute.

High-amplitude prose:
What I mean by this is when a writer wraps the bit of prose they want to emphasize up in florid or ecstatic or frenetic language, to heighten the emotional intensity of the passage. You know, the story is going along and Johnny walked down the corridor, moving against the tide of his fellow students, making his way to his locker. He had only a minute before his next class began and he was in a hurry. Johnny found his locker, spun open the combination lock and found his chemistry text. As he angrily slammed the uncaring locker shut, he heard the metal hinges' high-pitched squeaking that scraped tinnily with all the rushing agony he felt for his young life, a miniscule wail lost in the terrific indifferent din of the echoey corridor and so on and so forth for fifty or sixty words and really Johnny's just slamming his locker door but we want to show that he's upset.

This doesn't usually work because in general there's a stylistic shift into the purplest of prose and the actual meaning of the sentence gets buried under all the modifiers and editorializing. In the sentence above, every noun has at least one adjective, every verb at least one adverb, and I'm also telling you how Johnny felt and about what. More effective would be "Johnny slammed his locker door." Really it would, especially if you've solved the structural problems of emphasis.

I promised to talk about structure, didn't I? Yes, I see that I did. Anyway, the biggest failure when writers attempt to emphasize something is structural. It's not the sentence's fault that it doesn't jump off the page the way you want. You need to leave that sentence alone. There are two good rules that I try to follow when I want to emphasize a passage:

1. Use the simplest, plainest language I can in the emphasized passage, because it's the story event that I am trying to highlight, not my godlike prose style.

2. Prepare the event in the preceding passages.

Rule Number 1 is very important, and you can easily lose momentum by throwing a lot of poesy prosey at your victims readers at an important moment. Be clear. Focus. Let the characters and the premise and the emotion carry the moment. If your characters and premise and emotions can't carry the moment by itself, you have probably ignored Rule Number 2.

The thing is, a story is an object. It's a thing, that takes up space and has a discrete size and a set beginning, middle and end. It's right there on the page; you can see it for yourself. And within this object are traffic patterns and forces at motion. You've put them there yourself. Sometimes the forces don't go anywhere, or they don't go in the direction you want. This means that your story is broken.

This object of a story should have a single most important moment in it. It can be the Joycean "epiphanic moment" where the protagonist sees something and his life is forever changed. Or it can be simply the moment where the central conflict of the story is either resolved or not, the "crisis moment." Whatever you're doing, be it Joyce-style or Chekhov-style, you should know what the One Big Moment in your story is. And all of your storytelling should aim to set up that moment. The prose on either side of that moment should not muddy the issues, should not lessen that moment, should not for God's sake comment upon that moment. If the moment you're going for does not stand out, does not create emotion in your reader, you should look at the shape of the story. You should look for movement within your story that contradicts what you're attempting. You should look for vagueness that muddles the meaning of your One Big Moment. Don't just look at your Moment, look at the whole story. Very likely, the sentence you are laboring over for hours and hours is not the real problem.

It's hard to really illustrate this without an actual example or two, I know, but time is short and I have stuff to do at the office, so I'll just leave you where you are. The structural lessons are hardest to learn, so if you're just starting out writing stories, I push Rule Number 1 at you and suggest you work with that for a few stories.

*Or, perhaps, I have aesthetic differences with most writers and I label those differences "areas to improve" in other writers.

Wednesday, August 31, 2011

Three Acts, Two Acts or No Acts?

I've been thinking a lot about structure lately, about the large-scale organization of novels. I have two books in the works at present: one in rough-draft form that I'm about to start revising, and one just starting out with about 11,000 words written. The novel in draft form has a very loose 3-act structure, but only because I was pretending to follow the conventions of the genre (it's a literary detective novel).

There was a time that I leaned very hard on the 3-act structure. It's dependable, for one thing. It works. It gets the job done. There were a few years where, if I thought about the overall sweep of one of my books, I always imagined a three-part story. If I was putting together an outline of a book preparatory to writing a first draft, I'd spend hours tinkering with the plot and character arcs, working the whole thing up into the classic 3-act structure.

A couple of books ago I came up with a variation on the classic 3-act, which was the inner/outer conflict story model. Go here to read about it. That seems a pretty decent way of arranging a narrative, and it's also a sturdy, dependable model. You can write sturdy, dependable stories.

When I was drafting the detective story, I found that my writing was pushing against the 3-act structure. The whole "beginning-middle-ending" thing made sense at one level for what I was doing, but it made no sense at all for some of the other things I was working on. I ended up with a sort of hybrid structure, with a linear 3-act story going on while a bunch of short story type things kept cropping up along the way. Some of these short story things were flashbacks, some of them were almost self-contained stories and some of them were other things. Most of them dealt with the emotional themes of the story that weren't really addressed by the main detective story plot.

Working on the new book, I can see in my imagination how the first half of the book will go: two alternating stories that will join up in the middle of the book. And then, once the two main characters have met, some other stuff will happen. I have no idea what the "story question" is. I have no idea what will happen when my protagonists meet. I do know what each of them thinks they want more than anything else and I can see how their meeting will appear to open doors in their lives, but I don't know how any of that resolves. But I do know that this new novel doesn't fit into the 3-act structure. There isn't an "inciting incident" nor is there a development where the protagonist attempts to solve a problem, nor will there be a third act where the main conflict is resolved. Nope. None of that stuff. Two people move along, they meet, and stuff happens. I have a vague sense of how it will come out on the page, but I can't really see a big structure to it. And you know what? I'm not looking for one.

I think I'm now more interested in a more lifelike, realistic way of building narratives. The transformative hero's journey is wholly inadequate for the type of stories I'm trying to build these days. People->Action->Consequences, possibly, is the real paradigm. Don't talk to me of rising tension, I say.

One of the books I'm reading right now is Haruki Murakami's Wind-Up Bird Chronicles. Davin and I have been discussing it while I read it. He loved it and I've been having trouble with it. Today I read page 325 and there's a passage where one character tells the protagonist that he's not insignificant, that he's working on problems for any number of people without even knowing it. On the one hand, this passage bothers me because anyone who's read more than a couple of novels has already figured this out and this novel is thick with handholding statements like this, explaining itself to the reader in a clumsy sort of manner. On the other hand, I saw that Murakami really was presenting a Kafkaesque protagonist who was waffling around in a world that was largely incomprehensible to him (and to the reader) and that the point of the novel was that very incomprehensibility (which Davin told me last week but I didn't quite get it). The protagonist's world--and the narrative itself--are unpredictably shaped. Unexplained events and unlikely coincidences coexist in every chapter; who knows why? Just like reality. Now I'm enjoying the novel and I read a lot of it at lunch. I don't know if any of the story's questions will be answered, but I see that it doesn't matter if they do. What's the "meaning" of most of Kafka's stories? No idea and I don't care.

I'm also reading a lot of Chekhov stories, and Chekhov sort of invented the indeterminate ending, as well as the story where the climax comes at any point and the story might continue for thousands of words past that climax because the climax, the resolution of the primary tension, is not the real point of the stories. What's the organizing principle of a Chekhov story? That's hard to say, really. People. Action. Consequences. Or not.

Anyway, what I find most interesting about all of this is that, when I began writing novels, I struggled hard and long to find a structure around which to build stories. When I figured out how to use the classic 3-act structure, I was relieved and I thought I had that part of writing all figured out and I never had to think about structure again. After using the 3-act structure for a couple of novels, though, the artificiality of the form has made it more or less useless to me and I have to find something else. That "something else" seems at this point to be nothing more than a strong sense of what happens in life, a vague idea of causality, though I am working very hard to steal Davin Malasarn's trick of having unexpected changes of direction come along in the story.

So none of this is particularly useful or interesting, but it's what I've got. I thought I'd have something definite to say about large-scale structure, but it seems that all I've really got to say is that while I used to preach the classic 3-act shape, I no longer do. There are loads of excellent stories to be made using that structure (and almost every movie made follows it), but it's not a necessity. You can find your own way. Sometimes you have to.

Wednesday, April 6, 2011

Don't Look Directly At The Drama Or You'll Go Blind

You know how you're not supposed to look directly at some types of eclipses because the light might damage your eyes?

I wonder if you're not supposed to write directly about some dramatic points in your story because it'll end up being a let down for the reader.

I recently finished two novellas that were more plot heavy that most of my other stories. They were fairly linear, building up to climactic moments that involved murder and the like. As I was writing up to the dramatic scene, I was feeling the excitement of the story. But, when I got to the actual scene, there was always a bit of a let down. At least for me. Like other activities, it seemed like the build up to the climax is better than the climax.

It's not a surprise that readers have expectations when they're moving through a story. If you are leading them somewhere, and building the tension, they're probably preparing themselves for some big climactic moment. But, will the actual writing ever match up with what a reader hopes to read?

My guess is no.

In my experience, rarely has anything in reality been better than the vague expectations I prepared myself for. My unopened Christmas presents are always much cooler than my opened ones. And, it has nothing to do with quality, in my experience. It has to do with expectations. If you're expecting a mouthful of chocolate, a grapefruit is going to taste funny no matter how good it is.

I thought of Light In August by William Faulkner. In that book, the climactic scene isn't told to us directly. Readers are led up close the climax, and then, POOF, we're on the other side, and hearing about the event secondhand. Faulkner's reasons for doing that always puzzled me, but as I was writing my novellas I realized that that little F-ster might have actually been on to something. (If he were alive, I'd tussle his hair.) By leaving the climax unwritten, the reader is allowed to insert his or her imaginary expectations into the gap. They're creating their own climax, or at least supplementing the climax.

I'm going back to Cyberlama after taking my little novella-cation, and I'm excited to play with this idea of the hidden or implied climax.

What do you think?

Tuesday, January 18, 2011

Loose Endings

On Saturday evening, Mighty Reader and I saw a play: Cymbeline by William Shakespeare. It was a comedy, which means that it had not only the main dramatic arc but a half dozen other arcs going on. This is certainly an entertaining way to structure a play and it's also how Shakespeare managed to keep the beginnings and ends of his plays away from each other for three or four hours. The plots leapfrog past each other, faster and faster and more ridiculous and violent until the final scene where everything is resolved and all the mysteries and mistaken identities and misunderstandings are resolved.

And about that last scene.

What Shakespeare tends to do is gather together onstage every surviving character in the play and have these characters point at each other before witnesses and make accusations which are refuted; explanations flow nonstop for fifteen minutes or so while every character has one of those "But...I thought you...oh, I get it. Well done indeed. Kiss me, Kate and buy me a drink, Ernesto! All is forgiven!" moments.

About ten minutes from the end of one of these comedies (it doesn't really matter which*) I am always struck by the same realization: these last scenes really aren't necessary. Likely back in the 16th century, when people treated going to the theater as a more social event and drank, ate and chatted their way through the afternoon or evening, a big scene at the end that summarized all the subplots was needed because nobody had really been paying attention to the whole thing. Possibly people only really closely watched the first and fifth acts of these plays; I really don't know and that's not the point.

Here's the point, Mr. Shakespeare: Every character in your story doesn't need to know how everything works out for everybody as long as your reader knows. These final scenes are unnecessary and they slow down the action at the end because, frankly, we've all heard all of this explanation already. Sometimes twice already. So essentially the audience/reader is forced to sit through a summary of the action while all the characters get caught up.

I really hate these denouements, and what's worse is that they are not unique to Mr. Shakespeare's works. I have run across any number of novels that have anywhere from two to two-hundred pages of "wrapping up" and these final sections make me want to blind myself with a sharp object (I'm looking right at you, Mr. Tolkien with your "Scouring of the Shire" and other dull-as-death final chapters). Maybe this is purely a matter of taste, but I'm certain that a well-written ending without all the post-climax exposition would satisfy most readers. In my own books, I work my way to the climax and then I get out of the story as absolutely quickly as I possibly can. My opinion is that you do not have to explain what happens in any sort of detail, nor do you have to show all of the loose ends being tied up. What you need to do--all you need to do--is point the reader at the likely outcomes of the various dramatic arcs. Your readers are bright enough to figure the future histories of your characters out for themselves. Really they are.

*I except of course The Winter's Tale which ends with the stage direction "Exit, pursued by a bear."

Tuesday, December 14, 2010

Transitions and Foreshadowing

Sometimes when I am first writing a scene, especially one that's got a lot of dialogue, I jump from one conversational thread to another with no warning. That is, the characters are all talking about dogs, for example, when one of them will change the subject, suddenly asking about paramecia. This can jar the reader, which is usually a bad thing.

I know that some writers want to write a scene where one character surprises another, and that's fine. "Hey, what the--?" the surprised character says. But you don't want to surprise your reader the same way. You don't want them to question the internal reality of the story. If character X is concealing something, and character Y is going to spring the news that she suspects this, your reader should be aware of this in advance. You need to prepare the change in the dialogue. The reader should be able to see it coming. Not necessarily the answer to the question, but the question itself.

Most of the jarring transitions in dialogue or other scene elements are not attempts to spring a surprise; it's just clumsiness on the part of the writer. For example, one of the passages in a MS of mine read like this:

[Prince Hamlet has given Horatio an astrolabe found in an abandoned observatory]

The astrolabe was heavy. I had never touched it before but I had seen it every day that I served as Tycho’s assistant, over the desk where I performed my slow calculations after a night spent observing the heavens.

"Thank you, my lord. I will treasure this."

"You should sell it," he said. "There are men who would pay handsomely for such trinkets."

"How long have you been hiding here?"

"I do not hide, Horatio..."


The transition from talk of the astrolabe to Horatio's question ("How long have you been hiding?") was too abrupt, and not prepared for the reader. So I added a transitional statement to bridge the ideas:

The astrolabe was heavy. I had never touched it before but I had seen it every day that I served as Tycho’s assistant, over the desk where I performed my slow calculations after a night spent observing the heavens.

"Thank you, my lord. I will treasure this."

"You should sell it," he said. "There are men who would pay handsomely for such trinkets."

"I shall keep it, for it has been hiding here awaiting my return," I said. "And how long, my lord, have you been hiding here?"

"I do not hide, Horatio..."


This transitional passage works by taking an element from the current conversation (the astrolabe) and an element from what's to come (hiding) and combining them into a single idea (the astrolabe was hiding). This makes it appear as if Horatio's question ("How long have you been hiding?") flows naturally out of the conversation and smooths over the transition between subject matter.

Which is essentially my entire technique for transitions, whether I'm working on a short dialogue or a large-scale plot device. If you are going to introduce something new into the story, you should prepare the reader for it. We call this "foreshadowing," which is a term I really like. The "shadow" of what's to come falls on the narrative before we see the thing itself.

Anyway, suppose you are writing a book and you want to introduce vampires (really, Scott? Vampires?) into the story. What are the elements of vampirism that you'll be using? Maybe blood, sharp teeth, cemeteries, etc. So I'd have some of those elements in the narrative well before the actual vampires show up. Yes, maybe you think it's way more cooler to have the vampires explode onto the scene as a Big Damn Surprise, but you need to drop subtle clues for your reader ahead of time. It will make the vampires seem natural and inevitable. (Also I add this general comment: Don't confuse surprising your characters with surprising your readers. It is not the same thing.)

So the basic model for any sort of transition becomes this:

Past story elements --> transition <-- Future story elements

You just drag elements from where you are and from where you want to go together into a single scene. The cool thing about this is that you can pretty much use whatever elements you want. The less obvious the elements the better, and it still works most of the time.

Friday, October 29, 2010

Friday Filler: A Look Into Bailey's Brain!

I am beginning to outline a new book. The overall structure that's emerging seems to be fairly non-traditional, with the timeline cut into bits and rearranged. It's been hard for me to describe it to people, so I'll attempt it with the assistance of HTML font color tags!

Imagine that the following row of letters represents a continuous, linear timeline that tells the entire story of my novel. It starts at A1 and ends at D4. You can think of each letter/number pair as a chapter, if that makes it easier:

A1A2A3A4B1B2B3B4C1C2C3C4D1D2D3D4


Time, as in calendar time, moves from left-to-right, like this:
---------------------------------->
so that if A1 was January 1st, D4 would be December 31st. More-or-less.

You can also think of the As as being the story of preparing for a journey. The Bs will be the story of the journey. The Cs will be the story of the adventure at the end of the journey. The Ds will be the state of the world after the adventure has finished. With me so far?

So my near-brilliant idea was to take this linear story and cut it up into four big chunks, like the acts in a play, and each chunk of the book, or act, will contain part of each of the colored sections of the story. All the 1s will be in the same act, all the 2s, etc.

The first act would look like this:

A1B1C1D1


The second act would look like this:

A2B2C2D2


Et cetera. So the entire structure of timelines would be this:

DA1B1C1D1A2B2C2D2A3B3C3D3A4B4C4D4


Yes, it starts at the end. The "D" sections are sort of the big structural markers that recur throughout the narrative. Anyway, that all seemed kind of cool to me, and there were going to be parallels between the action in each section. You'd see how the way things were at the start of preparing for the journey affected the actual start of the journey which affected the start of the adventure, etc.

I realized, however, that I didn't want to actually be foreshadowing things like this. I wanted realization to dawn on the reader instead, by giving confusing information and then showing how things were destined to happen that way (this is going to be at one level, I think, a book about mistakes). Which means that I have to show the results first, and then the events that foreshadow them. In other words, I don't want to (for example) have a couple fight, he says something harsh, she slaps him, they break up. I want to have the breakup scene first, then her slapping him, him saying something harsh, then the couple fighting. So I have to reverse all the time-sections within each act of my book, like this:

DC1B1A1D1C2B2A2D2C3B3A3D3C4B4A4D4

As you see, at the very end of the book, you get the last bit of the "preparing for the journey" state right before you get the last bit of the aftermath of the entire story. Which I think will be pretty cool. If I can bring this off. My plan is to simply write out the entire story, in chronological order, and then cut it up into sections and put them into my possibly-near-brilliant almost-backwards narrative structure, and then see how it goes from there. This will either be great or just a huge mess. I have no idea what revisions will be like. But it looks difficult and interesting and so, you know, I can't resist. I am also toying with the idea of having the 4s come first and the 1s come last. I remain undecided.

Anyway, that's what I think I'll be doing with my winter and spring.

Also! Happy Halloween! Also-also! I am once again not doing NaNoWriMo! But good luck to any of you who are! You're braver than me.

Friday, October 22, 2010

Story and Nested Structures

Lately I have used a the idea of interrupting the dramatic action of a story with an explanation to give shape to my writing. I know, this sounds like a good way to ruin the flow and pacing of a story, but bear with me. This is a structure that I have found useful in everything from bits of dialogue to full scenes to entire story arcs across the length of a novel. It’s scalable and you can build nested story structures with it and It Works Really Well.

Here’s the basic idea, as applied to the act of writing a very short story. Imagine you've started writing something new, and you've got the initial action and image down on the page. Maybe it goes something like this:

The blood on my hands made the wheel slippery and the car slewed into the left-hand lane before I regained control. I’d put off replacing the old wiper blades and they were almost useless in the heavy rain; I was driving nearly blind through the night, driving much too fast. Christ, there was a lot of blood on me. It was serious now, and I had to get out there to the house as soon as I could. I wasn’t going to let anything get in my way this time. I was going to finish this, all of it, tonight.

You, as the writer, already know how the story will turn out, what’s going to happen at the house on the edge of town, and why. The main dramatic action of the story is What Happens This Night At The House Outside Of Town. But you have to explain it; you have to give meaning and context to that action. So you cut the story of the drive and confrontation in half, right in the middle, and you go backwards in time to give the events leading up to your protagonist getting behind the wheel of his car. So maybe we’ll take an intermediary step backwards, somewhere between the story-present and the backstory. Maybe it goes something like this:

Juliette had tried to stop this before I was even born. All of that crap with the Moon and all of that time in the asylum hadn’t changed anything. Juliette had been a good mother, but she couldn’t prevent this.

So I think that’s a fine transitional passage. The story-present has mentioned some mysterious “it” and this passage refers to that same “it” but gives more (though vague) information about whatever “it” is, invoking the Moon and an asylum. Maybe something to do with werewolves? I don’t know. I’m making this up as I go along, but if this was your story, you’d already know. We've given a lot of information in nine sentences, and to me it doesn’t feel like an info-dump, even though almost all of it’s been exposition so far.

We have also pointed the narrative in a new direction at this point, at a new character: the protagonist’s mother. From this intermediary passage, which already steps us outside of the story-present’s timeline, we can go to the important bits of the protagonist’s backstory, if we want. Maybe something like this:

The first sign that something was wrong came when I was five years old. We were living in Chicago at the time, in a crappy one-bedroom apartment in one of those ugly tombstone-like tenements on the South Side. One morning I was sitting at the wobbly linoleum table in the kitchenette, eating my cereal. Juliette was in the bathroom, getting ready for work. I saw something out of the corner of my eye and turned to look up at the kitchen counter. Right beside the sink was a greasy black rat, reared up on his back legs, his shining red eyes looking straight at me. I felt like I'd been hit in the chest, right in my heart, with a hammer.

I don’t know what happened next. Something scary, I’m sure. But at this point, we have established a nested structure of storylines:

1. The external dramatic story, of the House Outside Of Town.
2. The story of Juliette, which is also the larger historical story of whatever “it” is.
3. The personal history of the protagonist, who I have just named Dick Raley because I can.

Having established this overall nested structure, we can move between the three timelines at will. The thing to remember is that, if you want to do this right, you have to keep the action moving forward. Everything that happens in whatever level of narrative has to foreshadow and set up whatever happens next in whatever timeline. The story keeps moving forward, always. You do not stop the story. Ever.

My favorite place to insert these interruptions is right when the dramatic action has reached a fever pitch. That is to say, right before the climax and resolution of the action. For example, if a story of mine had this passage during the Final Confrontation between Protagonist and Antagonist: I pointed the gun at his head. He asked me not to, he begged me, told me there was no other woman. I didn't believe him. He started to run, and I pulled the trigger. I would be tempted to stop right there after the word "trigger" and loop backwards through time for a paragraph or two to give an image (always dramatized, not just internal monologue or whatever form of telling) that either shows how the woman with the gun is mistaken but doesn't realize it (Irony!) or how she and the cheating bastard were once happy (Pathos!) or something else depending on what's going on in the story.

It’s also possible to use these nested levels to discuss different things about the story. For example, you can use level 3, Dick Raley’s personal history, to tell the inner story, which is going to be Dick’s coming to terms with some truth about himself or the world that he doesn’t want to admit. Or whatever. You can use level 2, about Dick’s mother Juliette, to explore the theme(s) of the story, where this truth of Dick’s causes some kind of conflict between Dick’s personal reality and the rest of the world. Or whatever. And you can use level 1, the “gosh, but I’m covered with blood and driving too fast” story, to tell an action-packed suspense story. So you can have three stories all at the same time, linked together and nested like Matryoshka dolls. There is no limit to how many nested stories-within-stories or moments-within-moments you can have. There may be a limit to how much of this your reader can take, depending on how sudden the shifts are.

I actually wanted to talk about the subtle things you can do with this nesting of timelines, but I realized I should talk about this in a more general sense first. Maybe next time.

Also! Contest! Yes, a quick contest, if anyone wants to enter. Take my three paragraphs above and finish the "bloody hands" story I’ve begun! Keep it to about 1000 words or fewer! Winner gets a valuable prize! Likely a stinking Amazon gift card, because that seems to be what people give as prizes in the age of blogs. You have until, I don’t know, Tuesday, November 2nd to enter. I am sole and final judge, and I reserve the right not to award the prize. If you have an entry, email it to me at scott (at) scottgfbailey (dot) com. If you don’t have an entry, I still like you.

Tuesday, September 21, 2010

Taking Risks With Structure

When I wrote the most recent draft of my book Killing Hamlet, I used a traditional narrative structure where the story is presented in chronological order, in past tense, with only a few brief passages of explanatory backstory here and there. It seemed like the best way to tell the story and I was content with a straightforward narrative until I got to the very last chapter. At that point, something in my brain zigged when normally it would have zagged, and I decided to do something different.

There were a couple of reasons I wanted to do something radical in the final chapter:

First, the chapter had to contain the book's last scene of dramatic action and then relate what happens after the story proper ends. I really don’t like the “story/epilogue” structure, and I wanted to avoid it. But I still wanted all that epilogue material in the chapter.

Second, I have taken a lot of chances with this book already. I’ve pulled the characters out of Shakespeare’s play “Hamlet” and told a different tale with them, one that sort of mirrors the historical accounts of Hamlet that Shakespeare based his play on, but also plays fast-and-loose with the source materials and with “Hamlet” and is entirely new at the same time. That’s a risk in itself. So I figured that if the reader was willing to come along up to this point, I could try to pull one last rabbit out of the hat and give a shot at a really virtuoso performance in the final chapter. So, yeah, I just want to show off a bit at the very end.

Third, and this properly goes with the first point, I wanted the drama to keep rising until the very last word on the very last page of the book, and using the “story/epilogue” structure won’t allow that; the epilogue is always a slackening of drama and I want to go out on a high note, to keep pushing the reader into new territory with each sentence. Again, it’s showing off.

So I came up with a structure that’s more or less as follows:

Last scene of story (interrupted)
10 years previous
Last scene of story (continued)
A few hours later
Last scene of story (continued)
Three years later
Last scene of story (continued)
Three years later
Last scene of story (finishes)
Three years later and into the future

The language becomes increasingly high-flown and poetic as the chapter progresses, and I am inordinately pleased with the last sentence of the book. I’ve never attempted anything quite like this before, with a narrative sort of coiling around itself while moving forward. I bail out of the 'last scene of story' in the middle of the action without truly finishing the scene; it’s clear what’s going to happen so there’s no point in spelling it out. I’m proud of that bit. Anyway, this is the chapter that establishes my “literary fiction” street cred. I have no idea where the impulse to tell the last scene and the epilogue in overlapping segments came from, but I’m glad it came to me.

My next big book project will present the story out-of-order, for the length of the narrative. We'll see how that works out. Some day I'll try A.S. Byatt's idea of "laminating" stories on top of each other, or working the way Salman Rushdie has done, telling at once several stories that are linked just barely by theme/location. Or maybe I'll borrow the idea from Nabokov's The Real Life of Sebastian Knight where the book takes on the structures of the books the narrator is discussing, but this isn't pointed out to the reader. Who can say? Possibilities abound.

So, you: are you doing/have you done anything interesting/different with the structure/chronology of your narrative(s)? If so, what? How successful do you think you were? How have readers responded to it?

Friday, August 6, 2010

Cliffhangers & Page-Turners

As a writer of literary fiction, I am alleged to be unconcerned with such things as hooking my reader and making my novels into "page turners." Fie upon such allegations, I say. To paraphrase literary great Salman Rushdie, you can do whatever you want in the way of digressions and word play and formal innovation as long as you hang it all on a good story. And a good story, in my opinion, keeps the reader turning the pages to see what happens next.

Now, some of that "page turning" quality has to do with the premise and the characters. Heck, most of it. But some of it has to do with pacing and structure, which are purely mechanics. That is to say, there are some tricks you can play on your reader to keep them turning the pages, reading "just one more chapter" when they should be getting to bed.

In my current book (and in the MS I finished before my current project) I have been experimenting with different ways to add suspense to the structure of the storytelling. Suspense refers to the reader wanting to know what happens, or how the questions they are forced (by you, the author) to ask about the story will be answered.

I add suspense on two levels: the story level, and the chapter level. At the story level, I throw out the big Story Question ("Will X manage to do Y before Z happens?") and then as I tell the story, I throw out questions to the reader in the form of mysterious statements. "Pity about your dog," A says to B, but nobody explains what that means. Add more references to the dog as the chapters go by and, if you do it right, the reader starts to really want to know WTF is up with the dog. (Bear in mind that this is entering into a contract with the reader: if the payoff--the relationship of the dog to the story--isn't very interesting when you get to it or if it makes no sense or isn't really part of the Story Question, you have cheated your reader. Don't.) Basically you tantalize the reader with little mysteries as you go along, the answers to those mysteries revealing the nature of the Story Question.

At the chapter level, I have been experimenting with cliffhanger endings. These are pretty easy to do, at least the way I've been working it. Suppose you have a scene or a sequence of scenes leading to a Very Exciting Climax. Let's visualize the movement of the scene/chapter/whatevs toward the climax like this:

----------------CLIMAX!->

There is likely a temptation to make this into a single chapter, with the end of the chapter coming after the climax. You might be tempted do all your chapters like this, ending them at the conclusion of some exciting action or reveal. Let's use an asterisk to represent the chapter breaks:

*-------CLIMAX!-> * -------CLIMAX!-> * --- et cet.

This sets up a regular rhythm where the action always falls off at the end of a chapter, and gives the reader a place to put the book down and go to sleep. In one book I wrote, half the chapters ended with the protagonist going to bed at the end of the day. This structure did not exactly catapult the reader into the following chapter. Catapulting the reading along is, however, just what we want to do.

What I'm doing now is ending the chapters IMMEDIATELY BEFORE the exciting climax, so that the reader hits the chapter break and wants to know what happened and maybe will keep reading. So the structure looks like this:

* -CLIMAX!->--- * -CLIMAX!->--- * -CLIMAX!->--- * et cet.

Three things happen here. First, each chapter begins with something exciting. Which is good in and of itself. Next, you move on from the climax of one dramatic arc to building the next dramatic arc, giving the reader another little mystery and another question of "what happens next?" You hook them into the next scene/sequence and pull them forward into the story by raising the tension and then WHAM you end the chapter again without resolving any of the tension you've just built up.

This might be cruel to your reader and you might want to put in some slow chapters and vary the pacing so it's not exhausting and all being pitched forward through action. If you want. But you should never end a chapter at a point of rest in the story. Ask a question, or throw a grenade, or kidnap a princess, and then run like hell to the next chapter. If you do it right, your reader will stay hot on your heels, trying to catch up with you.

Wednesday, June 23, 2010

More On Middles: Starting Over

I've read any number of novels where the middle section moves the protagonist to a new setting and surrounds him with new characters. One of the difficulties of this sort of structure is that, in a lot of ways, the story sort of starts all over again. The author risks slowing things down to a crawl while she introduces setting, characters, backstories and all sorts of exposition. I cast my mind back to Jhumpa Lahiri's The Namesake, which does this "relocating and starting over" several times during the second act.

My work-in-progress has just moved into the second act, and I've written the first chapter of the middle. My challenges were to introduce a new setting and at least four new characters, as rapidly as possible while still keeping the action moving forward and not letting all the exposition display itself as exposition. Those are the same sorts of challenges we face at the beginning of a story, and I think it's essential that we meet those challenges the same way, with the same ideal of keeping the action going.

Rather than prolix and beazle on in the abstract, I think I'll just show you the first part of Chapter Ten, where my WIP's Second Act starts, and comment on what I'm doing as I go along. This is a pretty long excerpt, so you might want to come back and read all this when you have more time. Just saying. Also, this is still a bit rough since I wrote it only a few days ago, so all the usual caveats. Ready? Here we go:

(My explanatory notes are all in blue italics below.)

Chapter Ten

A local legend, very ancient, tells of the giantess Hvenhild who gathered up an armload of hills in Zealand, put the acres of earth into her apron and waded over the Sound toward Sweden, ten miles away. When Hvenhild was halfway across the water, one of her apron strings snapped and all her thousands of tons of soil fell into the Sound. I imagine the giantess looking sidelong at the great pile of hills she’d dropped, pushing at it with her toe for a moment and then lumbering off through the waves to sit on the Swedish shore and repair her apron, abandoning her lost acres without another thought. When Hvenhild was long dead and we Danes came to settle the island, we named it after her.

I didn't want to jump right in to a description of the new location, and I didn't want to say "So I got on a boat and went to this island." After about four false starts, I hit on the idea of introducing the island location by telling the myth of its origin. I may end up cutting this paragraph, as it's not really necessary, but I like the image of Hvenhild.

Hven rises up from the waters abruptly, a flat bluff with steep white cliffs all around and ringed with dangerous, rocky beaches. There is one small harbor on the north side of the island, where a steep road angles up through a gap in the cliffs, and visitors to the island are obliged to climb up hundreds of feet to the peasant village of Tuna. Standing, finally, on the rolling plain above the cliffs one can turn and look northward to see Kronberg, seven miles distant. The castle is a brick red and coppery green smudge on the faraway shore. Hven is likewise visible from Kronberg, the cliffs a white line floating on the Sound and the bell tower of the church of St. Ibb is a dark obelisk, a solitary tombstone. Elsinore and Hven seem far apart, different lands or even different worlds.

It was not snowing the morning I crossed from Elsinore Harbor to the landing at Hven’s north shore, but nor was it a pleasant day. A low mass of gray cloud filled the heavens and the Sound was a seething, undulating thing of gray wave upon gray wave. The coastlines of Denmark and Sweden were buried under three feet of snow, as was Hven. The world looked hewn from ice, ivory and granite.

The crossing took two hours in our small boat. Marcellus had assigned two Danish soldiers as my assistants, named Cornelius and Voltemont. They played dice, drank mulled wine and complained of the cold and wet during the voyage. They complained again when there was no one at hand to unload our supplies at Hven’s wharf, and their loud complaints as we dragged our trunks, sacks and boxes up the road from the wharf to the town were doubtless audible as far away as the moon.

So that's setting, travel to the new setting, and introduction of Cornelius and Voltemont, who will provide some comic relief. The typical style of their speech follows:

“There is no inn on this island,” Cornelius said.

“Nor a tavern neither,” Voltemont said.

“We must carry our trunks two miles, over hills buried in snow and then build our own fire at Brahe’s ruin,” Cornelius said.

“There will be no dry wood.”

“There will be no dry bed.”

“There will be nothing but a hole in the ground, and we three freezing in it.”

“You men,” I said. “Have either of you been to Uraniborg since Tycho left it?”

“Nay,” they answered. Neither man had stepped foot on the island in his life.

“Go to the church and borrow a cart and oxen,” I said. “We will light a fire in Tycho’s kitchen by noon, I tell you.”

Voltemont ran to the church while Cornelius and I stood at the edge of town, stamping our feet and rubbing our arms under our fur cloaks. Tuna was a village of a few score houses built from stone and wood with roofs of thatch. There were no people about but smoke rose from the chimney of every house and we smelled pottage and bread cooking.

That's right, more setting. This time it's the village of Tuna. Tuna is small. Also, everyone is warm and snug except our three plucky travelers.

“Voltemont takes his time,” Cornelius said. “Belike he joins the priest for a meal at the fireside. He will forget his friends, who turn to ice outside.”

Cornelius complaining. Get used to that.

“Nay, here he comes.”

St. Ibb’s is a small stone chapel that is centuries old and has a bell tower the height of six men. Voltemont hurried from the church, coming forth in a cloud of steam from a narrow side door. Before the door closed I saw the great bulk of Father Maltar. He was not smiling. I had almost forgotten Father Maltar.

Introduction of Fr. Maltar. "I had almost forgotten Fr. M" is meant to be ominous.

“That ancient priest refuses us,” Voltemont said. “His cart, oxen and driver are not at the beck of every slave from Elsinore, he says.”

What ho! Conflict! Conflict is good.

“Says he?” Cornelius put a hand upon the hilt of his sword. “Well, we ought at least claim right of sanctuary in the chapel and go inside.”

“Aye,” Voltemont said. “It is warm in the church. We have missed matins, but we may be in time for dinner.”

“Enough.” I picked up my cases and walked toward the church. With each step I sank an inch into the snow and I tried to remember Hven during the summer, when the hillsides flowed under deep green carpets of long grass where sheep and cattle grazed, when crops rippled in a gentle breeze while fish schooled in the sixty linked ponds Tycho had dug west of the observatory. I tried to recall the good smell of the earth beneath the maples where I had read Copernicus in the hours after dining. These memories refused me. I had nothing but the air filled with ice and wind, a low gray sky, the noise of the waves all around and deep snow lying over the whole of the island. My ears and nose felt brittle in the cold.

All of this is to show that Horatio (the protagonist/narrator) is familiar with the island, but he thinks of it differently than he now sees it. So Horatio is not a stranger, but he will still be uncomfortable there. Discomfort is conflict, which is good.

“Bring over your packs and trunks,” I called to my assistants. “We will speak to Father Maltar.”

It was dark inside St. Ibb’s, and humid, but it was warm. Father Maltar took up most of a low bench by the stove, a young priest and a boy who I took to be a villager sat beside him on wooden stools. Maltar did not look up even when I dropped my cases into a pew with no little noise. Cornelius and Voltemont set up their own racket a moment later as they dragged two large wooden trunks over the threshold and across the flagstone floor.

Two more new characters: the young priest and the boy!

“We are on a mission for the king,” I said, stepping over to the stove. I stood beside the young priest, stretched out my hands to the fire and tried to catch Maltar’s eye. “We require your assistance.”

“So you’ve returned,” Maltar said. His voice was low and rumbled deep in his chest. He looked at the grate of the stove, as if he spoke to it and not to me. “The great man’s toad hops across the Sound and into my church once again.”

Hey, looks like Maltar and Horatio know each other and don't get along so well. We jump immediately into their conflict. Maltar is characterized almost entirely through his animosity toward Horatio, since that's the single most important role he plays in the drama.

“Brahe is not here, only the will of the king,” I said. “We serve the king. As do you, Father.”

“Brahe is dead.” Maltar groaned out the words.

“Aye, but the king lives, and we do his bidding.”

“Brahe is dead.”

“Indeed, Father. I have been tasked with removing all traces of him from Hven. You should thank me.”

“Were I a younger man, I’d thank you with a beating.”

A very old priest threatens to beat you up. What's that say about you?

“You are thankfully spared that effort, then. We only require cartage to Uraniborg.”

“I had a dream.”

“Did you dream of an ox cart, Father?”

Fr. Maltar and Horatio will continue to snark at each other.

et cetera, end of excerpt

So that's what I've done to begin the middle of my WIP, introduce new characters into the story and set the stage in a new location. The technical bit that I think you should be aware of is this: whatever you do, do it quickly. Don't waste time. Get the most important information onto the page right away, and use it to show character. The dialogue here all serves not only to move the action forward, but to show us who the people are who are speaking. Cornelius and Voltemont are buffoons. Father Maltar is not the protagonist's friend. The young priest shows himself later to be allied with Maltar. The boy will be kind to the protagonist but there's some mystery about him. Get to the important stuff first; there is plenty of time later to round out the characters if you want to.

Also, just like at the beginning of the main story back in Chapter One, it's important to build mystery and suspense. That's why you never will get the story of Horatio's previous time on the island in one neat chunk, and every bit of information you get will lead to more questions. Questions = mystery = suspense = tension and all of that keeps the reader turning pages.

This was a long post, but I didn't know any other way to show (not tell!) my possibly useful advice about the start of Second Acts. Do forgive my going on like this.

Tuesday, June 15, 2010

Keep Your Middle From Sagging

I am thinking a lot about middles of novels right now, as I am just embarking on the middle of a first draft. The middle of a book is notoriously the place where the story slackens and readers find themselves slogging along, laboring to make headway through your book, almost fighting against you to make it safely across the swamp that is the Second Act of your story.

I think that there are a couple of things that make middles sag:

1. The story is too simple and the middle 100-200 pages are, frankly, padding (as Nick Hornby says, you're just keeping the reader's left and right hands apart).

2. The story is suspended for a few hundred pages while the writer digresses into discussions of his pet subjects, which have nothing to do with the story you're reading.

3. The plot becomes episodic, one similar conflict resolution after the other, and despite the author's imaginative new dangers to throw at the hero, the story feels repetitive (and dull).

4. The plot, the characters, the story are all sort of wandering around and going nowhere in particular for 40,000 words.

Now, consider that numbers 3 and 4 are actually symptoms of number 1.

In number 3, the story becomes a long series of episodes because the writer is attempting to show growth or progress or something, and it's all just mechanics: a dramatized list to prove that the hero is ready for the climax in Act Three. Or, the author is blindly following the maxim to "put your protagonist in a tree and throw rocks at him." But it's not a story, it's just the hero doing whatever the story's equivalent of pushups is. There is no real forward motion, there's just a lot of running in place or in circles. That is rarely interesting for long, and shows that (as I claim) the story is too simple to justify its length.

In number 4, the writer has no idea what to do and has to fill in space until it's time for the climax, so (because the story is too simple) the characters just mill about waiting for the bell to ring and let them back into class, as it were.

So really there are, as I see it, only two real reasons that middles sag: the writer decides to digress and leave the story behind for some length of time, or the writer has not got a strong enough story to fill the length of a novel.

Both of these problems are problems of structure, of the way the story itself is conceived by the writer. To fix Problem Number 2, my answer is Don't Do It. Seems pretty straightforward. But then you don't have a middle of your book, and you're back to suffering from Problem Number 1.

I pause to insert the idea that another possible problem with the middle of the book is that it's simply badly written and even if the story is well-structured, the telling is not well done. That's a whole other (and larger, sadly enough) topic. So back to where I was.

Problem Number 1: The story is too simple.

I see, in my wide travels as intinerant internet reader guy, a lot of early novels that have sort of one-dimensional stories. By that I mean stories where there is a problem put before the protagonist and they doggedly push on to solve it. There is, essentially, only one thing happening in the story, and the story operates at a single level: the level of the primary action of solving the problem. This means that these stories lack depth, usually, and they also lack variety and suspense.

They lack variety because there is basically one action: the protagonist moves toward a goal and encounters resistance. Even in those books where the protagonist gets the quest at the end of Act One, gathers strength during Act Two and then has a dark night of the soul before the climax in Act Three but suffers through the epiphanic moment to make the triumph possible (that is, books which follow the Campbellian Hero's Transformative Journey), you still have just the one real action, of the hero implacably moving against the antagonist. You throw in subplots all you like, you've still got a one-dimensional story going.

These stories lack suspense because the meaning of the actions are generally clear by the beginning of the Second Act. Yes, the story question ("will Luke destroy the Death Star and become part of the Rebel Alliance and clear up that skin condition?") remains unanswered, but if that's the only question the reader has, the suspense will turn to mere waiting during that long middle stretch. There is no mystery behind the story question, no deeper unknowns than the outcome of the primary conflict. That amount of suspense is not enough to carry a whole book.

What you need, then, is more variety to your story, more mystery and more layers of suspense. How do you do this? By making the story more complex. I am going to suggest a general framework for this, and it's a very old and reliable framework that's been around for centuries.

I call it the Inner and Outer Conflict Structure, and I have come to lean heavily on it because it works, it's flexible, it's generally invisible to the reader and it's applicable to all genres of fiction including literary.

It works like this:

You already have a story with a conflict (if you don't, then you don't have a story and this isn't the post for you). This conflict is either an external (Outer) conflict (Luke versus the Empire) or an internal (Inner) conflict (Gogol versus his idea of his parent's expectations of him, which is to say, of his expectations of himself). What you need to do is figure out which type of conflict you have in your story, and then come up with a conflict of the other type. That is, if your story has an outer conflict (George must kill the dragon), you need to find an inner conflict (George's father was saved by a dragon and George is, you know, morally opposed to killing dragons because he was raised with stories of the benevolence of dragons even though he has never, it must be said, personally met a dragon).

So you have your inner and outer conflicts. What you do then is build a three-part structure where the outer parts (Act One and Act Three) are the outer conflict, and the middle of the story (Act Two, natch) is the inner conflict. Like so:

Act One: George versus dragon (unresolved)

Act Two: George versus his feelings about dragons (conflict resolved during this act)

Act Three: George versus dragon (resolved)

When Act One ends, the outer conflict is still unresolved, and the reader doesn't know which way things will go. This is the unanswered story question, and is the primary suspense that will go stale if that's all you've got. So Act Two introduces the inner conflict, which is related to the outer conflict. This is variety, and the new story question adds more suspense for the reader. Also, the inner conflict is often more interesting to the reader than the outer conflict, which makes the reader perk up her ears and become more interested in your story as the middle of the book progresses. There's no reader boredom because there is a whole miniature drama in the center of your story, and this inner conflict must be resolved before the outer conflict can be. George can't commit to battle (or not battle) against the dragon until he works out how he feels about dragons in real life, once he has some exposure to the ways of real dragons. If he decides that dragons are as he thought, peaceful but misunderstood beings, Act Three isn't going to be a bloodbath. If he decides that dragons are actually dumb, violent beasts and his father made up the story about being saved by a dragon to hide a crime he'd committed, then maybe George will sharpen his lance and go slay a large reptile. Either way, the story has become much more complex, much deeper, possibly more meaningful and certainly it will be easier to write the middle when there's really a middle to be written.

If this is all obvs to most of you, then I apologize. If this is new stuff, or if you disagree with/see flaws in this version of the 3-Act structure, say so. If you have a different, but widely-applicable way of structuring your stories that defeats the devil of sagging middles, please share it!

Friday, April 9, 2010

Pizza Structure



My new book doesn't have chapters. It is divided, instead, into sections. Four of them, that I've planned so far. It has been an interesting thing, too, to work this way. I feel like I've suddenly been freed from a prison I didn't know existed around me.

Chapters - Blah!

Sections - Getting better

Scenes - YES

I believe structure plays a huge part in the way our creative brain churns out a story. With the three complete novels I have written so far, all have been split into chapters. I wrote within the confines of these chapters, and I allowed those confines to control how I treated POV, plot structure, scene structure, even how I ultimately shaped my characters. It feels like my books are split up into these little boxes, and that can be a good and a bad thing.

You can stack boxes into different shapes. After all, pixels are just little squares.

I know several writers who don't write within chapters at all. They just write and write and write until they have their 80 or 100,000 words, and then maybe they'll split the book up into chapters. Or leave it.

With this new work of mine, I feel freer. I'm writing the book by scenes, and each one can dramatically vary in length and it doesn't feel like an issue at all. When I write in chapters, I tend to slice the book up like a pizza, trying to get each slice the same size. It's my organized nature that does this, and so freeing myself of the pizza cutter altogether, I'm just picking off the toppings and piling them up on my plate, or maybe I'll just cut the pizza in two, or just eat it all with a fork.

I think sometimes we let the structure of our writing get in the way of our writing. We think of pizza and one image comes to mind - a perfect circle cut into triangles. I've enjoyed experimenting lately, finding new ways to compose a narrative. It is thrilling to see what this does for my characters, how it shapes them different from if I was writing in a stricter structure. I'm literally trying to think outside the box, and even if in the end, the book still feels structured in the traditional manner, I'll know that it didn't begin that way.

How do you structure your WIPs as you begin them? Do you always stick with chapters? Do you think this restricts elements of your characters and narrative?

Tuesday, December 22, 2009

Making A Scene

I am currently working on the middle section (or Act Two, if you use the three-act structure) of my novel-in-progress, Cocke & Bull. This section essentially does one thing: it leads up to a climactic emotional moment between two of the main characters to resolve a conflict that began at the end of Act One, the resolution of which conflict will lead to the climax in Act Three which deals with the conflict that started off the story. If that makes no sense, imagine the story as a conflict/climax within another conflict/climax. Conflict 1 is the story's outer problem, and Conflict 2 is the story's inner problem:

Act 1:
CONFLICT 1 begins
CONFLICT 2 begins
Act 2:
CONFLICT 2 climaxes
Act 3:
CONFLICT 1 climaxes

I'm very happy with this overall structure and I may just use it for every novel I write from here on out. Unless I don't. I'm capricious that way. Anyway.

The emotional climax at the end of Act 2 is a big moment in the story, making the climax in Act 3 inevitable. So I need to have this emotional climax really stand out and I have to lead into it well. I'm going to use an idea that I got from reading "The Art of Subtext" by Charles Baxter. In this book, Baxter talks about how in real life, most people avoid "making a scene." Most people bite back their strongest emotions and try hard not to bare their souls. There are things we would love to do, but we do not do them because such things are not done or because the price we'd pay for these acts would be too high.

For example, imagine two men. Let's call them Andy and Tom and let's say they work together in a large office. Tom's the sort of guy who objectifies women and is obsessed with the size of their breasts. In fact, one of his habits is to whisper his estimate of women's breast sizes to Andy whenever they're together. "Check it out," Tom will say. "38D!" He also gives nicknames to the women who work in the office with him and Andy. These nicknames all have to do with the women's breasts and are, of course, private and only used by Tom when speaking to Andy.

Andy is uncomfortable with this, but when he was first getting to know Tom, he said nothing about this behavior and subsequently it's only gotten worse as time goes on and now what Andy wants is for Tom to just leave him alone. But it's awkward. They work together on some of the same projects, and frankly Andy isn't sure how to bring the subject and his objections up. It's outside of his comfort zone. He doesn't want to make a scene at the office.

If this were the basis of a story, the climax of it would be Andy, finally unable to hold his tongue, busting out with a highly-emotional demand that Tom shut up about their coworkers' physiques and, you know, we're just not going to be friends anymore so just leave me alone. Andy will let out all this bottled-up frustration and embarrassment, unleashing it on Tom in a compressed moment, preferably in a too-small physical space like an elevator or a supply room or something, because small spaces increase emotional force. What happens after the climax will depend on if Andy or Tom is the protagonist, and that's not really the point here.

Leading up to the moment when Andy makes a scene, we'll need scenes that increase the tension between him and Tom, with Andy biting back words and being increasingly embarrassed by the whole thing. We'll have to make it clear that the one thing Andy would love to do is tell Tom to shut up (hey, maybe Tom is Andy's superior or team leader or something?), and make it clear that Andy would never do this, and then have Andy do it anyway. That's drama, folks. The conflict and tension increase over time and then are paid off in the climax.

So in my own book, I've got a character who knows that the real solution to the inner conflict of the story (Conflict 2 in my chart above) is an act that he will no way never commit. So what I'm doing now is having him fight against his urge to commit that act, putting in scenes where it will look as if that act won't be necessary and then...oh, gosh I guess it will be after all. He's faced with the decision to solve his problem and pay a very high price, or not solve his problem and live with a misery more-or-less of his own making (because the drama is better when the crisis has been brought about by the character himself).

Anyway, I just wanted to talk about this idea of "making a scene" and how the common-enough situation of demonstrating admirable restraint when we'd rather not can be the model for larger emotional movements in novels. It's a new way of seeing the dramatic arc for me, so I'm sharing. Also, this is my way of recommending Baxter's book: The Art of Subtext: Beyond Plot.

Tuesday, December 8, 2009

Classic Plot Structure (3-Act Structure)

One of the cool things about the software we use to track visitor statistics for the Literary Lab is the ability to see what search terms were used to lead visitors here. A lot of people find us by entering "classic plot structure" into Google or whatever search engine. While Davin has written a post about the classic plot structure that you should by all means go read, it's more a commentary than a definition, so I'd like to take a few minutes and talk about the basics of the classic plot structure, which I'll henceforth refer to as the Three-Act Structure.

In brief, the Three-Act Structure is a framework to arrange story elements into a narrative, with pacing and major plot points as goals, a template into which you can pour your characters and events to give it shape. Narratives are constructed in three consecutive sections, or acts. The author has a distinct job to do in each of the three acts. The basic formula is:

Act One
Exposition, set-up, inciting incident. Hero is given a goal.

Act Two
The middle. The hero tries and fails to achieve goal.

Act Three
The climax and resolution. Hero makes last attempt to achieve goal and succeeds at last or fails forever.

(These are really sweeping generalizations, I know. But I didn't invent the classic plot structure, I just report on it.)

More detail:

In Act One, we see the hero (a word I use because it's shorter than "protagonist" and I'm less likely to misspell it) in his daily life, whatever and wherever that is. The hero has some internal need, usually, that can't be met in his daily life. Then, something happens to knock the hero off the rails of his daily life. He's been given a problem or a quest. Act One ends when the hero decides to solve the problem or take up the quest. The author's job in Act One is to establish the crisis in the hero's life that the hero must solve. There are lots of tasks involved in doing this job.

In Act Two, the hero struggles to solve the problem or complete the quest. He appears to be having success, though it doesn't come easy. The antagonist/villain fights against him indirectly. At the end of Act Two, the hero, who has been successful all this time, suffers a major defeat at the hands of the antagonist. Usually this defeat is caused by the hero's internal need which he has yet to deal with. This is the hero's lowest point, morally/physically/spiritually. All seems lost.

Lots of times, Act Two actually consists of the hero solving the problem that came up at the end of Act One, only to discover that it wasn't his real problem at all, and that he's got bigger fish to fry, which frying takes place in Act Three at the climax. The author's job in Act Two is to keep the action and the conflict rising toward the climax, and to show the hero attempting to re-establish equilibrium in his world (that is, achieve his goal). Lots of tasks involved in this job, too.

In Act Three, the hero bucks up and decides that he can go on, usually with greater resolve because yes, he's solved his inner problem that was holding him back. Or, he's realized he has this inner problem and is going to confront that. Either way, off he goes to fight the big fight at the Climax, after which there is a short denoument. The fight, of course, can be internal or metaphorical. Or fought with laser cannons; it's up to you. Your job, as author, is to resolve the crisis one way or another (or show how it cannot be resolved) in a manner that is believable within the rules of the story. The climax must seem both surprising and inevitable (except for those stories where you see it coming the whole time and hope the hero will avoid it). Again, lots of tasks are necessary to do this job.

So you have rising action, rising conflict, the possibility of total defeat and then even more action and conflict and then climax. Sometimes the hero dies or is otherwise defeated at the climax. Anyway, that's your classic Three-Act Structure in a nutshell. It gets more complicated as you layer on subplots and themes and other story elements, but you get the idea.

Another way of thinking about the Three-Act Structure is in terms of Action/Reaction/Results. Or perhaps as Problem/False Solution/True Solution. Or Crisis/Loss of Identity/Rebirth. Or At Home/This Is Not My Beautiful House/This Is My New House. Really, the different stories you can tell in this three-part structure are endless.

Now, is the Three-Act Structure of any use to a writer? I think very loosely in these terms when I do my outlining before I've begun actually writing. I also have begun lately thinking in terms of the Action/Reaction/Results 3-part structure when writing chapters and scenes, which gives a nice feeling of controlled flow to the writing. But I do think it's easy to fall into the trap of writing to a formula, which generally results in stories that are predictable, melodramatic, and otherwise suck.

The idea of the Three-Act Structure grew out of Aristotle's basic structure (which interested parties can read about in his Poetics):

Beginning, Middle, End

But Greek plays had only one act and don't divide nicely into the Three-Act template. Roman plays had five acts (as did the plays of Shakespeare and the Elizabethans), but that was to allow for intermissions and snack breaks. Ancient plays were longer than our two-hour movies so there were practical matters to which playwrights and theaters had to attend.

What I think is as useful for a story template as the Three-Act Structure is to divide the story into two types of action: the action that creates the problem, and the action that resolves the problem. This is how real conflict works in real life. You might try writing down the action that creates the problem and then the action that resolves it, and then break those actions down into scenes and see what you've got.

So while the Three-Act Structure might be a helpful organizing tool, I caution anyone against tying themselves too tightly to it. Stories are about who we are and how we solve problems, and I suggest we think in those terms and not so much in terms of "I haven't raised the stakes for my protagonist" or "I need to use my antagonist's minions in this act."

Beginning, middle and end. Start with the end, if you know enough about your story to know who your characters are. Who is he at the end of the story? Then tell us how and why he got there. That is what you are telling us. That is a story.

Friday, November 6, 2009

Some Thoughts on First Acts

If you are basing your novel in any way on the traditional three-act structure, I think there are certain things you should think about when writing your first act. This applies to stories where the protagonist is goal-oriented and must work against some sort of active antagonist; other types of stories will require other types of structures, I'm sure.

In many of the unpublished mss I'm privileged to read, the first act isn't very strong. The ideas are there, the conflict is there, but there's just not enough of it. I don't like to hand out formulas or recipes for writing, but I do think that writers should have tools they can use (and no, I'm not prepared to distinguish between "formulas" and "tools" today), so I offer up these thoughts.

1. Your first act should end with the literary equivalent of a train wreck. What I mean by that is that you should be moving constantly toward a collision of conflicting needs and desires that results in the protagonist having to make a major life decision and consequently act upon that decision.

2. Your protagonist should have a clearly-defined goal. Often this is a wrong-headed goal based on a misunderstanding the protagonist has about the world. The train wreck at the end of the first act will leave the protagonist with a better picture of reality and possibly a new or modified goal to which he must direct his life and actions.

3. Your antagonist should have a clearly-defined goal. This isn't necessarily something Evil, but it has to set your antagonist and your protagonist on intersecting paths that will result in the above-mentioned train wreck. Generally, the train wreck leaves your antagonist stronger, and his goals won't change at all; he'll just keep moving in the direction of his goals and continue acting upon his desires and needs.

4. Your support characters should have clearly-defined goals. These are usually goals that are supported by or aligned loosely with the protagonist or the antagonist. Know which is which. Your protagonist could be allied with people who are actually working against his goals, even if not deliberately or with Evil Intent. Their lives will also be affected by the train wreck in some way. Some of them will change their goals, others won't, but all of them will continue to act to achieve their goals.

5. The story must MOVE toward the train wreck, and things have to REMAIN IN ACTION. Think of your first act as the opening of a game of chess, where each side is closing in on the other, and pieces are constantly being moved forward, some pieces captured and removed from the game as it progresses. Often the protagonist won't even know that there is another player opposite him, killing his pawns and planning to put his king in checkmate. The point is, the characters are all active and constantly moving forward.

You are, in a traditional first act of a traditional three-act structure, moving toward a point where all of these conflicting courses crash into each other with a big bang, from which the rest of the story will spin away toward the climax.

Your job is therefore to:

Keep your characters moving toward goals
Let your readers know what these goals are
Let your readers see what the conflicts are
Let your readers know what is at stake for each character
Let your reader see the train wreck coming before your protagonist sees it
Make sure all the motivations are plausible and clear


I do find myself thinking in terms of either a train wreck between locomotives racing toward each other on the same track, or a street intersection with two or more cars all speeding to a messy crash. Don't get me wrong; the pace of the story does not have to be breakneck. But you do need to set forces in opposition and have them collide.

The most effective way to do this is not, surprisingly, through plot but through character. What happens to people is not nearly as interesting as what people are trying to do. This is a very important distinction. Don't let your plot push the protagonist; have the plot result from the protagonist pushing against life. Agents, editors and, yes, readers generally aren't interested in characters who are reactive, who get pushed around by life. You might think that this sort of victimhood will make your characters sympathetic, and you may be right, but you will probably be wrong if you think that will make them compelling to readers. So think of the train wreck you'll be creating as a collision of characters and goals, not as the meeting up of plot strands, okay?

Sorry about all the italics. I got carried away.

Note: I am currently on vacation, so I won't be able to reply to any comments on this post. Hopefully Michelle and Davin can pick up the slack for me. Apologies all around. Also: someone needs to remind me at some point that I want to write about beginnings of stories, Chekhov's gun and how the two can work together to give a writer story options.

Tuesday, October 13, 2009

No, Let Me Explain That

One of the biggest issues writers struggle with is clarity of structure, telling a book-length story that makes sense all the way through. Just writing a straightforward narrative from a single POV in a more-or-less unbroken span of time is hard enough. The further your storytelling method gets from that, by shifting points of view, changing timelines and settings, mixing narrative styles and the like, the less clear the narrative becomes to your reader, and the more careful we writers must be to make certain our readers can follow us along. Unless, of course, your intent is to confuse or bemuse your reader, in which case you should ignore the remains of this post. But let's assume you want your narrative to be completely comprehensible to your reader, and talk about some issues that affect clarity.

First issue: The writer is unsure of his intent. I know that in my own writing, there have been passages where even I'm not able to say exactly what is going on. A scene or bit of dialogue is vague and while it seems important, nobody can point out why. This happens when I don't quite know what I want to happen. I know that I need some kind of scene there, but I don't know exactly what that scene should be, so I put in a sort of placeholder and hope it all becomes clear later on. Scenes like this are not only useless, because they add nothing to the story, they in fact do harm by baffling your reader and possibly putting them to sleep as you ask them to tread water or run in place for a while as you think about your story and then move on.

Second issue: The writer forgets that the reader is not a mindreader. This is what happens when the writer makes some sort of shift in the way the story is being told and forgets to tell the reader the shift has taken place. For example, you change POVs with each chapter or several chapters, and you don't bother to show right away that the POV has changed. The reader is suddenly in the land of "Huh? What the hell is going on?" That can be cool if you're going for that effect, but if you're not, then pay attention to the clues you give (or don't) to the reader.

Third issue: The writer puts in vague transitional devices. This is similar to the second issue, but the writer thinks she has warned the reader that the narrative has switched from, say, first-person action in the "story present" to journal entries or letters or something else. Often this is accompanied by a change in POV or voice or verb tense, but sometimes not. It can look, to a reader who hasn't been warned that he's now reading a diary instead of being told a story by a narrator, like nothing more than sloppy writing.

The second and third issues frequently crop up when we're trying to be subtle and not hit our readers over the heads with big signposts saying "POV SHIFT HERE." One thing I've learned is that what we think is subtle is often merely invisible or nonexistant to readers, and what we think is heavy-handed is often not. Because we are so familiar with the story, we sometimes lack the critical distance to know the difference. This is why trusted readers are important.

So, the big lessons here:

1. Know what you mean to say, and say it. If you have to explain it to a reader outside their reading, the words on the page don't work and have to be rewritten.

2. The more clever you are with structure, the greater your chance of losing your reader, so be prepared to do extra work clarifying what's going on. Books that shift POVs often have chapter titles with the POV character's name for this reason.

3. The more literary devices you employ, such as journals, letters, found books and the like, the more work you have to do to set those passages off from the rest of the narrative.

What's the best way to delineate between these changes in structural elements? Contrast. If your POV characters all sound the same, why are you bothering? If your narrator's journal entries sound like her narration, what's the difference or the point? Don't just hijack someone's storytelling methods because they were cool in his book; make sure they have an actual function in your own book, and think in terms of function and not of coolness value. If it doesn't make sense, it is nonsense, right?

Tuesday, September 22, 2009

Making a Scene

I am a firm believer that the basic building block of a story is The Scene, and that stories are most strongly told when composed of scenes. I am always surprised when I see a writer say that they aren't sure what, exactly, a scene is.

A scene, in my opinion, meets five criteria:

1. It is dramatized, not summarized.
2. It takes place in the "story present," seeming to happen in real time for the reader.
3. It has a beginning, middle and end and is clearly set apart from the surrounding prose.
4. It is a single, self-contained event in a single, discrete location.
5. The situation for the characters is different at the end of the passage than it was at the beginning.

Let's look at a passage that advances the story:

My journey seemed tedious--very tedious: fifty miles one day, a night spent at an inn; fifty miles the next day. During the first twelve hours I thought of Mrs. Reed in her last moments; I saw her disfigured and discoloured face, and heard her strangely altered voice. I mused on the funeral day, the coffin, the hearse, the black train of tenants and servants--few was the number of relatives--the gaping vault, the silent church, the solemn service. Then I thought of Eliza and Georgiana; I beheld one the cynosure of a ball-room, the other the inmate of a convent cell; and I dwelt on and analysed their separate peculiarities of person and character. The evening arrival at the great town of--scattered these thoughts; night gave them quite another turn: laid down on my traveller's bed, I left reminiscence for anticipation.

This passage moves the plot along. You could say there is action even: the narrator is traveling across country, and we see her thoughts along the way. But it is not a scene, because:

1. It is not dramatized, but is a summary of action.
2. It does not take place in the "story present," and fails to happen in "real time" for the reader.
3. It has no dramatic arc (no beginning, middle and end) and is not set apart from the surrounding prose.
4. It is not a single, self-contained event, but is part of a longer summary of events, nor is it in a single, discrete location.
5. The situation for the characters is the same at the end of the passage as it was at the beginning, except that the narrator has apparently traveled and spent a night or two at an inn.

Plot is advanced, but that's not enough to make this passage a scene. It is, rather, a transitional passage between scenes. It's connective tissue, as it were.

Here is another passage from a page or so after the one above:

"Hillo!" he cries; and he puts up his book and his pencil. "There you are! Come on, if you please."

I suppose I do come on; though in what fashion I know not; being scarcely cognisant of my movements, and solicitous only to appear calm; and, above all, to control the working muscles of my face--which I feel rebel insolently against my will, and struggle to express what I had resolved to conceal. But I have a veil--it is down: I may make shift yet to behave with decent composure.

"And this is Jane? Are you coming from Millcote, and on foot? Yes--just one of your tricks: not to send for a carriage, and come clattering over street and road like a common mortal, but to steal into the vicinage of your home along with twilight, just as if you were a dream or a shade. What the deuce have you done with yourself this last month?"

"I have been with my aunt, sir, who is dead."

"A true Janian reply! Good angels be my guard! She comes from the other world--from the abode of people who are dead; and tells me so when she meets me alone here in the gloaming! If I dared, I'd touch you, to see if you are substance or shadow, you elf!--but I'd as soon offer to take hold of a blue ignis fatuus light in a marsh. Truant! truant!" he added, when he had paused an instant. "Absent from me a whole month, and forgetting me quite, I'll be sworn!"

His last words were balm: they seemed to imply that it imported something to him whether I forgot him or not. And he had spoken of Thornfield as my home--would that it were my home!

He did not leave the stile, and I hardly liked to ask to go by. I inquired soon if he had not been to London.

"Yes; I suppose you found that out by second-sight."

"Mrs. Fairfax told me in a letter."

"And did she inform you what I went to do?"

"Oh, yes, sir! Everybody knew your errand."

"You must see the carriage, Jane, and tell me if you don't think it will suit Mrs. Rochester exactly; and whether she won't look like Queen Boadicea, leaning back against those purple cushions. I wish, Jane, I were a trifle better adapted to match with her externally. Tell me now, fairy as you are--can't you give me a charm, or a philter, or something of that sort, to make me a handsome man?"

"It would be past the power of magic, sir;" and, in thought, I added, "A loving eye is all the charm needed: to such you are handsome enough; or rather your sternness has a power beyond beauty."

"Pass, Janet," said he, making room for me to cross the stile: "go up home, and stay your weary little wandering feet at a friend's threshold."

I got over the stile without a word, and meant to leave him calmly. An impulse held me fast--a force turned me round.

"Thank you, Mr. Rochester, for your great kindness. I am strangely glad to get back again to you: and wherever you are is my home--my only home."


This passage meets all the criteria for a scene:

1. It is dramatized, not summarized.
2. It takes place in the "story present," seeming to happen in real time for the reader.
3. It has a beginning, middle and end and is clearly set apart from the surrounding prose.
4. It is a single, self-contained event, in a single, discrete location.
5. The situation for the characters is different at the end of the passage than it was at the beginning.

Think of a scene as real physical action that you can imagine, that's written to be read at more or less the same pace as it would happen in real life.

When I put together stories (no matter of what length), I write in scenes. I make a list (at least in my head) of all the events that must happen in the story, and how these events effect the characters, and then I make a list of scenes that will tell this story by encompassing the necessary plot events and character events into dramatic action. Those scenes make up the bulk of the writing, and everything else is transitional passage or the minimum of exposition that I can get away with. If I'm feeling poetic, I might add in a page or two about eel fishing, but in general, my stories and novels are sequences of scenes.

Do you make an effort to write in scenes? If so, how do you define "scene?" If not, why not? What is the basic building block of your stories?

Friday, September 18, 2009

Emotional Tension

Sometimes we write passages or whole stories that fail to engage our readers emotionally, even though these passages or stories engage our own emotions. We fuss about with the plot, the dialog, the structure of the scenes but sometimes we still get nothing out of our readers. I believe one common cause of this is lack of emotional tension for the characters themselves.

A mistake I made when I began writing was to forget that I knew a lot more about the characters than the reader did; I carry around a whole world in my head, and I know what my characters think and feel about everything that happens to them. Sometimes I didn't bother putting any of that on the page. No matter how high the drama of their situation, my characters didn't seem emotionally invested in their own story. They didn't react to events in their own lives.

This is an easy mistake to make when writing as we balance plot, theme, setting, character and pace over the span of tens of thousands of words. It's an even easier mistake to make when we revise scenes. We put our characters into novel situations, hair-raising danger or whatever, but we forget to let our characters be alive within those situations. I just found a scene in my own book where a character gets a piece of very bad news, but her reaction is neutral when it should be almost violent. I was too concerned with writing flowing action in the scene to pay attention to how she felt about that action.

A good scene should be a complete drama in miniature. It should have a beginning, middle and end, and there should be an emotional arc for at least one character. The scene should increase the tension for someone, or release the tension for someone. Either way, someone's emotional state has to change. If your characters don't feel anything, neither will your reader. If nothing has changed for your character by the end of a scene, your reader will also be unmoved. Even if you've moved the plot along.

This also means that your characters must be emotionally invested in the outcome of both the main story, and of each plot point along the way. What happens must matter to them. And we have to show readers that this stuff matters to our characters, and how our characters are affected by the events all through the story. Otherwise you have flat characters that your readers won't follow along on the ride.

One way to show increased/resolved emotional tension is to use a technique called "scene and sequel," which means that after a significant action, characters react. Action and reaction. Does a scene leave a character angry? Show it. Does a scene leave a character relieved, or sad, or confused, or defeated, or triumphantly evil? I suggest that you go through your stories, scene-by-scene, and after something happens, ask yourself how the involved characters feel about what just happened. Give them the opportunity to react to the events. Raise and lower the emotional tension as appropriate.

Yesterday Michelle talked about character motivation, and how essential it is for writers to know the answers to the questions:

What do our characters want to happen?
Why?
What are they doing about it?
How will they feel if it does/doesn't happen?

All of these questions come into play in every scene you write. Think especially about the last of these questions, and how your characters (not just your protagonist, but your antagonist and support characters, too) will react to the actions of your story as they find themselves closer to or farther from their goals at the end of scenes. Show those reactions, or your readers will react with a yawn and a search for something else to read!

Friday, July 24, 2009

Just then, the protagonist tripped...

I had a fascinating but lengthy prologue to this article which I've just cut because, you know, it was just me prolixing on about how cool I am. So let's just get to the goods instead.

Sometimes writers get stuck in the middle of their narratives. The story develops too quickly, for example, and your protagonist's journey from inciting incident to climax is over before you know it and your book is only 50,000 words long. Or, you simply don't know what to do with your characters on the way through Act Two (if you think in terms of a three-act structure). Anyway, there are three basic things you can do to make your plot more interesting during the middle of the story (and, incidentally, up your word count).*

The basic idea is to interrupt your protagonist's journey toward the climax. I will, alas, use examples from "Star Wars" because I doubt most of us share the same reading habits and references. Also, I get to be a geeky SW fan. Live with it.

Complications: These are things, people, or events that slow the protagonist's movement toward their goal. Luke being told by his uncle that he has to wait another year before applying to the Academy and leaving Tatooine is a complication.

Roadblocks: These are things, people, or events that stop the protagonist in his tracks. The Millenium Falcon being snagged by the Death Star is a roadblock.

Reversals: These are things, people, or events that turn the story on its head; the protagonist changes his worldview, his direction and often his goal. Luke's family being killed by the Imperial forces is a reversal.

All of these things are essentially problems the protagonist must solve. You can simply make them things that have happened to the protagonist, but that would be wrong. Why? Because a passive character to whom things happen but who does not himself act is boring. Rule Number One is that you do not bore your reader.

So, if your story is lagging, you give your protagonist problems to solve. Beginning writers tend to just throw these things at their characters in a long episodic middle stretch, and none of the problems are connected to the story as a whole. That's bad. All of your plot complications, roadblocks and reversals should grow out of things, persons or events that have appeared earlier in the story. Minor conflicts from Act One can loop back around and reappear as major conflicts in Act Two. This will give your story balance and shape and internal consistency.

Also, you might consider giving complications to your antagonist. How your villain (to sort of continue Michelle's post of yesterday about complex antagonists) deals with adversity might give us clues about his motivations and weaknesses, possibly foreshadowing the climax. Foreshadowing is teh roxor. Don't forget to use it. See above comments about events/items/people looping back around into the story.

So that's my advice today: if you find your story lagging or rambling in the middle, try to focus on the protagonist's goals. Point him at his goals and them have him trip, fall into a hole, come against a wall, or realize his basic assumptions are all wrong. Even if none of these ideas make it into your story, they could be useful brainstorming prompts that end up giving you ideas better than anything I could possibly offer.

*Does that all sound too formulaic and calculating and anti-art? I try to give pragmatic, nuts-and-bolts technical advice here. I don't know about art.