Show, Don't Tell: What It Really Means and When to Break It
"Show, don't tell" is probably the most repeated writing advice there is. It's also one of the most misunderstood. Some writers take it to mean they can never state anything, and their scenes fill up with fussy detail. Here's what the advice actually means, how to use it, and when telling is the better choice.
What it means
Telling states the conclusion. Showing gives the reader what they need to reach that conclusion on their own. Here's the difference:
Telling: Tom was nervous about the interview.
Showing: Tom checked his tie in the elevator mirror for the third time and wiped his palms on his pants.
When readers work out the emotion themselves, they're more involved in the story. That's the whole idea. It isn't a ban on stating things.
Years ago, I read Melinda Leigh's book, Midnight Exposure. That's a prime example of showing, not telling.
Where telling goes wrong
Emotion labels. "She said angrily." Let the words she chooses and what she does carry the anger instead.
Example:
"Stop it right now," she said angrily.
"Stop it right now." She slammed her palm against the counter.
Backstory dumps. Pages of history in one go slow the story down. Give readers what they need when they need it. Backstory is fine. And it's very often necessary. However a page or two describing the history of a family could often be threaded throughout the story. Maybe a part of the house's history is better in chapter 45 rather chapter 4.
"As you know, Bob" dialogue. This is when two characters tell each other things they both already know, just so the reader can overhear. The name comes from how these lines often start. Real people don't talk this way, so the scene sounds staged.
Example:
"As you know, Sarah, our father died three years ago, and I've run the bakery alone ever since."
Sarah was there when their father died. She knows who runs the bakery. The line is only there for the reader.
Here's a version where the same facts come out through an argument:
Sarah dropped the keys on the counter. "You could have called. Three years I've opened this place by myself, and you pick today to show up?"
If the reader needs a fact, give it through conflict, action, or a short line of narration instead of having one character explain it to someone who already knows.
Summarizing a big moment. If an event matters to the story, readers usually want to be in the scene, not hear a report about it afterward.
Where showing goes wrong
Too much detail. Three details where one would do. A character who throws things, clenches their jaw, and stomps out in every scene starts to look unhinged.
Stock gestures. Hammering hearts and white knuckles show up so often that readers skim past them. A plain statement can be better than a worn-out image.
Showing everything. Not every small moment deserves a full scene. If you show it all, the story crawls.
When telling is the better choice
Telling isn't a flaw. Many writers and editors agree it works well for:
Fast action, where extra detail slows things down.
Transitions, like "Three days later, they reached the coast."
Minor characters and details that don't matter to the plot.
Small amounts of backstory.
Long, emotional scenes.
A telling line can also confirm what the showing meant. These are judgment calls, and not everyone agrees on where the line falls, so trust your own read of the scene.
One more example
Here's another pair, made up for illustration.
Telling: The house was creepy.
Showing: The stairs creaked under every step, and the hallway smelled of decay and mold.
The second version doesn't use the word "creepy" at all. The reader gets there on their own. It also isn't longer than it needs to be. Two details are enough.
How to fix a flat or over-explained passage
Replace the emotion word with a specific action, a line of dialogue, or a physical detail.
Try subtext, where the words and the emotion don't match. A character who says "I'm fine" in a tight voice tells readers more than a paragraph of explanation.
Cut phrases like "she realized that" and "he saw that," and describe what happened directly.
Ask whether each detail earns its place. One sharp image usually beats three.
Pair the two. State the point in a sentence, then add one specific detail.
And don't worry about this too much in a first draft. Telling is natural when you're getting the story down. Revision is where you decide what to turn into a scene.
A common worry
Some writers hear "show, don't tell" and start adding detail everywhere. That can make a scene heavy instead of better. Writing teachers who cover this tend to treat it as a rule of thumb, not a law. It's a way to spot passages that could be stronger, and you decide what to do with each one.
Questions to ask about each scene
What does the reader need to understand or experience here?
Is the way I've written it the quickest way to get them there?
If I show it, is it worth the space?
Try it on one scene
Pick a scene that isn't working. Highlight every emotion word in it, like "angry," "nervous," or "happy." For each one, ask whether the reader already knows it from what the character says and does. If they do, you can probably cut the label. If they don't, the scene needs a detail or a line of dialogue that carries the emotion for you.
How an editor can help
Telling that goes on too long, or showing that goes on too long, is easier to see in someone else's pages. In a line edit, I look at word choice, clarity, and voice. A developmental edit looks at whether the big scenes land. Either way, an outside reader can tell you which passages leave them guessing and which ones over-explain.
A better question to ask
Instead of asking whether you're showing or telling, ask what the reader needs to understand in this moment, and how quickly. If it matters, make it a scene. If it's just a bridge to the next scene, say so and keep moving.
If you'd like a second pair of eyes on a scene that isn't working, I offer a free 1,000-word sample edit with every new inquiry. You can find the details at scarborougheditorial.com.



Comments