Collective Story Harvest
Collective Story Harvest is a storytelling process from the Art of Hosting community in which a group listens to a real story of a project or change while each listener follows one assigned theme, called an arc, and then reports back what they heard through that lens. Mary Alice Arthur, Monica Nissen and Toke Paludan Møller are credited with developing it around 2010. Because several people track different threads of the same story, one telling produces layered learning for the storyteller and for the group.
Facilitation script
- 1
Frame the purpose in plenary, have each storyteller name their story in one sentence, and let participants choose a story group.
15 min - 2
In each group, explain the arcs, assign at least one listener to each, and set up note-taking.
5 min - 3
The storyteller tells the story without interruption while harvesters note what belongs to their arc.
30 min - 4
Take clarifying questions, then hear each arc in turn as harvesters report what they heard.
35 min - 5
The storyteller says what they take from hearing the story mirrored back.
5 min - 6
Return to plenary, share two or three insights per story, and collect the arc notes for the write-up.
15 min
Tips
Choose arcs that match the question the group needs answered; five generic arcs produce generic notes.
Protect the uninterrupted telling, because the method depends on listeners staying with their arc instead of steering the story.
Ask harvesters to report what they heard, not what they would have done differently.
Decide before the session who will turn the notes into something usable, otherwise the harvest stays in notebooks.
Common pitfalls
Picking a polished success story with nothing unresolved in it: harvesters find little to report and the session turns into applause
Letting listeners interrupt with questions during the telling: the storyteller starts answering the group and the story's own shape is lost
Harvesters giving advice or opinions in the report-back instead of what they heard: the storyteller gets defensive and the mirroring effect disappears
Assigning too many arcs for the group size so some arcs have nobody on them: whole themes go unrecorded
Ending without a plan for the notes: the insights stay with individual listeners and the wider organisation learns nothing
Variations
With a large gathering, run several story groups in parallel and close with a plenary across stories. For a single team, one story with the whole team as harvesters works well as a project review. Online, use one breakout room per story and a shared document with one section per arc. Some hosts add a graphic harvester or a witness role alongside the thematic arcs.
Where it fits
When to use it
A project or change effort has ended and the people who lived it are in the room and willing to tell it
A community of practice wants to learn from members' real cases instead of presentations
A written report exists but the group senses it left out how things actually happened
A storyteller is too close to their own experience to see its patterns and would benefit from hearing it mirrored
You need material on several themes at once, such as turning points and transferable practices, from the same experience
When not to use it
You have under an hour: the telling and the report-back cannot be compressed much, so use an After Action Review instead
The story involves an open conflict among people in the room; a neutral, uninterrupted telling is not possible and a mediated conversation fits better
The group needs decisions or an action plan today; this produces learning, so follow it with a separate planning step or choose a planning method
Everyone should share their own experience equally; Story Circles give each person a turn, while this format centres one storyteller per group
The storyteller has not been briefed or has not agreed how the notes will be used
Related methods
Frequently asked questions
What is Collective Story Harvest?▾
Collective Story Harvest is a group storytelling process from the Art of Hosting community. One person tells the story of a real project or change while listeners each follow an assigned theme, or arc, and afterwards report what they heard through that theme. The result is several layers of insight from a single story.
What are the arcs in a Collective Story Harvest?▾
Arcs are the themes listeners follow while the story is told. Common ones are the narrative thread, processes and interventions, turning points, challenges, and what could be applied elsewhere. Hosts choose or invent arcs to fit the learning question, and some add a witness who listens for what is not being said.
How long does a Collective Story Harvest take?▾
Plan 90 to 120 minutes. The telling takes about half an hour, the questions and report-back from the arcs take another 30 to 50 minutes, and you need time at both ends for framing and a plenary. Choosing stories and briefing storytellers happens before the session.
How many people can take part?▾
A story group works with roughly 6 to 20 listeners, enough to cover every arc. Larger gatherings run several stories in parallel rooms and then compare insights in plenary, so the overall number is limited mainly by space and the number of storytellers.
How is it different from a general harvest?▾
Harvesting in general means capturing the outcomes of any conversation. Collective Story Harvest is one specific process: a single story, told without interruption, with listeners assigned to themes and a structured report-back to the storyteller.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Collective Story Harvest into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Art of Hosting community (Mary Alice Arthur, Monica Nissen, Toke Paludan Møller).