Show, Don’t Tell in Speculative Fiction: Active Voice for Magic, Tech, and Horror Scenes

Here is a scene I see in a lot of first drafts. Mine included.

The portal was opened by the wizard. Mira was terrified. The creature that came through was huge and scary, and the village was destroyed by it.

Everything happened. Nothing landed. The wizard did something offstage, Mira got an emotion label, and the village got wrecked in passive voice by a monster with the description budget of a parking ticket.

Two problems are stacked in that paragraph. It tells instead of shows, and it goes passive right when the story should be throwing punches. Most writers learn to fix these separately. In speculative scenes, you need to fix them together, because the weird stuff in your world only feels real when someone is actively doing it and the reader experiences it firsthand.

This post builds on two primers I already wrote. If you want the basics of show don’t tell writing, start with Show, Don’t Tell: Huh?. If you want the grammar side of active voice fiction and why passive writing fiction puts distance between your reader and the scene, read Passive Writing was avoided by the Author. Here, I am focusing on what changes when your scene has spells, starships, or something with too many teeth.

Show don’t tell writing in speculative scenes

In a contemporary story, the reader already knows what a coffee shop looks like. You can tell a little and they fill in the rest. In speculative fiction, the reader has nothing to fill in with. If you write “the alien city was strange,” they have no idea what strange means. Strange to whom? Strange how?

So show-don’t-tell writing does double duty in SF, fantasy, and horror:

• It carries emotion. Same as any genre. Clenched fists, not “Bob was angry.”
• It carries the world. Every detail you show teaches the reader how this place works.

That second job is the one newer writers miss. When you tell the reader “magic was dangerous in Velnar,” you lose them twice. They don’t feel the danger, and they don’t learn anything specific about the rules.

Show it instead. A healer with burn scars up to her elbows. A notice nailed up in the market that limits spells to three per day. A kid who flinches when someone hums, because humming is how spells start. The reader builds the rule from evidence, and evidence sticks.

Active voice fiction vs passive writing fiction in speculative scenes

Passive voice means the subject has the action done to it. “The spell was cast.” Cast by whom? We don’t know. The sentence doesn’t care either.

That missing actor matters more in speculative fiction than almost anywhere else. Magic, tech, and monsters are where your story’s power lives. Who holds that power, and what it costs them, is usually the whole point. Passive writing hides the hand on the lever.

Compare:

• Passive: “The shields were lowered and the ship was boarded.”
• Active: “Okafor dropped the shields. Six raiders cut through the airlock before she could reach the panel again.”

The active version gives us a person, a choice, and a consequence. It also gives us tension, because now we want to know why she dropped them.

Active voice fiction also forces you to pick verbs. “The door was opened” survives with a weak verb. “The thing in the hallway peeled the door off its hinges” can’t. Strong verbs and specific nouns do most of the showing for you.

Passive still has a place. Dialogue, for one. A shaken soldier might say “We were overrun,” because that is how people talk when they don’t want to name what happened. And sometimes nobody in the scene knows who did it. “The seal had been broken” works in a horror opener when the mystery is the point. Use it on purpose, not by default.

Putting them together: before and after examples

Here is where the two tools stop being separate rules and start working as one move. Each example starts with a tell-plus-passive version, then the fix.

Speculative action

Before: The mech was hit by a missile. The pilot was badly hurt and was scared she would die.

After: The missile punched through the mech’s left shoulder. Sparks rained into the cockpit. Jun tasted copper, slapped the eject release, and nothing happened.

We never say “scared.” The dead eject handle does that job. Every verb belongs to something doing something.

Magic

Before: A powerful fire spell was cast by Teodor. Magic was very costly to use.

After: Teodor spoke the word. Flame poured from his palms and swallowed the bridge. When the smoke cleared, he could not remember his daughter’s name.

Now the reader knows the spell is powerful (the bridge is gone) and costly (the memory is gone). Nobody had to say either word. If your magic system has rules, show one of them getting paid in full on the page.

Tech and SF

Before: The AI was very advanced, and the crew was made uneasy by it.

After: The ship answered Rhee’s question before she finished asking it. Then it answered the question she had been about to ask next. Nobody on the bridge spoke for a while.

Advanced and uneasy both come through behavior. Tech in SF reads as real when it does specific things with specific consequences, not when the narrator vouches for it.

Fear and horror

Before: The house was haunted. Ellen was very frightened when the noises were heard.

After: Something knocked three times inside the wall behind Ellen’s bed. She held her breath. It knocked three more times, lower, right next to her pillow.

Horror lives or dies on this. “Frightened” is the narrator’s opinion. A held breath becomes the reader’s. Passive voice (“the noises were heard”) also kills horror because it removes the person who is about to get hurt. Keep your victim as the subject of the sentence. They should be the one hearing, seeing, and backing toward the door.

World reveals

Before: Earth had been abandoned centuries ago, and it was believed by most colonists to be a myth.

After: Kesh found the word “Earth” stenciled on a ration crate and laughed. His grandmother used to tell Earth stories at bedtime, right after the ones about dragons.

One line of a character reacting to a detail does more world-building than a paragraph of history. If you need help deciding which details matter, my post on world-building tools for authors and game masters covers how to keep track of a setting so the right facts are ready when a scene needs them.

Common mistakes when polishing speculative drafts

A few traps I see a lot, and have stepped in personally:

• Showing everything. Not every walk down a corridor needs five senses. Tell the boring transitions. Show the moments that matter.
• An emotion label in disguise. “Fear gripped her heart” is still telling. It just bought a costume.
• Info dumps dressed as dialogue. “As you know, Captain, the warp drive was invented in 2340…” Nobody talks like that. Not even engineers. I have worked with engineers.
• Passive voice in the climax. Search your big scenes for “was” and “were” followed by a past-tense verb. The final battle is the worst place for “the dragon was slain.”
• Hiding the cost. If magic or tech has a price, show someone paying it. Telling the reader it is costly is a promise. Showing it is the receipt.
• Weak verbs propped up by adverbs. “Ran quickly” wants to be “sprinted.” “Said angrily” usually means the line of dialogue should carry the anger itself.

Clean it up before your editor sees it

Do this on your first editing pass. I hunt for tell slips and passive constructions before anything goes to my editor, because an editor’s time is better spent on story problems than on finding every “was cast by.” Clean drafts get better notes.

For the foundations, the two primers are still the place to start: Show, Don’t Tell: Huh? for the reader-inference side, and Passive Writing was avoided by the Author for the active voice fixes. This post is the speculative add-on. Use all three together, and your spells, starships, and monsters will start doing things on the page instead of having things done near them.