What Your Reader Concludes About Your Story Is Your Responsibility

Most writers leave this entirely to chance

Photo by Clay Banks on Unsplash

Every time a reader encounters a character, a relationship, a mystery, or a moment of tension in your story, they’re doing something you may not have accounted for.

They’re concluding things.

Readers can be incredibly impatient in that most are not waiting to form opinions and predictions. Most are not holding back judgment until the narration explains what’s happening (which if you’ve been following my social media and my other substack posts, you’ll know I am STAUNCHLY averse to using narration to explain anything at all).

Readers are always subconsciously (and sometimes consciously), actively assembling evidence, drawing inferences, predicting, and forming interpretations, sometimes before you’ve finished giving them the information to do it with.

Please hear me when I say this, because I see this in my comment sections from writers who are horribly afraid ALL. THE. TIME.

Readers will form a wrong conclusion.

This is not a problem.

It’s not.

Sit with that for a moment, because a reader coming to the wrong conclusion about something in your story is not an emergency that needs to be corrected.

And it might feel counter intuitive when I say this, but it can be a very, very powerful mechanism available to a writer. There is a caveat to this, however, and the question I have for you, the writer, is whether you’re using it deliberately or leaving it entirely to chance.

Writers spend a good chunk of time thinking about what they want the reader to know. Fewer think about what they want the reader to conclude. And those are completely different creative decisions and reading experiences.

Telling the reader something is a transfer of information.

Engineering a conclusion is something more sophisticated, it’s about building a pattern of evidence that is distinct enough that the reader arrives at a particular interpretation on their own, one you wanted them to reach, without the narration ever having to name it.

The reason you want this is because when a reader arrives at a conclusion on their own, it lands differently than when they’re told. It feels like discovery rather than instruction because to them it feels earned. It feels, on some level, like the truth because they found it themselves.

That’s the mechanism. And it works in two directions.

The first direction is deliberate misdirection. A.K.A. plot twists.

You build a pattern that leads the reader toward a specific conclusion and then you reveal that the conclusion was wrong. You did not hide information or cheat the reader, the evidence you gave them was real and complete and genuinely pointed in a direction that turned out not to be the right one.

This is how some of the best plot twists in fiction work. Through engineering, instead of hiding information you’re calling the reader’s attention to something else. The writer built a pattern so convincing that the reader committed to an interpretation on their own, and then the writer introduced new information that reorganized everything the reader thought they understood.

The reader doesn’t feel deceived. They feel the pleasure of having been led somewhere by evidence that was always in plain sight. And that pleasure, the retroactive recognition that all the pieces were there, is one of the most satisfying experiences fiction can produce. Think of the Sixth Sense. Everything was in plain sight, but the audience was happy to arrive at an incorrect conclusion.

But misdirection is only one application. The more fundamental one is this.

You can engineer a conclusion about anything.

A character’s hidden motivation. The true state of a relationship. What someone is capable of that they haven’t yet shown. What a character secretly believes about themselves or someone they love. And you can do it entirely through pattern without the narration ever explaining it. Without a character ever naming it out loud.

Here’s what that looks like.

A woman’s best friend shows up one day with a new laptop. High end. Costs more than a month’s rent and our character knows this friend has money problems. So our character asks about it. The friend changes the subject.

A few weeks later the friend is wearing a gold necklace. Real gold. And a new diamond ring. They’ve never been able to afford jewelry like this. But our character also notices the friend has bruises on their face and hands and they are complaining about pain in their back. They say they fell. Our character offers to take them to the doctor but the friend stubbornly refuses.

One day, let’s say our character and the friend are out and about shopping and notice police are canvasing a certain area and the friend suddenly feels “ill and needs to rush home”. Our character expresses concern and the friend hurries off without a goodbye.

Then, we later learn the friend was arrested for mugging and stealing from people.

No narration explained what was happening. No character named it.

The reader assembles a conclusion about the friend from three data points: the laptop, the jewelry and the bruises, and the sudden aversion to being around police; the perceptive reader arrives at the conclusion before the arrest confirms it.

And when the arrest comes, the reader doesn’t feel surprised. They feel the satisfaction of having known.

That’s a pattern doing exactly what it’s supposed to do.

Now here’s the more intimate version of the same mechanic.

You want the reader to understand that a character’s best friend secretly resents them. Not dislikes. Resents. This is resentment that lives underneath false warmth and performs as loyalty while wanting the other person to fail.

You could have the narration tell the reader this. You could have a scene where someone warns the character about their friend. You could have the friend slip and say something revealing.

Or you could build a pattern.

Evidence in objects and space:
The friend handles the character’s things with carelessness. This looks like returning books with cracked spines. Helping them cook and “oh, no, I accidentally broke your favorite spatula I’m so so so so sorry”. They sit in the character’s favorite chair and won’t move.

Evidence in the body:
The friend’s physical responses betray what their words don’t. So their smile doesn’t reach their eyes in our character’s presence. When the character shares good news, there’s a beat, a hesitation before the response where the friend’s face shows elation because they feel that resentment before they can force joy. When our character is struggling, the friend relaxes slightly.

Evidence in action:
The friend does things that are technically supportive but are actually and functionally undermining. So they share, on purpose, the character’s work or accomplishments in contexts where it won’t land well at all. They might introduce our character to people using descriptions that are accurate but unflattering. Or they share feedback or gossip with our character that was never meant to be passed along.

In any of those patterns, no narration named the resentment. No character accused the friend. The reader built the conclusion from the patterns. And the moment it crystallizes, the moment the reader thinks wait, does that friend actually want our character to fail, the story has done something the narration cannot.

It made the reader feel like they discovered something true.

Information delivered through narration is received. Information delivered through pattern is discovered. And discovered information produces a completely different reading experience, where the reader feels like an active participant in the story rather than a passenger being transported through it.

The writer’s job isn’t just to decide what the reader knows. It’s to decide what the reader concludes. And then to engineer the pattern of evidence that leads them there, without ever having to explain it.

So the question worth asking of every significant revelation in your story, every truth about a character, a relationship, a hidden motivation, a secret, is this:

Have I built a pattern that lets them discover it?

Consider what three or four specific, observable, un-narrated data points would lead a careful reader to conclude.

Because the reader who concludes something on their own will believe it more than the reader who was told.

The reader who is wrong, who followed your pattern to a conclusion they were all too happy to arrive at, will feel the correction not as a trick but as a revelation, that makes them want to go back and read the whole thing again.

That’s not a side effect of good pattern work. That’s the point of it.

What your reader concludes about your story is your responsibility and most writers leave it to chance.

You don’t have to.

If you found this post helpful, please consider subscribing or becoming a paid subscriber to help support this publication and its ongoing ability to provide these craft lessons :)

-AJ