Graphic by Peg Ihinger

Probably the most common piece of technical advice about writing fiction is “show, don’t tell.” I’ve gone on at length in other posts about what’s wrong with this dictum, but today I want to talk about how to do it right. Starting with some technical aspects.

First, I need to distinguish between two types of “telling”: generalizing vs summarizing. Generalizing is abstract and interpretive: “Jake was a generous person,” “Diane was always friendly,” “The battle was long and horrible.” General statements are telling readers what to think about characters, places, things, and events. They don’t give readers any room to reach their own conclusions based on what they personally consider “generous,” “energetic,” or “long and horrible.”

Summarizing is specific, but compressed rather than detailed: “Jake chaired two fundraising committees for nonprofits and contributed annually to several charities.” “Diane smiled at everyone.” “After three days of constant battle, the few survivors crawled off the field.” Summaries often take more words than a general description, because they provide some specifics. They are a brief snapshot of what Jake and Diane do that indicates generosity or friendliness, and summarizes what the results of the battle were that make it “long and horrible.” Readers can then form their own opinions about whether the characters were actually generous and friendly, or whether they are actually showing off or compensating for a guilty conscience.

The “don’t tell” part of that basic writing advice is aimed squarely at the first type of telling, but it frequently gets misapplied to the second sort.

“Showing” is technically another misnomer. All writing is telling the reader something. “Showing” simply gives readers specific details: exactly what the characters say and think, as they say or think it; what the characters do, as they do it; what specific things are present and precisely what they look like. And even then, it isn’t as much detail as one would get from watching the same scene in a movie.

Showing a scene doesn’t include all the details. In a movie, the camera catches the leaves blowing past the main characters’ feet during the big proposal scene that’s the actual focus; in a written narrative, there are simply too many tiny, irrelevant elements. “Showing” a scene in writing is like a detailed pencil sketch that the reader has to fill in with colors and any moving parts from their own imagination. Summarizing a scene is like those lovely Japanese ink drawings that take only two lines and a couple of dots to show you a sleeping housecat. Generalizing is like giving a reader a plain piece of paper labeled “This is a cat” with no picture at all (and then being surprised later to find out that some readers pictured a black housecat, others a calico cat, and a few thought of tigers or lions).

“Show, don’t tell” carries the strong implication that only showing is an effective technique, which is deeply unfortunate. All three techniques can be effective, because they each do something different. Which is where we come to the storytelling part of showing vs. telling, which involves choosing the most effective technique for what the writer wants to do.

The most vilified of the three is generalizing. “He’s generous, she’s friendly, it’s horrible” are all opinions. In straight narrative, they require the reader to trust that the writer is telling them the truth. Reader trust is a precious commodity, hard to gain and easy to lose. If readers have to choose between their own perceptions and what the narrator says is true, they will nearly always choose their own judgments. As soon as the reader perceives, according to their own standards, that Jake is not being generous, Diane is acting unfriendly, or the battle wasn’t as long or horrible as they’d pictured, they lose a bit of trust in what the writer is telling them. Too many lost bits, and the reader stops reading.

This means that 95% of the time, generalizing is extremely ineffective for description. Even if you’re desperately trying to reduce word count.

However, generalizing is useful in dialog and internal monolog, precisely because it conveys an opinion…the character’s. If a character says that Jake is a generous person, and the reader later sees him acting un-generously, the reader doesn’t lose trust in the writer. They lose trust in the character who told them Jake was generous.

Used this way, generalized “telling” becomes a useful tool for characterization. It also works as sarcasm (“‘Such a generous person,’ Harriet commented, watching Jake throw a single nickel in the Salvation Army kettle.”), as a tell for an unreliable narrator, or even in a thumbnail description of a group of walk-on characters where the writer doesn’t need to say more than that it’s an angry mob or a peaceful delegation.

Summarizing is halfway between showing and telling, but I’m treating it as telling because so many people think it is. It’s a really odd thing to forbid, because it is practically indispensable for writing transitions. The longer the period one is skimming over, the more useful it becomes as a way of giving readers some idea of what’s been going on in the past week or month or year or decade.

It doesn’t matter whether the writer is jumping over time in narrative (“George spent the next three weeks in the hospital”), in dialog (“‘After three weeks, I’m glad to get out of there,’ George told Michael as they left the hospital”), or in the point-of-view character’s internal monolog (“That was the most boring three weeks of my life, George thought as he left the hospital”). These transitions are all just compressing a bunch of time that, if told in detail, wouldn’t contribute anything to the story other than “time passed, irrelevant stuff happened.”

Dialog also uses summarizing a lot, for the same reasons. People in real life seldom, if ever, give a twenty-minute blow-by-blow description of George’s three weeks in the hospital. They say, “George? He’s been in the hospital for three weeks getting chemo. He got out yesterday.”

And since I’m running out of space in this post, I’m going to spend the next one on “showing.”

13 Comments
  1. But above all else, remember Mark Twain’s rule:

    “When the author describes the character of a personage in his tale, the conduct and conversation of that personage shall justify said description.”

    (The author not being the unreliable narrator.)

  2. I just thought I’d say “Show, don’t tell” just might be the best three-word advice in writing.

    As this entry shows, however, a thousand words is a lot better advice than three.

  3. It’s good advice if you’re telling too much and not showing enough. But I read a manuscript from a friend of my spouse’s which definitely had the opposite problem. Showed *everything*, bogging the story down completely. His main character couldn’t get across town without going block by block.

    I don’t know, but I wonder if they’d been told “show don’t tell” without any consideration for what their actual weaknesses were.

    • That seems likely.

      Advice is almost always better with nuance.

    • That’s why I have spent so much time ranting about how “show, don’t tell” is some of the worst writing advice–because applying it indiscriminately causes more problems than ignoring it, in most cases. It’s a hammer…but not everything is a nail.

      • I think the problem is more “applying it indiscriminately” than it being such bad advice.

        “Kill your darlings” doesn’t mean remove everything good from your manuscript. Aristotle’s dramatic unity doesn’t mean beating readers over the head with the theme or motif or conflict/problem.

        Any advice is bad if taken to extremes.

        • “No rule should be followed off a cliff.”
          —C. J. Cherryh

        • “Kill your darlings” doesn’t mean remove everything good from your manuscript.

          And yet, I have known beginning writers who seriously thought they had to go through their stories and delete every sentence that they really liked. As you may imagine, the results were… not good.

          I think any advice reduced to a pithy three-word phrase is bad advice. Writing is all about nuance and context, and “Do this thing” has neither. Presented that way, the advice has already been taken to extremes by the giver.

          Plus, diagnosis is key — yet many people throw that kind of advice around without any consideration of whether it applies, let alone how it might apply.

          • LizV: I think any advice reduced to a pithy three-word phrase is bad advice

            I had almost that exact thing queued up to say in my next post! Thank you.

          • The advantage to such a short saying is it’s memorable.

            The disadvantage, well, you and our hostess have both pointed that out!!!

      • I wonder if it might have been more applicable advice back when the fashion was for laconic storytelling, rather than the later/current style of describing the movie playing in the writer’s head.

  4. This is actually pretty nuanced:

    https://en.wikipedia.org/wiki/Show_don%27t_tell

    (For what it’s worth, when I was first trying to write, half a century ago, I found exposition *much* easier than narrative. To my credit, I realized pretty quickly I couldn’t lean on exposition, but had to use it sparingly.) (Your mileage will undoubtedly vary.) (And probably should.)

    • Which is why diagnosis is key. Advice that would be a train-wreck for one writer might be just the thing for another.

      (I tend to be cranky about any advice that’s bandied about as a universal rule, because I’m often the one with the opposite problem. I still remember wearing my first NaNoWriMo “winner” t-shirt to a convention, and having somebody — who didn’t know me and had never read a word I’d written — look at it and say “Congratulations! Now cut it by 15%.” I’m a chronic underwriter….)