How to Write a Red Herring That Doesn’t Cheat Your Readers

Most writers who shy away from red herrings do it out of decency. They have read mysteries where the misdirection turned out to be a swindle, a false lead the author knew was false and dangled anyway, and they do not want to do that to a reader. That instinct is right, but the conclusion drawn from it is wrong. Learning how to write a red herring is not learning how to lie to your reader more cleverly. It is learning how to let a reasonable, evidence-backed wrong explanation stand for a while, and then take it down with something the reader was also shown. The line between a fair red herring and a cheat is not cleverness. It is honesty.

The examples below come from The Memory of Drowned Things, a mystery written with Premise. Its misdirection runs through documents and official framings rather than a false suspect, which turns out to be the cleaner way to keep the whole thing fair.

A fair red herring is a real explanation, not a planted lie

The tempting version of a red herring is the one where you point the reader at an innocent person and let the narration imply a guilt you know is not there. That is the version that reads as a cheat, because the misdirection has no life of its own. It exists only to fool.

The fair version is different in kind. A fair red herring is a genuine, defensible reading of the evidence, one a smart character would actually reach, that happens to be wrong. You are not hiding the truth. You are offering a competing interpretation that the facts, at that moment, honestly support. When it collapses, it collapses because better evidence arrived, not because the author flipped a switch behind the curtain.

That is why the strongest misdirection in the book is an official document that wears the clothes of expertise. When the drowned begin surfacing in the reservoir and threaten the official story, the Authority answers with a briefing packet titled “Seasonal Turnover Anomalies” — the board’s own science, put in writing, asserting that the lake’s natural seasonal mixing fully explains why the bodies are coming up. The move works precisely because the explanation is real. Reservoirs do stratify and turn over, and that churn can lift things off the bottom. Nothing in the packet is a lie the author is telling the reader. It is a plausible, defensible explanation, offered inside the world by people with the authority to offer it, and the reader has every reason to accept it for now.

The book runs a smaller version of the same move a few chapters on, when an anomalous reading is waved off in a technician’s language: the signal is dismissed as “artifact drift,” a “probable recording error.” It is the same principle at a lower altitude — a natural-cause reading offered by someone with reason to offer it, not a switch the author flips behind the curtain.

Build the false trail out of evidence the reader can see

A red herring only plays fair if the reader can, in principle, see through it. That means the misdirection has to be made of real, visible material, not narration that quietly withholds.

Notice how the turnover packet is a matter of public record. It is a physical, stapled brief with a header the whole town can read — “SEASONAL TURNOVER ANOMALIES, BITTER WATER RESERVOIR” — and it is pushed out to the community as an official note about the reservoir’s natural seasonal processes. The reader takes its claim seriously because the people who issue it treat it as settled science, and because the claim itself is clean and specific: the lake mixed, and that is why the dead are coming up. It aims the whole case in the wrong direction for a good stretch of the book.

The point is that this claim is testable on the page. It is not a vague suspicion the author is spreading around. It is a definite assertion about the physical world — the reservoir turned over, and turnover accounts for the pattern — exactly the sort of thing a temperature record or a gate log could later contradict. You have handed the reader a claim they could check, not a mood they can only trust.

How to write a red herring: overturn it with evidence the reader already had

Here is the move that separates a red herring from a cheat. You take the false trail down with evidence the reader was already shown, not with a fresh fact conjured for the occasion.

The turnover packet does not fall because the author steps in to announce it was a lie. It falls because the deep-water temperature record — data the reader had been shown since early in the case — refuses to show any turnover at all: “no spike, no dip, no signature of anything mixing the deep water up and setting it back down.” The lake never turned over, so turnover cannot be the answer. The reading dismissed as “artifact drift” goes down the same honest way: it does not stay dismissed because a character decrees it noise, it stands back up when the physical evidence refuses to drift. In both cases the correction was available to the reader the entire time. The misdirection bought the story tension without charging honesty for it.

When you dismantle a red herring this way, the reader does not feel tricked. They feel caught, which is the good version of the same feeling. They accepted a plausible wrong answer, and then the book handed back the very piece that should have made them doubt it. That is misdirection that respects the reader instead of exploiting them.

Three tests for a fair red herring

1. Is it a real explanation? A fair red herring is a reading a reasonable person would actually hold, not a lead that exists only to deceive. If it has no life outside fooling the reader, cut it.
2. Is it made of visible evidence? The misdirection should be a claim or a reading the reader can see and, in principle, test. Mood and withheld narration do not qualify.
3. Does the correction already exist? When the false trail falls, it should fall on evidence the reader was shown earlier. If you have to invent the refutation, you have built a cheat, not a herring.

Where this sits in the clue craft

Misdirection is the counterweight to the clue itself, so it pays to read it alongside the pieces on the clues it hides among. For planting the true clue so its payoff lands chapters later, see how to plant clues in a mystery that pay off. For showing a real clue openly while disguising what it means, see how to hide a clue in plain sight. And for the moment the whole case turns over, see how to write the reveal scene in a mystery.

A fair red herring is one you plant in plain sight and then dismantle with something the reader was also shown, which means you have to keep every misdirection reconciled with the truth chapters away. Premise helps you keep a book honest with itself across that kind of distance.