What Is a Narratologist — Beyond the Definition
The dictionary says: one who studies narratives. That's as accurate as saying a doctor is "one who studies the body." Correct, entirely insufficient, missing the point.
A narratologist is someone who looks at a story and sees a mechanism. Where others hear plot, they hear structure. Where others feel tension, they identify the technique that created it. Where others are moved — they understand why, and how to reproduce it.
But this doesn't make them a cold analyst. The narratologist understands something the analyst misses: that a story is not a decorative layer over information. It is the only format that allows information to penetrate a person's decision-making system — through the body, not through logic. The human brain doesn't process truths. It processes events.
The narratologist knows this. And so they don't ask "what's the story?" but rather "what needs to happen in the body of the listener — and which story makes that happen?"
The human brain doesn't process truths. It processes events. The narratologist knows the difference — and builds accordingly.
The Difference Between a Narratologist and a Storyteller
The storyteller creates. The narratologist understands. The difference isn't one of degree — it's one of direction.
The storyteller works from the inside out: starting from experience, intuition, an inner voice. They create a story that feels right. They don't always know why it works — and they don't need to. Talent precedes method.
The narratologist works from the outside in: starting from mechanism, structure, purpose. They know what each component does and why. They can build a story that works — even without personal experience, even for an audience they've never met. Method precedes voice.
The great storyteller is sometimes an instinctive narratologist — they simply can't name what they know. The narratologist can teach. The storyteller can't always.
But the deeper difference: the storyteller asks "what to tell?" The narratologist asks "what needs to happen as a result of the story?" One starts from content. The other starts from impact, and works backward.
Narrative Engineering — A New Discipline
Narrative engineering is not a fancy name for creative writing. It is a discipline born at the intersection of three fields that have never properly talked to each other.
First: cognitive science. What happens in the body and brain when a person encounters a story. How narrative tension creates real physical tension. Why the body doesn't distinguish between experience and narrative, and how this turns story into a mechanism of change.
Second: poetics and narratology. Plot structure, character arc, point of view, time, pacing. The arsenal accumulated over millennia — from Aristotle to Lajos Egri, from Propp to McKee — still unexplained in language that business people understand.
Third: purpose. Not "fine literature" but: shifting a position, building trust, moving a decision, constructing organizational identity, rallying support. A narrative engineer builds for outcomes — and measures them.
This discipline is new not because people didn't know how to tell stories. It's new because for the first time there's a reason to articulate it explicitly: in a world where AI generates information abundantly and for free, what's scarce is not content — it's penetration. The ability to make a truth land in someone's body and change their next decision.
What a Narrative Engineer Actually Does
Three operations. Always in this order.
Analysis — breaking down to components. They look at an existing story — a speech, a campaign, a pitch, a brand — and ask: what works here and why? Where's the tension? Who's the character the audience identifies with? Good analysis usually reveals that the story that seems "boring" isn't boring — it's built backward.
Deconstruction — separating truth from packaging. Every story contains a raw truth — a fact, an experience, an insight — wrapped in a form that prevents it from landing. Deconstruction finds the raw truth and asks: what experience preceded it? Who lived it in their body? What was the moment everything changed?
Reassembly — building for purpose. Once there's a raw truth and a defined audience, the narrative engineer chooses a structure. Not "what's the most interesting story" — but: what does this audience need to experience in their body for the truth to enter? Reassembly is architecture — not design.
The storyteller asks what to tell. The narrative engineer asks what needs to happen in the body of the listener — and works backward.
Narrative engineering wasn't born because someone decided to invent a discipline. It was born because a world condition changed the value of things.
When information was scarce, the fact was the asset. When information became abundant, interpretation became the asset. When even interpretation became a cheap commodity — what remains is the ability to make a truth land in someone's body and change their next decision.
This is not another communication skill. It is the understanding that a person doesn't change when they know something new. They change when they experience something they didn't know they were missing.
