Skip to content

Writing · Episode 32 · WF-032

When is telling the better choice?

Match detail to narrative importance.

Watch the briefing

Watch the public video on YouTube

Full briefing transcript

Three ordinary crossings may need one sentence. A fourth crossing, when a passenger refuses to leave, may need an exchange. Telling and showing are not opposing moral categories. They control how much space and attention an event receives. The useful question is whether the amount of detail matches the event's job in this story, including any change hidden inside an apparently uneventful routine.

Here is equal emphasis. On Monday Mara checked tickets and crossed the bay. On Tuesday she checked tickets and crossed the bay. On Wednesday she checked tickets and crossed the bay. On Thursday a passenger stayed aboard after everyone else had left. We learn the sequence, but spend repeated sentences on similar crossings and only one on the event that breaks the pattern. That balance might not match our intended focus.

Here is another balance. Three crossings passed without incident. On the fourth, a passenger gripped the seat as Mara opened the exit. I'm not getting off, he said. The first sentence tells us what the uneventful period has in common. The next sentences present the refusal through an action and exact words. We have not dramatized every minute; we have selected the moment whose consequence the scene will explore.

The summary establishes a pattern and moves us across time. The fourth crossing interrupts it. Gripping the seat gives Mara something she can notice, while the refusal creates an immediate practical question: what happens now? Neither detail proves the passenger's motive. Fear, protest, confusion or another reason could follow. If motive matters, develop it through the scene rather than labeling the gesture as a diagnosis.

You would choose differently if Monday's quiet crossing contained the first sign of a changing relationship. Calling it uneventful could erase what the story needs. Or the refusal might merely connect two more important scenes, making a short summary adequate. Narrative importance is not the same as loudness. A tiny decision can deserve close attention, while a large event can be summarized when its details are not this story's concern.

Mark a passage where several days or repeated actions receive similar space. Name the change you want readers to notice. Summarize the genuinely repetitive stretch without hiding relevant differences. Then expand the chosen moment with a perceivable action, a line of dialogue, or a specific decision. Compare the proportions. Check that the transition still explains when and where we are, instead of making the reader reconstruct missing time.

Match detail to narrative importance. Keep a summary when it gives the needed pattern or connection efficiently. Keep a dramatized moment when its particular choices and responses matter. Neither form guarantees emotional involvement; placement and context still count. For your next revision, compress one routine and expand one turning point. Explain what you gained and what you deliberately left outside the frame before deciding which version serves the story.

Practical takeaway

Match detail to narrative importance.

Disclosures and limits

AI-assisted production and synthetic narration. Examples, demonstrations and diagrams are original teaching material unless a source is linked below.

All ferry-town passages, names, comparisons and exercises are original synthetic teaching material; no source literary excerpts, private manuscripts or copied imagery.

Original sources and limits

  1. detail — checked 2026-09-18. General importance of observation and detail; functional tests and all ferry-town examples are original interpretation, not quoted source fiction.
  2. editing — checked 2026-09-18. Broad editing, selection and clarity foundation. Original showing/telling proportions, permit conditions, invented term and spatial maps are editorial applications, not course prescriptions.

Checked dates are preserved from the project source records; this review package does not claim a later recheck.