How to Document World Café, Open Space, Liberating Structures, and Design Sprint Sessions

Four facilitation formats that scatter the conversation on purpose, and how to document each one faithfully using its own harvesting tradition rather than generic note-taking.

Documenting a World Café, Open Space, Liberating Structures, or Design Sprint session comes down to something the four formats share: each one deliberately breaks a big conversation into many smaller ones, so the record you want lives in several places at once and no single observer can hold all of it. The reliable approach is not a better note-taker. It is to lean on the harvesting tradition each of these methods already built for exactly this problem, and to add capture that matches how the method splits the room. This guide walks through what each method's own practitioners do, with specific advice for each.

Why these formats resist ordinary note-taking

An ordinary meeting has one thread and one note-taker, and it documents itself with a single set of notes. These four formats are built the opposite way, on purpose. World Café keeps people moving between tables, so no single conversation ever stays in one place with one set of people. Open Space lets participants invent the agenda on the day and walk between concurrent sessions whenever they like, so you cannot know in advance what will need capturing or who will be in the room for it. Liberating Structures runs many small parallel exchanges and folds them together in minutes. A Design Sprint runs one team, but over five days where each day's output becomes the next day's input. The scattering is a feature. It is what surfaces ideas a single plenary would bury. It also means documentation has to be designed in from the start, not bolted on when the room clears.

World Café: follow the thread that keeps moving

World Café, developed by Juanita Brown and David Isaacs in 1995, seats people at small café-style tables for a series of rounds, usually 20 to 30 minutes each. Between rounds everyone moves to a new table except one person, the table host, who stays behind to catch newcomers up on what the last group discussed. Ideas cross-pollinate as travelers carry threads from table to table. That movement is the whole point, and it is also why any one conversation is impossible to follow from start to finish. It never happens in one place with one set of people.

The method's own answer is the harvest. In the World Café's seven design principles, the last is to harvest and share collective discoveries: a closing whole-group phase where the patterns that formed across tables are made visible to everyone. Build your capture around it.

• Cover each table in paper and put markers out. When people draw and write as they talk, the table itself becomes the record, and the next group can read and build on what the last one left. Photograph every tablecloth before you clear the room.
• Use the table host as your continuity thread. The host is the one person who heard how an idea changed across rounds. Ask hosts to jot a line at the end of each round, not only at the very end, so that evolution survives.
• Treat the harvest as the main event, not a two-minute wrap-up. The cross-table pattern is the whole reason to run a café, and it exists nowhere except in the harvest. Capturing it in full is worth more than a tidy record of any single table.

Liberating Structures: the artifact usually already exists

Liberating Structures, created by Henri Lipmanowicz and Keith McCandless, are a published collection of thirty-three small, repeatable formats meant to replace conventional brainstorms and status presentations. Several of them produce a written record as a built-in step. In 1-2-4-All, for example, people first reflect in silence and write their own ideas down, then compare in pairs, then in fours, then the whole group names what stood out. The individual writing comes first by design, so a quiet person's idea exists on paper before the loudest voice in the room has spoken.

That changes what documentation even means here. The problem is rarely getting ideas written down, because the structure does that for you. The problem is that hundreds of slips, cards, and sticky notes are easy to orphan the moment the session ends.

• Label as you go, not afterward. A photo of forty sticky notes with no record of which structure or which round produced them is close to useless a week later. A short header on each cluster, naming the structure and the question, keeps the notes readable.
• Capture the "All" step, not just the slips. The written ideas lose their meaning without the whole-group moment where people say which ones matter and why. That synthesis is the part a sticky note cannot hold on its own.
• Photograph before people leave. Written artifacts walk out of the room in pockets and end up in a bin. Collect or shoot them while the group that made them is still standing there to explain the illegible one.

Open Space Technology: you do not know the agenda until it starts

Open Space Technology, created by Harrison Owen in 1985, has no set agenda until the participants build one on the day. People propose topics, post them on a wall, and the wall becomes a marketplace of concurrent sessions. The law of two feet lets anyone leave a session that is not useful to them and join another, so groups form, split, and re-form on their own. You genuinely cannot know in advance how many sessions there will be, how long each one runs, or who will be in the room for it, which makes assigning a scribe per table impossible before the day begins.

Open Space solved this decades ago, and the solution is worth copying whether or not you run a formal Open Space. Each session has a convenor responsible for capturing what was discussed, and those notes are compiled into a "book of proceedings" that every participant receives, often before they leave the room.

• Hand every convenor a one-page report template when they post their topic. A blank page after a session yields nothing. A page with three prompts, what we discussed, what we concluded, and what happens next, yields something usable in five minutes.
• Set a hard deadline of reports in before you leave. Proceedings collected on the day get written. Proceedings promised for later rarely arrive.
• Post the reports where everyone can see them. A shared wall or document lets the patterns across sessions surface, which is where an Open Space's real value tends to sit, and no single participant saw enough of the day to spot it alone.

Design Sprint: one team, five days, one decision trail

A Design Sprint is the odd one out here. Developed by Jake Knapp at Google Ventures and set out in the book "Sprint," it runs one team across five days: map the problem on Monday, sketch solutions on Tuesday, decide on Wednesday, build a prototype on Thursday, and test it with real users on Friday. There are not ten parallel tables to capture, so the many-conversations problem the other three formats share barely applies. The documentation challenge is a different one, holding a single line of reasoning together across five days where each day's output is the next day's input.

What is worth capturing in a sprint is the why, not only the what.

• Photograph the wall at the end of each day. The map, the sketches, the storyboard, and the test notes are the sprint's working memory, and they get erased or recycled fast once the week is over.
• Write down the reasoning behind Wednesday's decisions while it is fresh. A month later, "we picked option B" is worth little without the argument that beat option A.
• Keep the Friday test findings attached to the specific decisions they challenge. The point of the test is to learn what to change next, and that only helps a later sprint if it is recorded against the exact choice it tested.

Capturing sessions that run several tables at once

These four formats vary a lot in how much they run conversations in parallel. A World Café or a Liberating Structures session at scale can have a dozen tables talking at the same time. An Open Space can have as many concurrent sessions as the room proposes. A Design Sprint is usually a single team in one room. For the many-tables cases, one class of tool records every table at once. One example is RoomRadar: each table gets a phone that acts as a microphone, participants join from the browser by scanning a QR code with nothing to install, every table is captured in parallel, and afterward the material is grouped into themes and written up automatically rather than being listened back to by hand. The setup is described here. It suits the many-tables methods more naturally than a single-team sprint, or a fully self-organizing Open Space, where the record people want is often the convenor's own summary rather than a full transcript of every session.

FAQ