Show, Don't Tell | what it means and how to use it
Based on ShaelinWrites's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
“Show, don’t tell” is mainly about replacing direct labels and abstract summaries with sensory, inferable details that let readers interpret through subtext.
Briefing
“Show, don’t tell” is less a rule about when to use one or the other and more a craft choice about how much sensory, inferable experience to put on the page. Instead of labeling emotions or events directly, writers can describe physical sensations, concrete details, and observable actions so readers infer meaning while staying immersed. The payoff is immediacy and richness: describing slows the pace in a controlled way, pulls readers deeper, and turns a narrative into something they can experience rather than a summary they have to decode.
A key distinction runs through the guidance: describing (often treated as “showing”) is sensory, immediate, and word-heavy, giving writers control over what readers perceive—what they see, feel, or experience—while leaving interpretation to subtext. Explaining (often treated as “telling”) is faster and more abstract, taking fewer words and offering clearer control over the intended idea or emotion, but with less visual texture. Explaining can still be useful when information is necessary but not interesting—like confirming a mechanic fixed a car so the plot can move on—yet overreliance makes prose feel detached, like a textbook or event recap.
Rather than chasing rigid “always show” or “always tell” categories, the advice emphasizes making the judgment case by case. The most practical shortcut is to understand what each mode accomplishes: describing builds trust by letting readers infer; explaining can clarify quickly but risks flattening the story. For writers who struggle to shift modes, an exercise is to write in objective point of view—third-person narration without access to internal thoughts. Because objective POV can’t state “Jane feels sad,” it forces writers to translate emotion into visible behavior and sensory cues. Screenwriting is offered as a natural training ground for this constraint: time passing can be shown through images (like a frayed bandage) rather than narration.
The transcript then maps the principle onto common narrative contexts. Emotion: “She feels content” can become a sensory moment—sunlight pulsing against her face, soft warmth, gentle physical imagery. Character traits: “He was shy” can be shown through avoidance behavior, like tightening at a doorbell and ducking out of sight. Plot and setting: a junkyard trip can be summarized in one line, or expanded into a scene with smell, heat, and action. Dialogue: a conversation can be summarized, or fully dramatized. Backstory and atmosphere: a hard time finding a job can be told in summary, or enriched through a brief flashback or a more detailed sequence of attempts.
Finally, the guidance warns against two common misfires. One is relying on emotion words—searching for “sad,” “happy,” or similar labels can reveal telling. Another is “purple prose” that tries to show by swapping nouns for more dramatic versions without adding real sensory specificity (like replacing “the sun was shining” with vague, inflated imagery). Effective showing should make writing richer without making it harder to read: it should replace labels with concrete, observable details—glints of light, physical sensations, and actions that carry meaning.
Cornell Notes
“Show, don’t tell” is a technique for replacing direct labels and abstract summaries with sensory, inferable details. Describing (showing) tends to be richer and slower because it gives readers concrete perceptions—what characters see, feel, and do—while leaving interpretation to subtext. Explaining (telling) is faster and clearer but more detached, often making prose feel like a recap or textbook if overused. Writers can practice by using objective point of view, since it prevents direct access to internal thoughts and forces emotion to appear through visible behavior and sensory cues. The transcript also recommends spotting telling by searching for emotion words and avoiding “purple” expansions that don’t add real specificity.
What’s the practical difference between describing (“showing”) and explaining (“telling”)?
Why does objective point of view help someone learn to show rather than tell?
How can emotion be shown without using emotion-label words?
What does “show vs tell” look like for plot, dialogue, and backstory?
What are two common mistakes people make when trying to show?
How should writers decide when to tell instead of always trying to show?
Review Questions
- When would objective point of view force you to replace an internal emotion label with what kinds of on-page details?
- Pick one sentence that uses an emotion word (e.g., “She was sad”). Rewrite it using sensory description and observable behavior instead of labeling.
- What signs in a draft suggest “telling” is happening too often, and how could you use a targeted search to confirm?
Key Points
- 1
“Show, don’t tell” is mainly about replacing direct labels and abstract summaries with sensory, inferable details that let readers interpret through subtext.
- 2
Describing (showing) is sensory and immersive but takes more words and slows the pace; explaining (telling) is faster and clearer but can feel detached if overused.
- 3
Telling works best for necessary information that isn’t inherently interesting—like confirming a task is completed so the plot can move.
- 4
Objective point of view is a strong practice tool because it prevents direct access to internal thoughts, forcing emotion to appear through visible actions and sensations.
- 5
Emotion-word searches (e.g., “sad,” “happy”) can quickly reveal where drafts rely on telling instead of showing.
- 6
Avoid “purple” expansions that add dramatic wording without adding concrete sensory specificity or readability.
- 7
Make the show/tell decision case by case based on what the scene needs, rather than following rigid “always” rules.