Tag Archives: jack bickham

More structural self-editing resources

Yesterday I shared my presentation on structural self-editing from the 2014 LDStorymakers conference, and today I’m sharing some more resources on the subject—enough to keep you busy for quite a while!

Books I referenced

Blog posts

Other resources

Seven-point story structure by Dan Wells on YouTube—each video is about 10 minutes

What are your favorite resources on story structure?

Tomorrow: my presentation on gesture crutches!

 

Secret sauce: filter words

This entry is part 15 of 16 in the series Spilling the secret sauce

When you see a building under construction, your eyes are naturally drawn not to the building, but to the latticework of metal encasing its facade. In writing, the same attention to certain words and phrases—in this case “head words”—creates the same effect.

Sometimes we use phrases like “he thought” or “she knew” to reinforce the POV character’s connection with the thoughts in narration. But instead of drawing our readers’ attention to the character’s thoughts, too many of these phrases can draw attention to that scaffolding—the words that encase the character’s thoughts. Remember the example we used early on of watching a character looking out the window versus seeing the view ourselves?

This passage from the otherwise excellent Scene & Structure by Jack Bickham exemplifies the thinking behind this problem:

Failure to use constructions that show viewpoint is quite common, and, we can be thankful easy to fix. . . .

Consider the following statements:

The cold wind blew harder.
A gunshot rang out.
It was terrifying.

These are fine observations, but in none of them do we know where the viewpoint is. Ordinarily you should recast such statements to emphasize the viewpoint, thus:


She felt the cold wind blow harder.
He heard a gunshot ring out.
It was terrifying, she thought. Or:
Terror crept through her.(89)

I can’t say whether it’s just publishing trends or the version of deep POV that’s au courant, but today, publishing trends have moved far, far away from his “fixes” (other than the last one, of course). Today, such “scaffold fixes” smack of telling instead of showing.

Showing versus telling

By emphasizing the viewpoint character in these sentences, we are doing exactly what Bickham wants us to—show the viewpoint. However, we’re telling what that character is seeing/feeling/hearing.

The question readers should be asking upon reading a sentence like Bickham’s first examples isn’t “Who’s seeing/feeling/hearing this?” It’s “What’s next?”

Naturally, these examples are pretty much begging for this kind of scaffolding—because they’re in isolation. If you start your scene with a sentence like any of these (without a clear POV, that is), then yes, readers could be confused whose POV you’re in. You must establish the viewpoint character early on—but not by telling.

The cold wind blew harder and Jack flipped up the collar of his coat. He hated the winter.
A gunshot rang out. Maria flung herself under the nearest car before the terror could even register.

If you establish the POV at the beginning of the scene, and continue to show your character’s thoughts throughout the scene, simple declarations and observations of the world around him don’t require you, the author, to tell us that the POV character is the one seeing/feeling/tasting, etc. Cutting back the unnecessary scaffolding lets the elegant architecture of the sights and senses of your story shine through.

Sometimes, however, these head words are absolutely necessary: they can add important shades of meaning. “She realized he was wrong” is different from “she knew he was wrong,” “she thought he was wrong” and “he was wrong.” Use head words when they add necessary shades of meaning, and take them out when they don’t. (One of my biggest pet peeves: “wonder.” I will almost always recommend writing “How would he survive?” instead of “She wondered how he would survive.”)

What do you think? Do you notice “scaffolding” or head words when you’re reading? Do you try to avoid them while writing? Or do you see them as a useful tool to establish viewpoint?

Photo credits: scaffolding—Paula Navarro; Colosseum—Hannah Di Yanni

Secret sauce: Behold, the scene chart!

This entry is part 7 of 16 in the series Spilling the secret sauce

There are probably as many ways to edit a story as there are to write one. One of my favorite tools has been a scene chart, inspired by a post on Edittorrent.

The original post suggested creating index cards for each scene, listing a number of important features—everything from where and when the scene is set, to first and last lines, to “promises” made to the reader, to important details like descriptions. Then you could move the index cards around to resequence events or scenes, or play with the story without hurting your MS.

Like many of the commentators on the post, however, I used a spreadsheet to do this in a very small space. I also combined this with probably the most important thing I learned from Jack Bickham’s Scene & Structure—the structure of a scene and the importance of a scene goal—for the character, not just me as a writer. (More on scene goals next week!)

So here’s an example of the kind of scene chart I used, partially filled in for an imaginary story (anybody recognize the plot? Hint: it’s from an old card game). I didn’t use all of these columns myself (and if any of them aren’t clear, feel free to ask what I mean).

I liked this technique so well, I’ve used it on almost everything I’ve written since the first time I used it, more than four years ago. I can use it to make sure the vital elements of every scene are present.

Checking for these elements is a very powerful tool. It makes sure that:

  • Each scene is vital to your story
  • Each scene has direction and purpose
  • Each scene keeps your reader engaged and interested
  • The story is consistent in its details
  • There are no loose threads or forgotten promises

We’ll talk more about how the scene chart helps with some of these elements over the next couple weeks.

What do you think? Do you use a form of scene charts? What’s your favorite high-level editing technique?

Photo credit: Aaron Brown

Secret sauce: scene structure

This entry is part 6 of 16 in the series Spilling the secret sauce

Just like stories have structure, scenes have a specific structure, too. Story structure can help make sure your scenes matter; scene structure helps your scenes make sense. Your overall story might be on course, but if your scenes meander, readers will still feel lost.

Scene structure

In his aptly-named book Scene & Structure, Jack Bickham delves into the scene structure proposed by Dwight Swain. The basic structure of any scene, Bickham says, is Goal – Conflict – Disaster.

The Goal is the POV character’s goal at the start of the scene, for just that scene. (More about this later in the series!) The Conflict is what happens as the character pursues the Goal and meets resistance—dialogue, movement, pursuit, etc. The Conflict builds to the climax of the scene—the Disaster, when the character’s goal is frustrated.

Sequel structure

A scene is followed by a sequel, which has its own structure. Bickham’s structure for the sequel is Emotion – Thought – Decision – Action (which leads to another scene). The Emotion is the initial response to the events of the scene and its Disaster. When the character moves past the initial emotion, they think through the events, their response and their options in the Thought phase. This ultimately leads to a Decision, which takes the character to another Action—setting a goal for them.

Not all the steps of the sequel are necessary. In fact, the sequel itself might not be necessary—depends on the pacing and whether the emotional reaction constitutes a change. I often find my sequels very brief, or rolled into the beginning of the next scene.

How does all this help make your story stronger?

Scene structure is a basic good practice. Like I said at the beginning, it keeps scenes from wandering, and our readers’ attention spans from doing the same. It clues readers in from the beginning that the following does impact the story, keeping them hooked through the action.

As Bickham says it, the scene goal poses a question—will s/he get what he’s after? The character then pursues that goal until the disaster answers the question, most often with either “yes, but(she achieves her intermediate goal, but a larger goal might have to be sacrificed) or “no, and furthermore(not only does he not accomplish what he wanted, but now there are more problems!).

Our sequels motivate the next action. If you need a character do to something that might seem crazy next, the sequel is the place to give him or her a good reason, and to show the thought process, setting up the next goal and action. This pattern makes our scenes causally linked (instead of casually linked)—creating a plot instead of a sequence of events.

Believe it or not, this pattern can become so ingrained that it’s second nature. You still want to check to make sure you have the basics (more on that next week), but scene structure is so prevalent in modern literature that once you notice it, it’s easy to mimic, even on a subconscious level.

What do you think? How does the structure of scenes and sequels influence your writing? Come share!

Photo by Tony Case

What’s your favorite “macro” editing technique?

There are probably as many ways to edit a story as there are to write one. Today, I’m thinking about “macro” edits—looking at structure and scene placement, rather than the individual words and style.

One of my favorites has been the scene chart, inspired by a post on Edittorrent. The original post suggested creating index cards for each scene, listing a number of important features—everything from where and when the scene is set, to first and last lines, to “promises” made to the reader, to important details like descriptions. Then you could move the index cards around to resequence events or scenes, or play with the story without hurting your MS.

Like many of the commentators on the post, however, I used a spreadsheet to do this in a very small space. I also combined this with probably the most important thing I learned from Jack Bickham’s Scene & Structure—the structure of a scene and the importance of a scene goal—for the character, not just me as a writer.

When I used these techniques together, I found that the scenes that lacked a goal for the character (or a unique goal, as opposed to one that the character’s had four times now) were often the unfocused scenes I needed the most work on—or to cut altogether. I could also bring out hidden scene goals, find new ones to add layers to a scene and strengthen the scenes by enhancing the goals, conflict and disasters.

So here’s an example of the kind of scene chart I used, partially filled in for an imaginary story (anybody recognize the plot? Hint: it’s from an old card game). I didn’t use all of these columns myself (and if any of them aren’t clear, feel free to ask what I mean).

That’s just one thing I’ve tried, and I liked it so well, I’ll definitely use it in the future.

What do you think? Do you use a form of scene charts? What’s your favorite “macro” editing technique?

Photo credit: Aaron Brown

Eliminate “scaffolding” for elegant deep POV

This entry is part 5 of 14 in the series Deep POV

When you see a building under construction, your eyes are naturally drawn not to the building, but to the latticework of metal encasing its facade. In writing, the same attention to certain words and phrases—in this case “head words”—creates the same effect.

Sometimes we use phrases like “he thought” or “she knew” to reinforce the POV character’s connection with the thoughts in narration. But instead of drawing our readers’ attention to the character’s thoughts, too many of these phrases can draw attention to that scaffolding—the words that encase the character’s thoughts. Remember the example we used early on of watching a character looking out the window versus seeing the view ourselves?

This passage from the otherwise excellent Scene & Structure by Jack Bickham exemplifies the thinking behind this problem:

Failure to use constructions that show viewpoint is quite common, and, we can be thankful easy to fix. . . .

Consider the following statements:

The cold wind blew harder.
A gunshot rang out.
It was terrifying.

These are fine observations, but in none of them do we know where the viewpoint is. Ordinarily you should recast such statements to emphasize the viewpoint, thus:


She felt the cold wind blow harder.
He heard a gunshot ring out.
It was terrifying, she thought. Or:
Terror crept through her.(89)

I can’t say whether it’s just publishing trends or the version of deep POV that’s au courant, but today, publishing trends have moved far, far away from his “fixes” (other than the last one, of course). Today, such “scaffold fixes” smack of telling instead of showing.

Showing versus telling

By emphasizing the viewpoint character in these sentences, we are doing exactly what Bickham wants us to—show the viewpoint. However, we’re telling what that character is seeing/feeling/hearing.

The question readers should be asking upon reading a sentence like Bickham’s first examples isn’t “Who’s seeing/feeling/hearing this?” It’s “What’s next?”

Naturally, these examples are pretty much begging for this kind of scaffolding—because they’re in isolation. If you start your scene with a sentence like any of these (without a clear POV, that is), then yes, readers could be confused whose POV you’re in. You must establish the viewpoint character early on—but not by telling.

The cold wind blew harder and Jack flipped up the collar of his coat. He hated the winter.
A gunshot rang out. Maria flung herself under the nearest car before the terror could even register.

If you establish the POV at the beginning of the scene, and continue to show your character’s thoughts throughout the scene, simple declarations and observations of the world around him don’t require you, the author, to tell us that the POV character is the one seeing/feeling/tasting, etc. Cutting back the unnecessary scaffolding lets the elegant architecture of the sights and senses of your story shine through.

For Thursday, we’ll look at when you should use “head words” and how to not “eject” your readers from the characters’ point of view.

What do you think? Don’t you want to wish me a happy fifth wedding anniversary? Do you notice “scaffolding” or head words when you’re reading? Do you try to avoid them while writing? Or do you see them as a useful tool to establish viewpoint?

Photo credits: scaffolding—Paula Navarro; Colosseum—Hannah Di Yanni