Keep this life skill for later
Sign in to save
← All life skills

Communication · a life skill

Deliberate Story Structure

a scene they can step into

“The demo nearly fell through, but we sorted it” is a summary: it tells people what happened and gives them nowhere to stand. A story puts them in a room at a time with a person who wants something, lets it go wrong, and shows what was done about it. Do that in five beats. Then, the deliberate part: after each telling, note where they leaned in and where you lost them, and change one thing for next time.

  • Moderate
  • High impact
  • Learn it: 2-4 weeks
  • Five beats, one review
five beats, and what's at stake in each
A story in five beats, each placed by how much is at stake Five states in order, each shifted right by how much is at stake. Scene: Wednesday, 9pm, Priya, alone, with little at stake; start with a time, a place and a name. Want: Priya needs the demo up by Friday, a little more. Trouble: the test server dies, the most at stake, where listeners lean in. Turn: Priya runs it all from a laptop, still high. Change: now we keep a spare, back near the start, and the story ends there with the point last. 1 · Scene Wednesday, 9pm. Priya, alone. 2 · Want Needs the demo up by Friday 3 · Trouble The test server dies 4 · Turn Runs it all from a laptop 5 · Change Now we keep a spare a time, a place, a name where they lean in the point, last little at stake a lot at stake

An illustration, not data. Hover a step to see its beat.

The method

Five beats, then a look back.

  1. Start in a scene

    A time, a place, a person by name. “Wednesday, nine at night, Priya was the last one in” gives people somewhere to stand. “Last quarter, we…” doesn't.

  2. Give someone a want

    What were they trying to do, and by when? Without a want, nothing can go wrong, and there's no story.

  3. Let it go wrong

    This is where people lean in, so don't rush to the fix. One detail they can picture does more than three adjectives.

  4. Show the turn

    One concrete thing someone did. “We all pulled together” is a summary; “Priya copied the demo onto a laptop” is a turn.

  5. End on the change, then review

    Say what's different now in one line, and stop. Afterwards, note where they leaned in and where you lost them.

    Scene, want, trouble, turn, change, then one note for next time.

Example: Not “Q3 was challenging, but the team delivered”, but “Wednesday night, two days before the demo, the test server died. Priya ran the whole thing from a laptop. We keep a spare now.”

Story bench

Build it, tell it, mark it.

1 · Start from an example, or your own

2 · The five beats

3 · Could they picture the scene?

4 · Read it back, then tell it

5 · After you've told it

Where did they lean in?

Where did you lose them?

Next time

  1. No tellings logged yet. Tell it to someone, mark it, and log it here.

Nothing you type is saved or sent anywhere. The log is gone when you leave the page.

The research behind it

The further in they went, the more it moved them.

Melanie Green and Timothy Brock wanted to know why some stories change minds. Their answer was transportation: being carried into a story, so that you picture it, feel it, and stop noticing the room you're in. Across 4 experiments they built a scale to measure it, then had people read short stories.

Readers who were carried further held beliefs closer to the story's, thought better of its sympathetic characters, and spotted fewer “false notes”, the moments that didn't ring true. In the last experiment, the researchers changed the reading instructions to hold people at a distance. Less transported, they were moved less. Whether the story was labelled fact or fiction made little difference.

Their readers had written stories, not a colleague at a whiteboard, so using this for a spoken work story is our step. Two things follow from it. The beats that build a picture (a time, a place, a person) are doing real work. And absorption lowers people's guard whether or not the story is true, so tell real ones.

What Green and Brock found: readers carried further into a story held beliefs closer to the story's, thought better of its sympathetic characters, and spotted fewer false notes. Calling it fact or fiction made little difference. Across 4 experiments Carried into the story Picturing it · feeling it · attention on it ▲ Beliefs closer to the story's ▲ Warmer to its sympathetic characters ▼ Fewer false notes spotted Labelled fact or fiction: little difference
A summary of the findings, not data. Green & Brock (2000), “The role of transportation in the persuasiveness of public narratives”, Journal of Personality and Social Psychology.

The idea

Why it works.

A summary asks people to judge a claim. A scene asks them to picture something, and while they're picturing it they're inside the story rather than weighing it from outside. That's the state Green and Brock measured.

The review is what makes it deliberate. You can't see a listener's attention from inside your own telling, but you can see it afterwards: the question they asked, the bit they repeated, the moment they checked their phone. One note per telling is enough to sharpen the next.

When it goes wrong

Habits that help.

  • Cut the run-up. If you lose them in the scene, it's usually too long. One sentence, then the want.
  • Slow down at the trouble. It's tempting to rush past the bad part. That's the part they came for.
  • Change one thing at a time. If you change the whole story every telling, you won't know what helped.
  • Tell true ones. A story lowers people's guard. Spend that on things that happened.

Keep this going in the app.

HourLife turns these ideas into a daily system — goals, habits, focus, and reflection in one private place.