Your Training Partner
Techniques Toolbox
The storytelling flow in five steps from left to right: themes and questions, anecdote circle among peers, audio capture and titles, coding with a template, themes and culture. A loop leaves the coding step and returns to it under the label "revise the template".

Storytelling

Storytelling is an elicitation technique in which a group of peers recount episodes from their own work. The analyst collects these experience stories in an anecdote circle, records them and then codes them against one shared template to compare the narrators. From them the analyst draws recurring themes and a reading of the organisation's culture. A story carries an experience and the meaning its narrator gives it. The technique looks for that meaning and for the regularities across stories. It establishes no isolated fact.

Purpose

Storytelling helps the analyst understand a work situation through what people experienced in it. The analyst brings together colleagues who share an experience and gets them talking about past events: a day that went wrong, a case that took a bad turn, a customer lost. The analyst then codes the transcripts and groups what recurs from one narrator to the next. The deliverable is a synthesis of themes backed by the stories and by the coding template that sorts them.

The Cynefin Company, which Dave Snowden founded as Cognitive Edge, holds that every story describes events: if nothing happens, what you hold is an opinion, a statement, a fact or an instruction. The technique collects episodes placed in time and space. Convictions and general rules stay out of the collection.

This material serves the analysis of the situation that comes before the requirements. It shows the tacit rules, the workarounds and the irritants that no procedure describes. A single story counts for what it means to its narrator. Take a story in which a customer threatens to cancel. Whether the customer really threatened matters less than this: the claims handler gave in because she believed him.

User Stories and Job Stories carry a similar name and have another purpose: they are formats for writing requirements.

Usage

When to use it

  • Tacit rules to uncover: bring out what the team does without having written it down.
  • Merger or reorganisation: understand how each team experiences the work before designing the shared process.
  • A poorly adopted tool: collect the workarounds users practise without reporting them.
  • Interviews that only yield the official version: without a manager in the room, peers tell each other what happened rather than what should happen.
  • Cultural diagnosis before a change: read the routines, the symbols and the power relations that the project will collide with.
  • Distributed team: the circle meets by video call with a recording and a shared whiteboard.

When not to use it

  • Questions of verifiable fact: volumes, lead times or rules in force come from document analysis or observation.
  • Climate of fear: in the middle of a restructuring, negative episodes do not come out in a group. Prefer confidential one-to-one interviews.
  • A need that is already framed: requirements workshops specify what remains.

Description

The technique chains two methods that come from outside business analysis. The anecdote circle comes from knowledge management: The Cynefin Company describes it in its wiki of narrative methods. Template analysis comes from qualitative research. Its reference author is Nigel King of the University of Huddersfield. The analyst adds Gerry Johnson's cultural web.

The storytelling flow
From choosing the themes to the cultural reading
1Themes and questions2 or 3 themes, event questions
2Anecdote circle6 to 10 participants, among peers, 90 min
3Captureaudio, titles on hexagons
4Coding with a templateinitial template on part of the stories
revise the template
while relevant passages remain uncoded
5Themes and culturesynthesis, cultural web
The coding template is revised on each new batch of stories. It is not sufficient while relevant passages remain uncoded.

The anecdote circle

An anecdote circle is a group session, in a room or remote, that draws out and collects anecdotes on a topic. The participants share an experience and bring different points of view. The Cynefin Company asks that participants perceive neither a heavy structure nor an objective to reach. They should feel that they are reminiscing together.

The make-up of the circle decides the quality of the material. Bring together peers. A line manager in the room pulls the participants back to the official version. That manager can end the session by contradicting a participant's account. Vary seniority, role and attitude: a circle made up only of enthusiasts tells success stories. Invite volunteers. Our practice puts six to ten people in a ninety-minute circle. Several circles on the same theme give you material to compare.

Preparing the themes and the questions

  1. Choose the themes. Start from the questions the analysis must settle and keep two or three of them per circle. Beyond that, each theme gets too few stories to be coded.
  2. Write the questions. Write two or three questions per theme. Each one targets a moment that the participants experienced. Use the participants' words rather than the project's.
  3. Test the questions. Put them to two or three colleagues before the session. Rewrite a question that produces opinions rather than episodes.
  4. Explain the approach. A sponsor may doubt that anecdotes support analysis. Before the session, explain what the stories bring and what they do not prove.
  5. Prepare the equipment. Plan one recorder per group, hexagonal sticky notes and a written statement of the session's ground rules.

Never ask for "a story". The Cynefin Company explains why: the word suggests a novel, a film or a comedy routine. The participant then makes up a story instead of remembering. Talk about a time, a moment, what happened. Avoid anything without a time element: conditions, beliefs, rules, expectations. "Why" and "how" call for a justification. "When" and "where" lead back to an episode.

Opinion questionEvent question
"What were your accomplishments this year?""Was there a time you felt proud of your work?"
"How does claims approval work?""Tell us about the last time a case waited for a signature."
"Why are lead times so long?""When did a customer call you back when you had nothing new to tell them?"
"What do you think of the new tool?""Think back to the first time the tool blocked you. What happened?"
The event question asks for a moment placed in time. The opinion question gets a judgement or the official version.

When no circle can take place, the analyst asks the event questions in a one-to-one interview or a workshop and codes the answers the same way.

Running the session

The facilitator opens with the ground rules, the reason for the session and the context of the project. The facilitator defines what an anecdote is. Next comes a brief episode from the facilitator's own experience, which shows the kind of material and the degree of openness expected. The facilitator asks the first question and then falls silent. The silence that follows is normal. Filling it cuts off the remembering. The circle works when the participants tell the episodes to one another. When the participants address the facilitator, the session turns into a group interview.

The facilitator prompts without steering: "Do you have an example?", "What happened next?". The facilitator looks for the extremes: the best and the worst moment of a career rather than an ordinary day. Successes come easily. Failures and disappointments come less easily. The facilitator asks for the latter because they tell more. When a participant gives an opinion, lectures or complains, the facilitator asks for the episode: "Was there a time when that happened?".

The facilitator allows time: the useful anecdotes sometimes arrive in the last quarter of the session. When a participant dominates the conversation, the facilitator does not rebuke them in front of the group. The facilitator takes that person aside and gives them a task, for example deriving archetypes: the stock characters who recur from one story to the next.

Capturing the stories

Record audio. Video makes participants more self-conscious. Test the device before the session and start recording at the opening. The participants write the title of each anecdote on a hexagon as the session goes on. These titles index the recording and give the analysis its first material.

The Cynefin Company describes two variants. In the first, the circle chooses the anecdotes to keep. The narrator of each one leaves the circle to tell it alone to the recorder. The narrator thus gives consent. The volume of recordings stays minimal. Scribes can also write the anecdotes down as they are told: the method avoids transcription but loses the exact words.

An hour and a half of recording gives several dozen pages of transcript. The stories contain names, conflicts and customer cases. They are personal data within the meaning of the Federal Act on Data Protection (FADP). Tell the participants how you will use the material, obtain their consent and anonymise the transcripts before you share them.

Coding with a template

Template analysis is a form of thematic analysis. Its coding template is a hierarchical list of themes that the analyst applies to the transcripts and corrects in the course of coding. Brooks, McCluskey, Turley and King describe its steps.

  1. Familiarise yourself with the data. Read the transcripts in full. When there are many, read a subset.
  2. Start preliminary coding. Mark the passages that bear on the question. The analyst can set themes in advance (a priori) as long as they stay provisional.
  3. Cluster. Organise the themes into a hierarchy: broad themes, then narrower sub-themes.
  4. Define the initial template. Build it on a subset of the data chosen for its variety. The article gives the example of five interviews out of twenty.
  5. Apply and revise. Code new transcripts with the template. Add, redefine or delete a theme when the data demand it. Note possible revisions across several transcripts before building a new version of the template.
  6. Finalise. The template is not sufficient while clearly relevant passages remain uncoded. Given the time available, the analyst settles the template when it serves the analysis. The authors add that no template is ever final.

A theme carried by a single anecdote illustrates a possibility. A theme that recurs across several narrators and several circles describes a trait of the situation. The sources use anecdotes to draw out regularities over a large number of stories. We draw the rule from that: a single anecdote supports no conclusion. For each theme the synthesis states how many narrators carry it.

Reading the themes through the culture

Gerry Johnson describes the culture of an organisation through its cultural web. At the centre sits the paradigm: the assumptions that nobody questions. Six elements surround it: stories, rituals and routines, symbols, organisational structures, control systems and power structures. The analyst places each theme on the element it bears on. A theme of working around the tool speaks to the control systems and the routines. A theme of waiting for a signature speaks to the power structures. The elements that receive several themes point to what the change will collide with.

Themes on the cultural web
The claims handlers' case
Paradigmthe assumptions that nobody questions
Stories"Where we came from, we did it differently"
Symbols
Power structuresWaiting for the team leader's signature
Organisational structures
Control systemsWorking around the claims management tool
Rituals and routinesWorking around the claims management tool
"Where we came from, we did it differently"
Waiting for the team leader's signature
Working around the claims management tool
The themes of the case sit on the element of the culture that they bear on. Working around the tool touches two elements.

The Cynefin Company names other uses for the anecdote titles: deriving archetypes or placing the turning points of the stories in the Cynefin framework.

AI considerations

Automatic transcription lightens one of the heaviest tasks of the technique. A speech recognition model transcribes a ninety-minute session in a few minutes. The analyst then checks the transcript against the audio. Names and business jargon need the most attention. A language model can propose preliminary codes on the first transcripts and apply the initial template to the ones that follow. It also finds the relevant passages left uncoded: the template is not sufficient while such passages exist. For the preparation, it rewords an opinion question as an event question. The analyst tests the result on colleagues.

The meaning of a story stays with the analyst. A language model tends toward the generic themes it has seen elsewhere: communication, workload, resistance to change. It smooths out the singular details that give the circle its value. It can also invent a quotation: the analyst checks every excerpt quoted in the synthesis against the transcript. A generated story reports no event that anyone experienced. A set of synthetic anecdotes therefore replaces no circle. Before the session, the analyst decides in the light of the FADP and the participants' consent whether to send the recordings to an external service. A local transcription avoids the question.

Examples

The coding template changes when the analyst applies it to new stories. The case: an insurer in Vaud has merged two teams of claims handlers. The analyst holds five circles on the theme "a case that took a bad turn". Circles 1 and 2 each bring together one former team. The analyst builds the initial template on them. The analyst then revises it while coding circles 3 to 5.

CodeInitial template (circles 1 and 2)Revised template (circles 1 to 5)Narrators (of 38)
1Getting a decisionGetting a decision21
1.1Waiting for the team leader's signatureWaiting for the team leader's signature14
1.2Deciding alone late in the afternoonRedefined: deciding alone for lack of anyone reachable11
2Talking to the customerTalking to the customer17
2.1Announcing a refusal of coverAnnouncing a refusal of cover9
2.2Calling back with no new informationCalling back with no new information12
3"Where we came from, we did it differently""Where we came from, we did it differently"12
4(absent)Added: working around the claims management tool7
4.1(absent)Added: keeping a personal spreadsheet of pending cases5
4.2(absent)Added: copying the case notes into an email4
Coding template before and after revision. Theme 4 and the redefinition of sub-theme 1.2 come from circles 3 to 5.

Seven narrators out of thirty-eight carry theme 4. They come from both former teams. Circles 1 and 2 contained no episode of it: a template frozen after them would have missed it.

Visualisations

The flow of the technique runs from choosing the themes to the cultural reading. The coding loops back on itself as long as relevant passages remain uncoded. The cultural web arranges the themes around a centre, which a table cannot show.

Row by row, the question table sets each opinion question against its event version. The coding template is the table that the analyst keeps up to date during coding. Its columns compare the initial template with the revised template.

Cost

PhaseLevelJustification
PreparationMediumChoose the themes, write and test the questions, recruit volunteer peers for each circle.
ExecutionMediumOne ninety-minute session per circle. Comparing stories takes several circles on the same theme.
DocumentationHighTranscribe, anonymise, then code in several passes. Coding costs several times the length of the sessions.

Tooling

A digital recorder or a mobile phone in flight mode is enough for the capture. Hexagonal sticky notes and markers serve for the anecdote titles. Remotely, a recorded video call and a shared whiteboard (Miro, Mural) replace the room and the hexagons.

Whisper is an open-source transcription model that runs on the analyst's own computer. It avoids sending the audio to an external service. For the coding, a spreadsheet is enough for a few circles: one row per passage, one column per level of the template. Beyond that, qualitative analysis software such as MAXQDA, ATLAS.ti or NVivo holds the hierarchy of themes and counts the narrators per theme.

Sources

Storyboarding
All techniques
Strategy Knotworking (SKW)