A group builds a story one sentence at a time using a fixed eight-line structure borrowed from improvisation: Once upon a time… Every day… But one day… Because of that… (three times) …Until finally… And ever since then… It is a fifteen-minute lesson in building on someone else's contribution instead of replacing it.
What it is good for
- Creative thinkingGenerating options before judging them, and building on other people's ideas.
- CommunicationPractising clear hand-offs, active listening and saying the hard thing early.
- CollaborationWorking a shared problem where no one person holds all the information.
- Pure funNo learning objective. Sometimes that is the correct answer.
What you need
- The eight prompts, on a slide
The run sheet
Put the spine on screen (2 min)
All eight starters visible the whole time. People cannot play and remember the structure at once.
Demonstrate one round fast (3 min)
Run one complete story with four volunteers in ninety seconds, deliberately silly. The demonstration teaches it better than the explanation.
Groups of four to six (15 min)
Each person takes the next line, going round. One sentence only — hold that limit, because the activity dies the moment someone narrates a paragraph.
Second round, with a constraint (10 min)
Run it again seeded with something real: a customer's first day with your product, or a project from last year. The second round is where the insight is.
Facilitator notes
- The rule that matters is 'yes, and' — you must accept the previous sentence as true. Contradicting it is the only genuine foul, and naming it once is usually enough.
- Groups of four to six. Eight people means a four-minute wait between turns and a dead room.
- Excellent as the opener to a workshop about process or customer journey, because round two produces a shared narrative you can then pick apart.
Debrief questions
Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.
- What happened when someone took the story somewhere you did not expect?
- In round two, did the story end up anywhere true?
- Where in our work do we contradict each other's sentence instead of building on it?
Variations
Customer journey edition
The story must be about a real customer from first contact to outcome. Doubles as a journey-mapping warm-up and produces a usable artefact.
Written edition
Passed round as a document, one line each, no talking. Better for mixed-language teams and for anyone who freezes when improvising aloud.
Access and inclusion
Improvising aloud under time pressure is a real barrier. Offer the written edition as an equal option, and never put a group on the spot in front of the whole room.
Running it remotely
Breakout rooms of four with the spine pinned in chat. The written edition in a shared document is just as good and often funnier.