Culture Snail
The Culture Snail is a group exercise that traces the recent history of a team or an organisation on a timeline. The timeline carries the events that changed its culture: projects, reorganisations, mergers, crises, arrivals and departures. The group reads it to see which changes the organisation adopted quickly and which it avoided. From it, the group reaches findings about the organisation's capacity to absorb the change ahead. George W. Anderson describes the exercise in Design Thinking for Tech (2023). The name comes from his image: like a snail, culture moves slowly and without a clear direction.
Goal
The Culture Snail traces the recent history of an organisation to see how it absorbed past changes. Anderson writes that culture changes "a person at a time and a day at a time". Each arrival and each departure shifts it a little.
In his view, this history tells the group about the organisation's ability to change, about the pace of that change and about how the organisation absorbs it. The timeline describes the past. From it, the group forms hypotheses about the change ahead.
Our version of the exercise produces an annotated timeline and a few findings for the project. The project manager and the change manager use them to choose when the change happens and how much support it needs.
Usage
When to use it
- A large change in preparation: the timeline shows how the organisation received comparable changes.
- Choosing the date of a change: the timeline shows the past difficulties that the schedule must avoid.
- Joining an unfamiliar organisation: the analyst or the project manager learns how it got to where it is.
- A programme that runs several initiatives: each leadership team traces the history of its own area.
- Before a Culture Cube: the Snail traces the recent history before the cube describes the current state.
When not to use it
- A newly created organisation or entity: it has no shared past to trace; describe its current state with the Culture Cube.
- Measuring readiness for change: the timeline does not measure it; use a survey or questionnaire.
- Past failures that are taboo even among peers: the timeline keeps only the official story; run individual interviews.
Description
What the book gives
Anderson describes the Culture Snail on one page. He gives one instruction: "Map this journey! Draw it out with the help of others and consider what you see." He adds questions to read the drawing:
- Do you see inflection points where change was rapid and adopted well?
- Do you see other times where change was avoided and stalled the organization?
- How does this culture journey reflect projects, initiatives, mergers and acquisitions, divestitures, changes in strategy, product launches and product failures, economic downturns, industry changes, and so forth?
In the answer to his case study, Anderson states what the timeline carries: the major events, the inflection points, the decisions, the successes and the failures. His figure draws a winding line dotted with events. At the right-hand end, a snail moves towards a question mark that stands for the future.
Anderson lists the outside influences on culture: partners, training organisations, cloud and application vendors, hardware and network providers.
The timeline and its marks
The timeline, its marks and the steps are our proposal. They stay within Anderson's instruction and his three questions.
The template replaces the book's winding line with a straight time axis. In the book's figure, the troughs fall on the layoffs and on the pandemic. A reader takes these troughs for a mood or a morale level. On the axis, the facilitator marks the years of the period. Above it, the group places the events: projects, reorganisations, mergers, crises, launches. Below it, the group notes arrivals and departures by role and without names. On the right, the book's snail faces the next change.
The marks take up Anderson's first two questions.
- Adopted: the change entered everyday work. The group notes the time from the announcement to everyday use when it knows it.
- Avoided or stalled: the change was dropped, postponed or worked around. The group notes what stopped it.
An event without a mark stays on the timeline. An outside crisis or an arrival does not always call for a judgement.
The steps
- Frame. The sponsor and the facilitator set the scope: a team, a department or the whole company. They choose a period that reaches back at least to the last change comparable to the one ahead.
- Form the group. The facilitator brings together people who cover the whole period: long-serving staff who lived through the first years and people who joined recently. The group mixes business and IT. Anderson places the culture of a project where the two meet. In our version, the group has six to ten people.
- Prepare the events. Before the session, the facilitator collects the dates through document analysis: organisation charts, annual reports, internal announcements, project history. The facilitator places them on the axis. The group's memory completes the list of events without replacing it.
- Complete the timeline. Each participant writes on sticky notes the events that changed how they work. They place the notes above the axis. Below the axis, they note arrivals and departures by role.
- Mark the changes. The group goes along the timeline from left to right. For each change, it sets a mark or sets none. When people disagree, the facilitator sets both marks side by side. For each mark, the facilitator records which site or role gives that judgement. When two participants lived through the same merger differently, that difference is a finding.
- Read the timeline. The facilitator asks Anderson's three questions. The facilitator then adds the question that Anderson asks to time a change: which past difficulties does the timeline illuminate?
- Report to the project. The group compares the change ahead with the marked changes. It writes three to five findings. Each finding cites the events it rests on and says what it changes for the project.
The Snail and the cube
Anderson pairs the Snail, which traces the recent history of an organisation, with the Culture Cube, which describes its current state through three dimensions. At the end of the Snail section, he points to the cube to describe today's culture. In a session that runs both, the group first draws the timeline, then describes the current state with the cube.
The pitfalls
These pitfalls come from facilitation practice.
Naming the people who left. A timeline that notes "Ms X left after the reorganisation" becomes a file on individuals. Art. 328b of the Code of Obligations (CO) limits the data that an employer processes about an employee to the employee's suitability for the job and to the performance of the contract. The group notes arrivals and departures by role and in numbers: "five experienced agents left".
Keeping only the memory in the room. A room of recent arrivals does not know the first years of the period. The documents and the long-serving staff fill that gap. For a stretch that nobody in the room lived through, the facilitator writes "period with no witness".
Telling the official story. In front of the management that launched a change, few participants call it stalled. The facilitator collects these marks in interviews or runs a session without the participants' managers.
Reading the timeline as a forecast. An organisation that failed twice can succeed the third time under other leadership or with other support. The findings stay hypotheses that the project tests.
Confusing the event with its reception. "Merger 2018" says what happened. The mark says how the organisation received it. A group that judges the event ("a bad merger") no longer says anything about the pace of change.
Putting everything on the timeline. Fifty notes hide the inflection points. The group keeps the events that changed how people work. The facilitator groups the others.
AI considerations
A language model prepares the list of events before the session. From the annual reports, the internal announcements and the project history, it builds a chronology. The facilitator checks each date in the document cited: the model invents dates and mixes up projects with similar names. On a virtual whiteboard, the model groups the notes by period and by type of event during the session. After the session, a multimodal model transcribes the photo of the board into a dated document.
The model does not know how the organisation received a change. An announcement presents a reorganisation and does not say that it was dropped a year later. The marks come from the group. A model that calls a culture "resistant to change" on the strength of documents judges without grounds.
Session notes often name colleagues who left or joined. They are personal data under Art. 5 let. a of the Federal Act on Data Protection (FADP). An organisation that hands these notes to an external AI service has that service process them on its behalf. Art. 9 FADP requires a contract for this processing by a processor. Most AI services process data outside Switzerland. Art. 16 FADP also sets the conditions for this disclosure abroad. Before anything is sent, the facilitator removes the names and the roles that point to a single person.
Examples
The customer service department of a health insurer in French-speaking Switzerland will replace its customer relationship management (CRM) tool in 2027. The vendor is ending support for the current tool. Six customer service agents, a team leader and the IT project manager for the CRM trace the department's history since the 2018 merger with an insurer from Valais. Three of them lived through the whole period.
Each mark carries what the group noted: the lead time or what stopped the change.
| Finding | Events | For the CRM project |
|---|---|---|
| Both organisational changes came to nothing. | Common procedures in 2019. Reorganisation by segment launched in 2022 and dropped in 2023. | Introduce the CRM without changing the split of the teams at the same time. |
| Both adopted tools went in with key users. | Online chat in 2021. Telephony in 2024. | Appoint key users at each of the two sites. |
| The only change adopted in under a month answered an outside constraint. | Remote work in 2020: two weeks. Online chat: four months. Telephony: nine months. | Announce the CRM with its constraint: the end of support for the current tool. |
The third finding appears only when the group compares the lead times of the three adopted changes.
Visualisations
The template shows the two marks and where each kind of note goes. The example timeline shows an annotated history. The findings table shows what the group draws from it for the project.
Cost
| Dimension | Level | Justification |
|---|---|---|
| Preparation | Medium | Form a group that covers the whole period. Collect the dates from the documents before the session. |
| Execution | Medium | Our estimate: one session of two to three hours for a timeline that covers about ten years. |
| Documentation | Low | The timeline and the list of findings. One person writes them up after the session. |
Tooling
On site, a roll of paper fixed to the wall or a long whiteboard carries the time axis. Sticky notes in two colours separate the events from the arrivals and departures. Dot stickers in two shapes set the marks. Remotely, a virtual whiteboard such as Miro, Mural or Microsoft Whiteboard does the same job. A spreadsheet holds the list of events prepared before the session and the clean copy of the timeline.
Sources
- George W. Anderson, Design Thinking for Tech: Solving Problems and Realizing Value in 24 Hours, Addison-Wesley, 2023, ISBN 978-0-13-793303-7. Hour 6 "Understanding the Lay of the Land", section "Design Thinking in Action: The Culture Snail for Pace of Change", pp. 80-81: culture that changes a person at a time and a day at a time, its levels, the instruction, the three questions, Figure 6.6 and the pointer to the Culture Cube. Hour 6, case study and question 2. Appendix A, answer to question 2: what the timeline carries. Hour 23 "Making Change Sticky", section "Techniques for Timing Change": the Snail among the techniques that help to time a change. Hour 24 "Design Thinking for Project Velocity", section "Stakeholders and Expectations": the Snail and the cube for the recent history and the current state of an organisation.
The timeline template, the marks, the steps, the pitfalls and the health insurer example are our proposals.

