What is it?

A Learning History is a structured way for a group to document and make sense of its own experience. The facilitator guides participants through a process of collecting multiple perspectives on a shared event, project, or change effort, then organising those perspectives into a narrative document that the wider organisation can learn from. The distinctive feature is the two-column format: one column holds the voices of the people who lived through the experience (in their own words), while the other column holds questions, observations, and commentary that help readers see patterns they might otherwise miss. The group does not just produce a report. They build something closer to a collective memoir that is designed to spark better conversations about what happened, why it mattered, and what to do next.

Also Known As

• Learning History Document

When to Use It

• After a significant project, initiative, or change effort when you want to capture what the team learned before people move on or forget
• When the same types of problems keep recurring across teams or departments and you need to transfer tacit knowledge that does not show up in standard reports
• When a pilot programme has generated useful lessons that need to reach the rest of the organisation
• When there is a gap between what leaders believe happened during a change effort and what frontline people experienced
• When a team has achieved something unusual and you want to understand what made it work so others can build on it
• When formal evaluations and metrics tell you the "what" but not the "why" or "how" behind results
• When you want to preserve institutional memory during periods of high turnover or restructuring

When NOT to Use It

• When the experience is still actively unfolding and people cannot yet reflect on it with any distance. The technique needs enough time to have passed for participants to see patterns rather than just relive emotions.
• When there is no appetite in the organisation to act on what the history reveals. Creating a Learning History and then shelving it damages trust and makes people less willing to be honest next time.
• When the group is smaller than about five or six people. You need enough different perspectives to create a genuinely multi-voiced narrative. With fewer voices, a standard debrief or After Action Review works better.
• When you need a quick turnaround. A proper Learning History takes weeks to produce, from interviews through to the finished document. If you need answers by Friday, use a retrospective or AAR instead.
• When there are active legal proceedings or investigations related to the experience. People cannot speak freely when what they say might end up in court.
• When trust is so low that participants will not give honest accounts even with confidentiality protections. The two-column format relies on candour to work.

The Learning History was developed by Art Kleiner and George Roth at MIT's Center for Organizational Learning in the mid-1990s. They created the method to capture and transfer the tacit learning from high-performing teams in the automotive industry, drawing on ethnographic research traditions including the "jointly told tale" from anthropology. The approach was later expanded by Hilary Bradbury and others for use in the public sector, NGOs, and educational settings. Roth and Kleiner published their foundational work through the Learning History Library series at Oxford University Press, starting with "Car Launch" in 2000.

What You Need

Group size: 8-30 participants for the interview and workshop phases. The core Learning History team (the people who conduct interviews, write the document, and facilitate the dissemination) is typically 2-4 people.

Time required:

• The full process runs over several weeks
• Allow 60-90 minutes per interview
• 2-3 days for writing and editing the document
• And 2-3 hours for each dissemination workshop
• A simplified single-session version can run in 90-120 minutes but produces a rougher output

Space:

• A quiet room for each interview (or video call for remote interviews)
• A workshop room with wall space for the dissemination session
• Tables where small groups can read and discuss the document together

Materials:

• Audio recorder or recording software for interviews
• Interview question guide (prepared in advance)
• Flip chart paper and markers
• Printed copies of the finished Learning History document for the dissemination workshop
• Sticky notes in two colours (one for reactions, one for questions)
• A4 paper and pens for participants

The Process

Setup

1. Identify the experience you want to capture. This could be a completed project, a change initiative, a crisis response, or any shared experience that holds learning the wider organisation needs.
2. Assemble your Learning History team. Ideally, this includes one or two "insiders" (people from the group who lived the experience) and one or two "outsiders" (people with enough distance to spot patterns the insiders might take for granted). If you are an external facilitator, you are the outsider.
3. Brief the sponsor or commissioning leader on what a Learning History is and is not. It is not a performance review, a blame exercise, or a conventional report. Make sure they understand that the value comes from honest accounts, and that means protecting the candour of participants.
4. Identify 8-15 people to interview. Include people at different levels, from different functions, and with different perspectives on the experience. Seek out sceptics and critics as well as champions.
5. Prepare your interview guide with open-ended questions. Focus on what happened, what people noticed, what surprised them, and what they would do differently.
6. Decide on confidentiality arrangements. Most Learning Histories use first names or role titles rather than full names. Agree this with participants before interviews begin.

Step 1: Conduct Interviews

Time: 60-90 minutes per interview, spread over 1-2 weeks

Purpose: Collecting the raw material. Multiple honest, detailed accounts of what happened and why.

1. Open each interview by explaining the purpose: "We are creating a Learning History so the organisation can learn from what this team experienced. I want to hear your account of what happened, what you noticed, and what you think it means."
2. Start with a broad opening question: "Tell me the story of this project from your perspective. What stands out to you?"
3. Follow the energy of the interviewee rather than rigidly working through a script. When they mention something interesting, go deeper: "You said the turning point was the meeting in March. What happened in that meeting?"
4. Use questions that draw out the difference between what was expected and what happened: "What did you think would happen? What actually happened? What surprised you?"
5. Ask about the emotions and dynamics, not just the facts: "What was the mood in the team at that point? What were people saying in the corridor that they were not saying in meetings?"
6. Close each interview by asking: "What is the most important thing you think the rest of the organisation should understand about this experience?"
7. Record every interview (with permission) and transcribe the key sections.

Watch for:

• Interviewees slipping into "official" accounts rather than personal ones. Gently redirect: "That is the version in the project report. What was it like for you?"
• People asking who else you are interviewing. Keep this confidential to prevent coordination of stories.

Step 2: Identify Themes and Build the Narrative

Time: 1-3 days of writing and editing

Purpose: Turning raw interviews into a coherent story that surfaces patterns, tensions, and insights.

1. Read or listen through all the interviews and highlight the moments that made you sit up. Look for places where multiple people describe the same event differently, where emotions ran high, where decisions were made, and where unexpected things happened.
2. Sort the material into themes. Common themes include: the moment the team realised what they were dealing with, key decisions and their consequences, relationships that helped or hindered, what was learned, and what remains unresolved.
3. Arrange the themes into a rough chronological or logical sequence. This becomes the spine of your Learning History.
4. For each theme, select the most powerful interview excerpts and place them in the right-hand column. Edit for clarity but keep the speaker's voice and idiom. Do not clean up the language to the point where everyone sounds the same.
5. In the left-hand column, add questions, observations, and commentary that help readers notice what is significant. These might include: "Three people described this meeting differently. What might that tell us about how information was flowing?" or "Notice how the language shifts here from 'the project' to 'our project.'"
6. Send the draft to each interviewee to check that their quotes are accurate and that they are comfortable with what is attributed to them. This is not optional. People must be able to correct or withdraw their words before publication.

Watch for:

• The temptation to write a conventional report with interview quotes sprinkled in. The two-column format is the method. The left column is not a sidebar. It is the mechanism that turns a narrative into a learning tool.
• Leaving out the uncomfortable parts. If the Learning History only tells the success story, it is useless. The learning lives in the tensions, mistakes, and surprises.

Step 3: Facilitate the Dissemination Workshop

Time: 2-3 hours

Purpose: The document is not the end product. The conversations it generates are. This workshop is where the real learning happens.

1. Distribute printed copies of the Learning History to participants. Include people who were part of the original experience and people who were not. The mix is important.
2. Give people 20-30 minutes to read the document individually, marking passages that surprise them, that they disagree with, or that they want to discuss.
3. Form small groups of 4-5 people. Mix insiders (people who were there) with outsiders (people who were not). Ask each group to discuss: "What stands out to you? What patterns do you notice? What questions does this raise for our work going forward?"
4. After 30-40 minutes of small group discussion, bring the full group together. Ask each small group to share the single most important insight or question that emerged from their conversation.
5. Facilitate a whole-group conversation focused on: "Given what we have learned from this history, what should we do differently going forward? What practices should we keep? What should we stop?"
6. Capture the actions and commitments that emerge. Be specific about who will do what and by when.

Watch for:

• People wanting to debate whether the accounts in the document are "accurate." Redirect: "The Learning History captures how different people experienced the same events. The fact that perspectives differ is part of the learning."
• Outsiders being too deferential to insiders. Encourage them: "You are reading this with fresh eyes. The questions you ask are exactly what this process needs."

Closing

Time: 15-20 minutes

1. Ask each person to name one thing they will take away from this process and one thing they will do differently as a result.
2. Thank the people who gave interviews and were willing to share their honest accounts. Acknowledge that this takes courage.
3. Agree on what happens to the Learning History document. Will it be shared more widely? Stored in a knowledge library? Used in onboarding? Make a specific decision rather than leaving it vague.
4. If the organisation plans to create more Learning Histories, identify who will champion the next one and what experience it should capture.

Facilitator Guidance

What Makes This Work

The power of a Learning History comes from the combination of multiple voices and the two-column format. When people see their own words alongside the words of their colleagues, placed next to analytical questions that invite fresh thinking, something shifts. The document becomes a mirror that shows the group things it could not see while it was in the middle of the experience. The left-column commentary is what separates a Learning History from a simple oral history. Without it, readers consume the story passively. With it, they are drawn into active reflection. The dissemination workshop then takes that reflection and turns it into action. The document without the workshop is an interesting read. The workshop without the document is just another meeting. Together, they create a cycle of reflection and action that builds organisational learning capacity.

Common Pitfalls

• Treating it as a report: The most common failure mode is producing a conventional report with interview quotes inserted as decoration. If the two-column format feels awkward, that is a sign you are doing it right. Stay with the format.
• Sanitising the story: Sponsors sometimes want to remove anything that makes leadership look bad. Resist this. A Learning History that only tells the comfortable parts teaches nothing. Negotiate what can be anonymised, but do not remove the substance.
• Skipping the dissemination workshop: Circulating the document by email and hoping people will read it does not work. The learning happens in conversation, not in reading. Without a facilitated workshop, the document sits in a folder.
• Interviewing only the leaders: If you only hear from senior people, you get the strategy narrative but miss the implementation reality. Include frontline staff, sceptics, and people who left the project midway.
• Rushing the interviews: A thirty-minute interview produces surface-level material. People need time to move past their rehearsed accounts and into genuine reflection. Budget sixty to ninety minutes per person.
• Neglecting the verification step: Publishing quotes that interviewees did not approve destroys trust and can end the practice of Learning Histories in an organisation permanently.

Adaptations

• Virtual/remote delivery: Conduct interviews via video call and use a shared document for the two-column format. For the dissemination workshop, use breakout rooms for small group discussion. Share the document digitally 24 hours before the session so people have time to read and annotate.
• Simplified single-session version (90-120 minutes): Skip the formal interview phase. Instead, gather participants in a room and run a structured storytelling exercise where people write their accounts on cards. Collect the cards, cluster them into themes on a wall, and facilitate a discussion using the left-column questioning approach verbally. You will not get the depth of a full Learning History, but you can capture useful learning quickly.
• Larger organisations (50+ stakeholders): Interview a representative sample of 15-20 people. Run multiple dissemination workshops with different groups rather than trying to get everyone in one room. Each workshop will surface different insights because the readers bring different perspectives.
• Ongoing projects (not yet complete): Create an interim Learning History at a natural milestone or phase transition. This allows the team to course-correct while the project is still live. Label it as a working document and plan to revisit it later.
• Multi-team or cross-organisational projects: Interview people from each team or organisation involved. Use the two-column format to highlight where accounts diverge across boundaries. This often reveals coordination failures and assumptions that would not surface in a single-team history.

Real-World Applications

Post-merger integration review: A Learning History team interviews 15 people across both legacy organisations six months after a merger. The document reveals that while leadership saw the integration as successful based on financial metrics, middle managers experienced a collapse in cross-team trust that was slowing decision-making. The dissemination workshop leads to a series of targeted relationship-building interventions that leaders would not have known to commission without the Learning History.

Product launch lessons: After a software company's biggest product launch, a facilitator creates a Learning History capturing the perspectives of engineering, marketing, sales, and customer support. The two-column format highlights that marketing and engineering had fundamentally different understandings of the launch timeline, which caused last-minute scrambles. The document becomes required reading for all future launch teams.

NHS ward transformation: A hospital ward that dramatically reduced patient falls creates a Learning History so other wards can learn from their approach. The interviews reveal that the improvement came not from the new protocol itself but from the way the ward sister involved healthcare assistants in designing it. The dissemination workshops across three other wards lead to measurably different adoption patterns compared to the usual top-down rollout.

School curriculum redesign: A teaching team documents their two-year journey of redesigning a Key Stage 3 curriculum. The Learning History captures the resistance they encountered, the compromises they made, and the breakthroughs that happened when they involved students in the design process. New staff joining the department read the history as part of their induction, giving them insight into why certain design choices were made.

Non-profit programme scaling: An international development organisation uses a Learning History to document the first three years of a community health programme. Interviews with field workers, community leaders, and headquarters staff reveal that the programme's success in one region was tied to a specific local partnership that could not be replicated elsewhere using the same playbook. This insight prevents a costly failed expansion and leads to a more context-sensitive scaling strategy.