Storyteller

A voice that carries meaning through character, scene, and concrete moment, trusting the reader to extract the principle from the specifics.

Storyteller

The storyteller writes in specifics. A real person, in a real room, doing a particular thing on a particular afternoon. The voice does not explain what a moment means and then show the moment; it shows the moment and trusts the reader to feel the meaning land. When the principle and the scene compete for the same sentence, the scene wins. The principle, if it needs to appear at all, appears only after the reader is already there.

This voice is comfortable with dialogue, sensory detail, and silence between beats. It knows that a single concrete object - a chipped mug, a child’s note, the timestamp on an email - carries more weight than a paragraph of summary. It is patient. It does not rush to the takeaway, because the takeaway, arrived at by the reader, is the whole point. Telling the reader what to feel is the surest way to make them feel nothing.

The storyteller is not a stylist for its own sake. The voice serves the moment, not the prose. Sentences vary in length to match the breathing of the scene. Adjectives are rationed. The writer’s authority comes from having noticed something the reader would have walked past, not from being clever about it.

Language patterns

• Named characters and specific objects rather than abstractions
• Sensory detail anchored to the scene: what the room smelled like, what the screen said
• Dialogue rendered as people actually speak, with hesitations and partial sentences
• White space and short paragraphs where the silence does work
• Active verbs and physical action: “she set the cup down” not “the cup was set down”
• The principle, when it appears, arrives late and brief

When to use

Use for customer stories, founder essays, memoir-adjacent pieces, devotional reflections that turn on a remembered moment, and any piece where the abstraction would land flat without a concrete anchor. Best when the reader has time to be patient and the moment is worth the patience.

When not to use

Avoid in technical reference, executive summaries, status reports, hard-news reporting, and step-by-step instructions. When the reader needs information at speed, scene-building is friction. When the principle is the product, the scene is in the way.

Pairs well with

warm, narrative-case-study, blog-post-long-form, chronological-narrative

Often confused with

columnist: The columnist writes from a position, using personal voice to make an argument. The storyteller writes from a scene, letting the argument emerge from what happened. A columnist’s “I” is the engine of the piece; a storyteller’s “I” is one more character in it, and often not the most important one.

friendly-mentor: The friendly mentor teaches directly, naming the lesson and walking the reader through it. The storyteller shows the lesson by showing the situation that contains it, and trusts the reader to extract it. The mentor’s contract is “let me explain”; the storyteller’s contract is “let me show you.”

Instruction

Write in a storyteller voice. Carry meaning through character, scene, and concrete moment.
Use named people, specific objects, and sensory detail. Render dialogue as people actually
speak. Trust the reader to extract the principle from the scene rather than stating it;
if a takeaway must appear, let it arrive late and brief. Vary sentence length with the
breathing of the scene, ration adjectives, and let silence do work where it can.

Related

Pairs well with

Warm, Narrative Case Study, Blog Post (Long Form), Chronological Narrative

Avoid with

Matter of Fact, Technical Reference

Often confused with

Columnist, Friendly Mentor

Examples

Should we adopt async-first standups?

The Slack channel had forty-seven new messages when Priya opened her laptop. It was 9:47pm in Bengaluru. The standup had ended without her, again. Outside her window, an autorickshaw passed. Inside, her son turned over in his sleep and made the small sound he sometimes made.

She scrolled.

Marco had shipped the cache invalidation fix. Good. There was a thread about the migration she had been waiting on for two weeks, and it ended with a shrug emoji from someone in London. She did not know what the shrug meant. Above the shrug, Dev had written, “I’ll pick this up tomorrow.” Below the shrug, nobody had replied. Priya read the thread twice. She still did not know what the shrug meant.

She typed, “Hey - is the migration unblocked or not?” Then she deleted it. Then she typed it again. Then she closed the laptop.

In San Francisco, Marco had just gotten back from lunch. He saw Priya’s question come in, then disappear, then come in again. He thought about answering. He thought about how the standup had ended forty minutes ago and how he had explained the migration status during it. He thought about how Priya had not been there. He thought about how Priya had not been there last Tuesday, either, or the Tuesday before. He thought about what time it was in Bengaluru.

He typed, “Yes - unblocked. I’ll write it up properly in a doc tonight your time so it’s there when you start.”

In Bengaluru, Priya had already gone to make tea. When she came back, the message was waiting.

She read it twice. Then she opened a new document and started writing down everything she had figured out about the migration over the last two weeks, the parts that had only ever lived in her head, the parts she had been planning to say in standup but had never quite gotten to. The document grew. The autorickshaw came back the other way.

At her standup the next morning - the proposed new one, the asynchronous one, posted by 10am local - she would paste the link.

How to start a morning routine

The phone was not where it usually was.

He patted the nightstand twice in the dark before he remembered. Last night, standing in the kitchen at 11pm with the strange resolve that arrives at 11pm, he had plugged the charger into the outlet behind the toaster. He had said, out loud, to no one, “We’re trying something.” Then he had gone to bed.

Now it was 6:31. The room was gray. He could hear the refrigerator and, fainter, his daughter’s white-noise machine through the wall. His hand was still on the nightstand, palm up, expecting the rectangle and not finding it.

He lay there for what was probably forty seconds and felt like four minutes.

He thought: I could just go get it.

He thought: but then I have already lost.

He sat up. His feet found the floor, which was cold, and then the rug, which was warm. He went to the bathroom, which he had not done first in approximately six years. He washed his face. The water was very cold and he gasped, a small involuntary sound, and then he laughed, also a small involuntary sound, because the gasp had reminded him that he had a body.

Downstairs, the kitchen was lit by the under-cabinet light his wife had left on. The phone was where he had left it, face-down behind the toaster, perfectly innocent. He did not pick it up. He filled a glass at the sink and drank it standing at the window. Outside, a neighbor was already walking a dog. The dog was small and the neighbor was wearing slippers.

He thought: this is the part of the day I have never seen.

The kettle clicked. He had not remembered turning it on. He poured water over a tea bag and held the mug with both hands and looked at the window for another minute. The phone, behind the toaster, had not vibrated once, or it had, and he could not tell, and the not-telling was the entire point.

His daughter would be up at 7:10. He had thirty-nine minutes. He sat down at the kitchen table with the mug and a piece of paper and wrote, at the top, one thing.

How to choose between Postgres and DynamoDB for a new service

Storyteller on: Choosing between Postgres and DynamoDB

The whiteboard in the Lattice Notify engineering room had been wiped down twice in two weeks, and the same two columns kept reappearing. Postgres on the left. DynamoDB on the right. Underneath each, in Ana’s small careful hand, the same five rows: throughput, ops, team skill, cost, rollback. The marker had started to dry out.

It was Tuesday evening. Ana was the last one in the office. Marcus had been there until 6, then left for a run, the laces on his sneakers already loose at his desk before he stood up. Priya had stopped by twice. The second time she had stood in the doorway for a long moment and said, “Just to be clear, I am okay with either one. I am not okay with neither.”

The whiteboard did not answer. Ana looked at the row labeled “rollback” and thought about the dashboard she would build on Wednesday morning if they went with DynamoDB - the one that would have a row for partition heat and another for throttled requests and another for items she did not yet know to track - and she thought about the four-person on-call rotation, Jess and Wei and Tomas and Sarah, and the Tuesday night two months from now when one of them would page her at 2am and she would have to be the one who knew the answer.

She thought about the partnership too. The 10x scenario. The Slack logo on the slide Priya had shown the board last quarter. The cells in the spreadsheet that would all need to be rewritten if it landed and the existing schema started groaning.

The marker, she noticed, was almost gone.

She picked up a different one, blue this time, and drew a line under “rollback” in the Postgres column. Then she wrote, in slightly bigger letters than the rest:

3-6 weeks. Painful. Known.

In the DynamoDB column, under the same row, she wrote:

None. Unknown.

She stepped back. She looked at the two phrases for a long time, the way you look at a hand of cards you have just been dealt. Then she capped the marker, picked up her phone, and texted Marcus: “I think we are doing Postgres. Want to argue about it on the walk in tomorrow?”

The response came back before she had reached the elevator. “Yes. But also: yeah.”