Born and raised in Honolulu, Hawaii, Ryan now lives in the Midwest, USA, "trying to keep warm." Knowing he has so much to offer in the way of writing advice, I asked him to appear here. I'm very pleased he is able to share a post that rang true for me on the topic of showing vs. telling. This is an essential skill for a writer in any genre. Please read on to hear Ryan's take on this topic and do share with your writer friends. And if you find Ryan's examples helpful, please take a moment to comment and let him know today.
If there was one piece of writing advice I disliked most as a new writer, it certainly was “Show, don’t tell.” Initially, I had no idea what it meant. Self-help writing blogs often toss this phrase around without examples. I even had a critique done on my writing once, and the person critiquing said this phrase several times but offered no help on what showing actually meant.
Finally, I stumbled upon a quote that changed my outlook on writing forever.
“Don’t tell me the moon is shining; show me the glint of light on broken glass.” -Anton Chekhov
It clicked for me. I finally got it. At least, it was enough to where I knew what the heck those people were talking about. But I still craved examples. In this blog post, I thought it would be fun to dive into the important topic of showing versus telling. And yes, fair reader, there will be examples.
“Show the readers everything; tell them nothing.” -Ernest Hemingway
First, let’s think about why we tout showing rather than telling. Why is it so important and popular these days? Literary trends change over time, although much more slowly than, say, fashion trends. These days, the trend in commercial fiction is concise, lean writing without a lot of overly-descriptive “purple prose.” Prologues are somewhat out of fashion for certain genres. Third person limited and first-person are by far the most popular these days, when it used to be third person omniscient about 40-60 years ago. To recall third person omniscient, think Lord of the Rings and phrases like, “Little did they know . . .”
“An overturned tricycle in the gutter of an abandoned neighborhood can stand for everything.” -Steven King
In my opinion, I believe that we show rather than tell because the modern reader is pretty smart. Fiction, in some form, has been around for thousands of years. Readers have come to expect certain things when they read stories. They may not be able to name literary devices, but they are intuitive nonetheless.
“Good writing is supposed to evoke sensation in the reader–not the fact that it is raining, but the feeling of being rained upon.” -E.I. Doctorow
What fun is a crossword puzzle that gives you all the answers up front? It’s much more interesting, and more challenging, to be hinted toward the answers. Essentially, when you “show” in your novel, you are hinting at the answers. You don’t have to come out and say the whole thing; you can give the reader several pieces, and the reader can apply the final piece . It’s an interesting dynamic when you think about it, and it’s much more gratifying to the reader.
“The secret of being boring is to say everything.” -Voltaire
The same principle applies to comedy. If you provide all the information upfront, it’s not funny. But when you give the audience every piece but one (with the right timing), the joke is hilarious. The audience’s mind supplies the final tiny piece of information.
I’ll give an example. Recently, I sent out a tweet featuring a room with crumpled up pieces of paper waist-high. As a caption, I wrote, “Yes, I’ve gone through several drafts . . . why do you ask?” Now, I’m not saying that’s the summit of comedy, but can you imagine how unfunny it would’ve been if I instead had written “These are all of my drafts.” It’s unfunny, because within the context, that part is already obvious. Unconsciously, your readers want you to leave out the obvious parts, too.
By the same token, when your protagonist is upset, simply describing her eyebrows drawing together is enough to tell the reader as such. Within the context, the reader gets it. The reader is pretty smart. These days, continuously telling the reader something that is obvious insults their intelligence and bothers them, even if they’re only subconsciously aware of it.
“A writer should seize upon small details, arranging them so that the reader will see an image in his mind after he closes his eyes.” -Anton Chekhov
So! How about some random examples?
- Telling: Tiffany felt afraid. He pounded on the door, demanding to be let in.
- Showing: Tiffany gripped the sheets in bunches between her cold fingers. Her forehead was slick with sweat. The door rattled again and again against its weak hinges. She didn’t imagine it would be long before he got in.
- With this example, it shows physical signs that Tiffany is afraid, rather than telling the reader out-right. The reader can easily surmise that she is afraid by those physical clues and the context.
- Telling: The crowd looked angry. He wouldn’t be surprised if they revolted. The guards did what they could to keep the peace.
- Showing: The crowd boiled like a simmering cauldron. When the guards weren’t looking, some of the people threw apple cores, aimed at the well-polished helmets. Yells and curses cut through the air. The captain stepped forward with his hands spread out.
- In this example, you can tell the crowd is upset because of the simile and the fact that they are yelling and throwing things. Saying they are upset doesn’t really move the plot forward, but the crowd throwing apples at the guards does, while at the same time showing their anger.
- Telling: Luke drew his sword. He knew this would be the fight of his life.
- Showing: Luke drew his sword. He eyed the graceful movements of the man standing in front of him. His opponent held his sword easily, as one would after a lifetime of applying it. Luke willed his hands to stay dry.
- It’s fairly clear that Luke’s hands are threatening to sweat because he is nervous to fight his opponent, who looks intimidating by his battle stance. Reading that indication is likely enough to signal to the reader that he may be in a tough fight without needing to tell the reader as such.
- Telling: “You have nothing to worry about,” Susie said. It was clear she was lying.
- Showing: Susie shifted her weight, never bringing her eyes up fully to meet mine. When she did speak, she interrupted the sentence by biting her lip. “You have nothing to worry about.”
- Although the “tell” in this example isn’t terrible, you can use physical cues to show that Susie is not confident about what she’s saying. Maybe you want to shed doubt on Susie, but you don’t want to out-right tell the reader that she’s lying, for reasons of mystery. It may not be a simple “which is better,” but it might be a question of how much you want to reveal and when. Showing hints is imperative in a mystery subplot.
Conclusion
Having said all this, it’s not possible to write an entire book without “telling” something. You have to “tell” the readersomething eventually. Add a pinch of salt to any writing advice. What I encourage everyone to do, is to pick off at least the obvious instances to show rather than tell.
Having said all this, it’s not possible to write an entire book without “telling” something. You have to “tell” the readersomething eventually. Add a pinch of salt to any writing advice. What I encourage everyone to do, is to pick off at least the obvious instances to show rather than tell.
Virtually every human emotion could be shown. Observe your friends when they talk. You don’t need to hear your friends thoughts to know when they are feeling certain emotions. True, you have the visual cues that you don’t have in a book, but you can describe the visual cues in writing, which in most cases is all you need. Increasing the amount of “showing” in your books could mean the difference between a good book and a great book.
Ryan's original post on showing vs. telling can be found here: http://ryanlanz.com/2014/11/22/showing-vs-telling/
If you write, I urge you to subscribe to his helpful blog today. Thanks for sharing this information with us, Ryan!
Glad you could join me today, Ryan. Thanks for the awesome advice.
ReplyDeleteIt was my pleasure. Thanks for having me on. : )
DeleteThis is something I have struggled with in my first book. Great post, advice and examples thank you
ReplyDeleteThank you for joining us, Suzie. I'm glad you found Ryan's post useful. I know I did.
DeleteExcellent post with great examples.
ReplyDeleteThanks for reading, WAB. So glad you could join us.
Delete