Search This Blog

Showing posts with label show. Show all posts
Showing posts with label show. Show all posts

Saturday, April 13, 2013

Show, Don't Tell?

The common writing "rule," show, don't tell, has taken a beating in recent times. When I started writing fiction in 2006, it wasn't long before I heard about the suggested mode of writing. Usually from a critiquer who pointed out I was in telling mode here or there.

But I've noticed there has been a growing backlash to this mode of writing. Why is it being rejected as a valid guideline for new writers to write fiction? I think for the following reasons:

  1. Extreme usage in critique groups. One such person attempted to tell me that one should have no telling in fiction, everything had to be shown. So he would point out any telling, and appeared to refuse to offer any other constructive feedback until I "fixed" this one issue. If a person encounters too many like that, it is easy to overreact to the opposite extreme and throw the baby out with the bathwater.

  2. Show, don't tell is the answer to every issue. Related to the above, some critiquers go overboard to using show, don't tell for the solution to any number of unrelated writing problems. Writers hearing "You're not showing here, just telling," when addressing a character's dialog only shows they don't know what they are talking about, using the rule as a crutch because they don't know what else to say. Enough of those, and a writer is tempted to ditch the rule as lame simply because they encounter people who are using it lamely.

  3. Hate any perceived rules. Some folk are just anti-rule. Any perceived guideline that says one should do X, Y, or Z in writing automatically gets push back. "I'll show them" attitude prevails. Especially true if the person gets someone saying you always have to do it this way if you want to keep a reader's attention.

  4. Lazy writers not looking to improve. Some writers don't care. They just want to write a story and have everyone praise them. They aren't looking for critiques. They don't want to know how to improve their writing. They feel what comes natural to them is correct for them, and any effort to write differently is artificial. So they don't gain the writing skills through practice, including knowing when and how to show instead of tell.


If you've fallen into one of these reactions to the show, don't tell rule, maybe it is time to take a step back and gain a balanced perspective. The last group may find this the hardest to do, so let's look first at why one needs to show in fiction, instead of tell.

Non-fiction conveys information; fiction conveys an experience. Few pick up a work of fiction hoping to learn how to grow a garden or how to change the starter in a car. Not that one can't learn how to do those things from a work of fiction, but that's not the reason most buy a fictional story. They buy a fictional story to be entertained. To be immersed into another person's world and experiences. To see the world from a different set of eyes.

The showing mode of writing is not an efficient means to convey information. This is why non-fiction doesn't use much, if any, showing. Even the stories told in a non-fiction book are told in telling mode, because the point is to illustrate a truth, not have the reader experience another person's life. For instance, you'll note the stories in the Bible are primarily told not shown.

However, to have a reader sink into another person's world, to see from their eyes, showing becomes critical. Telling can't effectively do that. To accomplish its goal, fiction has to be primarily showing, using telling when needed. In short, to experience another person's world, you have to convey to the reader what they are experiencing, not simply what happens to them.

A quick example. This would be telling: "Paul saw the dagger as it sank into him." It conveys the information of what happened to Paul efficiently. It does not convey what Paul experienced.

Showing would be more like this: "Paul saw the sun glint off a blade flashing his direction. He jerked back, but a pain echoed through his nerves, his skin numbed, and warmth flowed down his side, soaking his clothing. His knees buckled as darkness swept over him."

The showing doesn't efficiently convey what happened, but it does efficiently tell you what Paul experienced, thus providing emotional impact. Emotional impact is the key to entertaining fiction. Without showing, there would be little emotion conveyed, and would not be as entertaining as it could be. If a person ditches showing for one of the above reasons, then you need to be honest with yourself. You are writing fiction as if it were non-fiction.

Some will tell me, "But this writer did it effectively." Usually they are pointing to a "classic" written years ago. An omniscient narrator used to be the standard story telling mode, which involved more telling. In that day, an author didn't have to compete with more emotionally engaging stories, so writing in telling mode could still stand out, not to mention the number of published books back then per year was smaller, so easier for a well-told story to stand out.

This is not true today. You are competing with story-tellers who know how to engage their reader's emotions through effective showing. This is why you'll hear if Tolkien were submitting his Lord of the Rings book today, it is unlikely he'd gain a following. By today's standards it has a lot of problems. But you'll notice even in that work, Tolkien does show, even if it is not as much as most authors do today.

So, how does one know when to tell and when to show in fiction? I have the following general guidelines I use once I've finished my first draft and am ready to edit.

How critical is the phrase, sentence, paragraph in the movement of the story and/or character arc? The more important to these goals, the more important it is to show instead of tell.

For instance, let's say we need to get Jane to answer the telephone. The call itself moves the story forward. The ensuing conversation provides a clue to the mystery, but the fact she answers the phone isn't important other than the fact she does it. It isn't something the reader needs to experience for the story to move forward.

Indeed, to show that would likely bore the reader if they read, "A ringing echoed through Jane's head. The phone! It must be him. Her shoes snapped against the wooden floor, creaking the planks under her weight so much she wondered if she would fall through them. She wrapped her fingers around the smooth, black dial phone. A cold plastic greeted her hands. The ringing ceased as she lifted the receiver, lighter than she expected. 'Hello'?"

Unless you are building tension for a big moment/reveal, you're building emotional investment for nothing. People don't notice that level of detail unless it is new or they sense a moment of importance. You're convincing the reader something important is about to happen, and when it doesn't, they'll tend to wonder why the emotional investment was made. If you simply need to tell the reader that she answered the phone, it would be more efficient to say, "The phone rang. 'Hello'?"

To maintain the pacing of your story. Related to the last point, sometimes you need to move your characters from point A to B, but nothing happens during that time which moves the story forward. So to show all the detail of that trip would bore the reader. Reducing the trip down to a handful of descriptive words and a telling summary will keep the pacing of the novel from bogging down into drudgery.

Transitional paragraphs. Often you have a transitional paragraph between scenes that requires moving through a period of time to the next scene were story-moving dialog/action will take place. Like the last reason, it would be pretty boring to show someone on watch all night when nothing happens of significance. A simple, "George struggled to fight off sleep until the first rays of dawn arrived and Henry arrived to relieve him," gets the reader quickly through an otherwise uneventful time frame with little loss of interest.

Dialog. It is rare that you hear someone talking in showing mode. When is the last time you heard someone describe their reaction to a joke like this: "My gut tightened. I squeezed my lips tight in hopes of blocking the impending spray of coffee from my mouth. But the pressure grew to the point of shoving my lips apart. Hot liquid careened into his face." No, instead you're more likely to hear, "I laughed so hard I spewed coffee all over him."

Dialog is predominately telling. Leave the showing for the narration if you don't want unnatural dialog littering your story. Included in this is a character telling a story to another. Unless the story goes into a full flashback, in-story mode, a story told by a character in the story would tend to be more telling than showing, unless they were attempting to dramatize it.

Non-fiction. If you are writing non-fiction, one naturally uses telling mode to communicate information effectively. But there are times in fiction where a writer may want to convey some information. Back story is often given in more telling mode, often by a character. Dishing out back story needs to be in short bursts, on a need-to-know basis. You don't want long paragraphs of back story, so you don't want to show it unless there is a good reason to do so. When you need to convey information, a telling mode gets the job done much quicker.

Creating emotional distance. There are times a writer may need to create emotional distance. Especially if it is something that the point of view character is not that emotionally invested in or you want to minimize the impact on the reader. For instance, if you have a rape scene, to minimize any emotional reactions from readers who have gone through it, it could be told instead of shown.

One could come up with other instances of using telling instead of showing, but if you want your scenes to have emotional impact, in-the-story feel, you need to ensure important story-moving segments are shown instead of merely told. The uniqueness of reading a story is the immersion into another's experience, another's thoughts, another's worldview. Movies can't easily accomplish this. If you fail to take advantage of this strength in your stories for one of the reasons listed at the beginning, you'll shortchange the reader, and not give them a reason to read the next book, much less finish the one in their hands.

Do you think some of the negative attitudes toward show, don't tell are a valid reaction or an over-reaction?

Friday, April 15, 2011

The Bible, Fiction, and Real Life

At the risk of hitting a dead horse, once again, I'm going to respond to something I've heard recently. I've heard it before, and I've responded to it before, but I don't think I have on this blog...until now! What did I hear? In fear of Christian fiction devoid of bad words and violence, etc., someone inevitably brings up the line, "But the Bible is full of horrible violence and rough characters," or its cousin, "The Bible is R-rated."

First, I want to acknowledge where that point is correct. There is Christian fiction that reflects an unrealistic, idealistic life that few actually live. The Bible is full of stories about some very bad people doing some very bad things to other people. Even the "good guys" like King David committed horrible sins. It shouldn't be taboo, as long as we are not in the end promoting sin, to show our characters committing sins as well. Perfect characters are not as easily relate-able to the reader as one who messes up. We inherently know this because we all know just how imperfect each of us is, even if we want to hide that from everyone else.

Consequently, any fiction that only wants to show the ideal instead of reality will be hard for most people to relate to. Heroes should have flaws. Though I will add, sometimes it is good to have the one person who can be the example, but they are usually secondary characters in a good story, not the main character. Like Faramir was with Frodo in Lord of the Rings (the book, not the movie).

And the Bible adequately reflects that reality. All through it we see flawed heroes, not perfect characters. And that fact gives hope to all of us. If God can do something great with that person, then maybe I'm not too far gone.

With that understanding as a given, sometimes I get the feeling that people use that line to give themselves permission to make something as foul-language ridden and graphically violent as they dare, and then use it as a stick to beat anyone over the head with who disagrees with their approach, who says they don't want to read something with that kind of language in it. These are the folks likely to say that the Bible is R-rated, so why can't their own stories be?

Problem is, the Bible is far from R-rated. It isn't what happens that makes a film R-rated, but in how it is shown. A great example are the Lord of the Ring's movies. They are rated PG-13, even though they have a lot of violence in them. Even though you see a head get cut off. What is missing? Blood spewing out when that happens. Even the battle field where they orcs are killed by the good guys isn't blood stained as one might expect after killing a whole pile of orc bodies with swords and arrows.

The Bible doesn't describe in detail all these bad things, it merely relates them to us. It does what we as fiction writers are instructed to avoid: it tells rather than shows. For instance, take a look at the following Bible verse, clearly one of the more "graphic" in there:
Jdg 5:26 ASV  She put her hand to the tent-pin, And her right hand to the workmen's hammer; And with the hammer she smote Sisera, she smote through his head; Yea, she pierced and struck through his temples.

That is PG-13 rated at best. It simply tell you what she did, with no "showing." If we were to write this as fiction authors, we'd have something along the lines of:
She placed the tent-pin against his head. The hammer shook in her right hand so much she feared if she missed, it would crush his head. She only wanted to pierce it, to kill him, to end this nightmare. She breathed deep. Get it over with, before he awakes! She drew the hammer back and without giving it another thought, before she threw it aside and ran, she plunged the mallet onto the tent peg as hard as she could muster. The head jerked as the pin pierced his skull and warm blood shot over her hand. His eyes flung wide and a gasp escaped his lips as his head sank back to the ground, blood draining from his wound, pooling below him. His eyes acknowledged the fact that she had killed him, and there was nothing he could do about it. Air stopped gurgling from his mouth. She threw the hammer down only to discover his red liquid on her hands, staining them with the murder. She heard herself screaming, even though she didn't will it.

So, what do you think? Should God have contracted me to write the Bible? (grin) But you see the difference. That would be R-rated, the former is not. The Bible has a lot of nasty stuff in it, very true. But it doesn't show it, it tells it. And that is why it is not R-rated, nor can it be used as an excuse to make one's book R-rated. If you want to make an R-rated book, that is fine. Go for it. But don't say that God made you do it because the Bible is that way. That's simply not true.

Make the stories real, but make them graphic at your own risk of losing readers. Sometimes it is a fine line to walk, and not everyone will hit it all the time, nor will a particular author always avoid it, if only because everyone's line is drawn in a different place. But the Bible is not R-rated, nor the fact that it does relate some bad events mean the extreme is fair game because of it. If you want to follow the Bible in that regard, you'll never show, only tell. And I don't think most authors want to go there on a regular basis.

Where's your line between "real" and "extreme"?