Story Spine for Business Storytelling: Structure and Team Exercise

A sequence of events is not yet a story

A project update often sounds like this: first we held a workshop, then we gathered requirements, then we tested a solution, then we changed the plan. The chronology may be accurate, but the audience has to work out the meaning for themselves.

A story becomes easier to follow when events are connected by consequence. What disrupted the normal pattern? What became necessary because of that disruption? Which decision changed the direction? What is different now?

This does not mean making routine work sound dramatic. It means showing the logic of change. The facts remain essential, but they are placed inside a structure that helps people understand why they matter.

A timeline tells us what came next. A story helps us understand why it came next.

The eight prompts of the Story Spine

Playwright, improviser and teacher Kenn Adams created the Story Spine as an exercise for understanding story structure. In a 2026 interview, Adams described it as eight sentence starters that a storyteller completes to create a condensed version of a well told story.

The prompts move from a stable world to disruption, consequence, resolution and a new normal:

• Once upon a time... establishes the person, team or world.
• Every day... shows the normal pattern before anything changes.
• But one day... introduces the disruption, opportunity or decision.
• Because of that... shows the first consequence.
• Because of that... follows the causal chain rather than jumping ahead.
• Because of that... raises the stakes or creates the decisive choice.
• Until finally... reaches the action, discovery or turning point.
• And ever since then... reveals the new reality after the change.

The most useful words may be ‘because of that’

The repeated middle prompt is where the structure becomes especially valuable in business. It prevents a speaker from joining events with ‘and then’ when the audience needs to understand the relationship between them.

If a consequence does not genuinely follow from the previous sentence, the weak link becomes visible. Perhaps an assumption is missing. Perhaps two separate stories have been combined. Perhaps the proposed solution does not respond to the problem that was introduced.

This makes the Story Spine more than a presentation template. It can be a thinking tool. A team can test whether its explanation of a transformation, customer journey or strategic decision has a coherent line of cause and effect before trying to make it persuasive.

Where the structure can help at work

The same spine can support several forms of professional communication. The content and evidence change, but the underlying questions remain useful.

• Change communication: describe the old normal, the event that made change necessary, the decisions that followed and the new way of working.
• Customer stories: begin with the customer’s routine and need, then show the obstacle, response and meaningful result.
• Strategy presentations: connect a change in the market or organisation to the choices now required instead of presenting priorities as an isolated list.
• Project updates: explain why the plan changed, what each discovery caused and what the team knows now.
• Retrospectives: reconstruct a causal chain without reducing the discussion to blame or disconnected observations.
• Public speaking: give the audience a path through the material so that evidence, examples and a call to action support one clear movement.

Use the spine as scaffolding, not as the final script

The sentence starters are excellent for developing and testing a story. They do not need to remain in the finished presentation. Once the logic is clear, the speaker can replace them with natural language, relevant evidence and details that suit the audience.

A business story also needs boundaries. Do not invent a villain, exaggerate a result or turn uncertainty into false certainty merely to complete the shape. Confidential examples should be anonymised or replaced with an approved fictional case.

The structure should make the truth easier to understand, not make a weak claim sound stronger. Mark which parts are observed facts, which are interpretations and which still require evidence.

A shared story is stronger than a polished monologue

Because the Story Spine comes from improvisation, it can be built collaboratively. One person may understand the customer experience, another the technical constraint and another the financial consequence. Completing the prompts together reveals where those perspectives connect and where they do not.

The conversation around the spine is often as useful as the final story. It asks a group to agree on the normal state, the real disruption, the chain of consequences and the change that counts as an outcome.

That shared understanding makes later communication clearer. It also reduces the risk that a confident speaker presents a neat story that the people closest to the work do not recognise.