Tool 1: Storytelling Audit Template for Tamaraland

Opening: Chasing Stories from Room to Room

Picture this: You're consulting for a mid-sized company. The CEO tells you one story about why the reorganization failed. When you talk to middle managers, you hear a completely different story. The frontline employees? They're telling yet another version. And the story customers are posting online bears almost no resemblance to any of these internal narratives.

Welcome to Tamaraland—every organization with more than two rooms. The metaphor comes from a theatrical production called Tamara, where audience members chase actors through multiple rooms in a mansion, catching fragments of simultaneous storylines but never experiencing the whole play from one vantage point. You cannot be in more than one room at a time. Meanwhile, different stories are unfolding in different spaces, and they're often contradictory, competing, and collectively constituting organizational reality.

This isn't a problem to solve—it's the nature of organizational life. As I documented in my 1991 study of an office supply firm and my 1995 analysis of Disney, organizations are storytelling systems. Stories aren't just communication tools; they constitute the performance system that shapes identity, power, change, and sensemaking. The Storytelling Audit Template helps you map this multi-sited, polyphonic reality so you can work with it rather than against it.

Core Concepts: Understanding the Storytelling Organization

What is a Storytelling Organization?

Every organization is a storytelling organization. In my first field study in 1991, I spent months observing how employees in an office supply firm performed stories in everyday conversations—brief, fragmented, often challenged by listeners, yet constituting collective memory and shared sensemaking. These weren't polished corporate narratives with clear beginnings, middles, and ends. They were terse story performances where speakers assumed listeners would silently fill in major portions of the storyline.

Three characteristics define storytelling organizations:

1. Story Performance, Not Just Story Text

Stories in organizations aren't static texts—they're performances that vary by context, audience, and political purpose. The same "official story" about a new initiative gets performed differently in the executive suite, in department meetings, at the water cooler, and in exit interviews. When you audit organizational stories, you're tracking performances and how they shift across contexts, not just collecting written narratives.

2. Collective Storytelling Systems

Individual organizational members don't possess complete stories. Instead, they contribute fragments to a collective storytelling system where institutional memory supplements individual memories. People perform story bits that others pick up, challenge, revise, and re-perform. The organization's "story" emerges from this distributed, dynamic system, not from any single authoritative telling.

3. Tamara-land Structure

Organizational storytelling unfolds in multiple rooms simultaneously, with different audiences chasing different storylines. When I studied Disney in the mid-1990s, I found the organization operated as literal and metaphorical Tamara-land: tourists chased stories through themed lands, employees experienced divergent narratives in front-stage and back-stage spaces, and marginalized voices told darker counter-stories the official Disney legend excluded. Your client's organization works the same way—multiple stories happening at once in different spaces, and you can't catch them all from one position.

The Four Types of Stories You'll Find

When conducting a storytelling audit, you're tracking four kinds of stories that interplay in organizational Tamaraland:

1. Precedent Stories (Past-Oriented)

These are "how we got here" stories that organizational members tell to make sense of current situations by referencing past events. They include founding myths, war stories, cautionary tales, and historical precedents people invoke to justify present actions. In my 1991 consulting study, I found people performed precedent stories to support or resist change initiatives—"Remember what happened last time we tried this?"

2. Future-Directed Stories (Speculative)

These are the bets, plans, visions, and "what if" scenarios people tell about possible futures. Leaders tell aspirational stories to inspire; employees tell skeptical stories to inoculate against disappointment; consultants tell change stories to mobilize action. Future-directed stories are often antenarratives—fragmented pre-stories that haven't yet crystallized into coherent narratives.

3. Living Stories (Present-Moment)

These are the unfolding, in-process stories happening right now in organizational life. They're embodied, situated, and often unfinished. When you observe a contentious meeting, witness a customer interaction, or watch a team struggle through a problem, you're seeing living story—the raw material before it gets retrospectively narrated into tidier versions.

4. Counter-Stories (Marginalized Voices)

These are the stories official narratives exclude or suppress. They come from marginalized employees, dissatisfied customers, critics, whistleblowers, or anyone whose experience contradicts the dominant story. When I analyzed Disney, I found rich counter-stories about labor exploitation, environmental destruction, and cultural imperialism beneath the surface of the happy Magic Kingdom narrative. Every organization has counter-stories—the storytelling audit makes them visible.

Why "Audit" Is the Wrong Word (But We Use It Anyway)

Traditional audits assume you're counting objective things that stay still while you count them. Organizational stories don't work that way. They're dynamic, contextual, and performative. They change based on who's listening, shift mid-telling, get challenged and revised, and morph across spaces. So when we say "storytelling audit," we don't mean a static inventory. We mean a systematic process of tracking story performances across your client's Tamaraland to reveal patterns, contradictions, silences, and possibilities.

The Political Nature of Organizational Storytelling

Stories in organizations are never neutral. They're tools of power, resistance, sensemaking, and change. In my 1991 field observations, I watched employees perform stories to gain political advantage, introduce change, make sense of confusing events, and challenge authority. Managers told stories that reinforced hierarchy; workers told stories that subverted it. Some stories were told openly in meetings; others were whispered in hallways. Some storytellers had authority that made their versions stick; others' versions got dismissed as "just complaining." The audit reveals not just what stories exist, but who has the power to make their stories become organizational truth.

How to Apply It: Conducting the Storytelling Audit

Step 1: Map the Tamaraland

Start by identifying the physical and metaphorical rooms in your client's organization. Physical rooms might be departments, locations, hierarchical levels, customer touchpoints, or supplier interfaces. Metaphorical rooms might be formal meetings versus hallway conversations, official communications versus back-channel gossip, or digital spaces versus embodied interactions. Create a simple map showing these rooms and note: you cannot be in all rooms simultaneously, and different stories are happening in each.

Step 2: Position Story Collectors in Multiple Rooms

You need multiple observers to track simultaneous story performances. If you're a solo consultant, you'll need to move through rooms systematically over time. If you're a team, position people in different rooms. The goal is gathering story fragments from across the Tamaraland, not achieving complete coverage (which is impossible). Instruct collectors to listen for:

Terse story performances in everyday conversation
What speakers assume listeners know (the silently filled-in portions)
Challenges and revisions during the telling
Who's performing which stories for which audiences
Which stories get retold frequently versus told once and forgotten

Step 3: Track the Four Story Types

For each room in your Tamaraland map, collect examples of precedent stories, future-directed stories, living stories, and counter-stories. Use a simple matrix:

Room/Space	Precedent Stories	Future-Directed	Living Stories	Counter-Stories
Executive Suite	[Examples]	[Examples]	[Examples]	[Examples]
Middle Management	[Examples]	[Examples]	[Examples]	[Examples]
Frontline Staff	[Examples]	[Examples]	[Examples]	[Examples]

Don't try to capture complete stories. Capture the fragments, the terse performances, the story openings that never get finished. That's the real data.

Step 4: Identify Story Patterns and Contradictions

Once you've collected fragments across the Tamaraland, analyze for patterns:

Dominant Stories: Which stories get performed most frequently? Who performs them? Which rooms embrace them versus resist them?
Story Contradictions: Where do stories from different rooms directly contradict each other? (Example: executives telling growth stories while operations tells survival stories)
Silent Stories: What aren't people talking about? What topics provoke uncomfortable silence when raised?
Marginalized Voices: Whose counter-stories are getting excluded from the dominant narrative? What happens when they try to tell their version?
Story Drift: How does the "same" story morph as it moves through rooms? What gets added, deleted, emphasized, or reversed?

Step 5: Map Political Story Work

Stories in organizations are inherently political. People perform stories to gain advantage, resist authority, justify decisions, and shape collective memory. Track:

Who has storytelling authority? Whose versions get accepted as "truth"?
How are stories used to support or undermine change initiatives?
Which stories are used to include people versus exclude them?
How do power dynamics shape which stories can be told and which must be silenced?

Step 6: Present Audit Findings as Tamaraland Map

Don't present your findings as "the organizational story"—that would deny the polyphonic reality you've discovered. Instead, present the Tamaraland map showing simultaneous, competing storylines. Use visuals showing:

Different rooms and the distinct stories in each
Arrows showing how stories move and morph across spaces
Dominant stories (thick lines) versus marginalized counter-stories (dotted lines)
Contradictions, gaps, and silences

Your job isn't to resolve contradictions into false coherence. Your job is making the polyphonic reality visible so the organization can work with it.

Step 7: Design Story Interventions

Once the audit reveals the storytelling landscape, you can design interventions:

Story Bridging: Create forums where people from different rooms can perform their stories to each other
Counter-Story Amplification: Give marginalized voices platforms to tell their versions
Story Challenge Sessions: Facilitate conversations where dominant stories can be questioned and revised
Antenarrative Tracking: Monitor emerging future-directed stories to catch change possibilities early (see Tool 5)

Example: Healthcare System Merger

A regional healthcare system hired me after a merger created massive dysfunction. The storytelling audit revealed why: Hospital A told a precedent story about being the "flagship" with superior clinical care. Hospital B told a counter-story about being the "community hospital" that actually cared about patients versus profits. In executive meetings (one room), leaders performed a future-directed story about "unified excellence." On nursing floors (other rooms), staff performed living stories about resource wars and quality decline. Patient forums (yet another room) surfaced counter-stories about worse outcomes post-merger.

The audit made visible that this wasn't one merger story—it was competing storylines in different Tamaraland rooms with no bridges between them. The intervention involved creating cross-room story sessions where Hospital A and Hospital B staff performed their precedent stories to each other, then co-created new future-directed stories that honored both legacies. Nursing staff finally got to tell their living stories of struggle to executives. Patient counter-stories were integrated into quality improvement initiatives instead of dismissed as "complaints."

Six months later, storytelling patterns had shifted. The organization hadn't achieved false unity—it still had multiple stories in different rooms. But the stories were in dialogue rather than opposition, and marginalized voices had more authority in collective sensemaking.

Key Takeaways

Every organization is a storytelling organization where stories constitute identity, power, and change
Organizations are Tamaralands with multiple simultaneous storylines in different rooms—you cannot be in all rooms at once
Track four story types: precedent stories, future-directed stories, living stories, and counter-stories
Stories are performances, not texts—they vary by context, get challenged mid-telling, and morph across spaces
Collective storytelling systems mean no individual holds the complete story; institutional memory is distributed
Don't resolve contradictions—make polyphonic reality visible so organizations can work with it
Counter-stories matter—marginalized voices tell crucial stories that dominant narratives exclude
Use audit findings to design story interventions that bridge rooms, amplify silenced voices, and enable dialogue across difference

🔍 Tool 2: Consulting in Storytelling Organizations

The Diagnostic Voice: "I see the errors in how this organization handles its many voices." Every storytelling organization makes predictable mistakes when dealing with polyphony—the multiple, competing voices that constitute organizational reality. This tool applies Mikhail Bakhtin's framework to diagnose six critical errors: monologism (forcing all voices into one official story), finalization (prematurely closing people's stories as "finished"), theoretism (abstracting people into categories instead of seeing their unique voices), secondhand discourse (repeating hollow corporate-speak), carnival suppression (eliminating playful challenge to authority), and dialogue avoidance (preventing genuine multi-voiced conversation). You're the critical diagnostician who names what's going wrong: "Your organization is committing monologism, and it's costing you innovation, engagement, and authentic change." This is precision consulting that identifies the specific polyphony failures causing dysfunction.

Mikhail Bakhtin's Polyphony and Errors Consultants fall into Transforming 'Storytelling Organizations'

Mikhial identifies the serious errors in Polyphony that earlier author-thinkers made concerning Dostoeveky's approach to Polyphony. Each error helps us understand how to consult the Storytelling Organization. They constitute a Toolkit for consultants and coaches.

🧠 Summary Table: Polyphony Errors in Tamaraland

Error Type	Impact on Tamaraland	Boje’s Remediation
Monologic Hierarchy	Managerial dominance, silenced voices	Antenarrative disruption, story audits
Deterministic Mechanism	Mechanized storytelling, predictable change	Quantum storytelling, antenarrative tracking
Ideological Simplification	Stories reduced to binary categories	True storytelling ethics, contradiction prompts
Neglect of Unfinalizability	Premature closure of stories	Enthinkment, reflective journaling
Authorial Puppetization	Stakeholders used to validate leadership scripts	Agential antenarratives, role-play restorying

📌 Breakdown of Consultant Errors in Polyphony Transformation of Storytelling Organizaitons

Each row represents a Bakhtinian error, showing:

🔴 Impact on the consulting process
🔵 Remediation strategy using GrowthOD.com tools

Scholar	Error Type	Impact on Consulting Toolbox	Remediation Strategy
Komarovich	Monologic hierarchy	Reinforces dominant managerial narratives	Disrupt hierarchy with bottom-up prompts
Englehardt	Deterministic mechanism	Mechanizes storytelling, seeks resolution too quickly	Embrace emergent, open-ended storytelling
Askoldov/Grossman	Ideological simplification	Categorizes stories, loses nuance	Invite complexity and contradiction
Kaus	Neglect of unfinalizability	Pushes for closure, treats stories as static	Encourage iterative, evolving storytelling
Vyacheslav	Authorial puppetization	Uses stories to validate pre-set agendas	Facilitate co-creation and reframing

Next, See YouTube of Formal Axiology Critique and Value Capture and Dostoevsky Polyphony

Consulting in Storytelling Organizations Toolkit is affected by several Bakhtinian polyphony errors as identified in critiques of scholars like Vyacheslav Komarovich, Askoldov, Grossman, Kaus, and Englehardt. Here's a breakdown of how each error manifests and how it can distort the effectiveness of the consulting toolbox:

Five Errors Consultants comit when transforming
Storyteling Organizations to Polyphony

David Boje and colleagues define Storytelling Organizations as dynamic entities where narrative and storytelling are central to how organizations make sense of themselves and their environment. In his book Storytelling Organizations (2008), Boje emphasizes that:

🧭 Core Definition

A Storytelling Organization is one in which storytelling is not just a communication tool but a fundamental process through which strategy, development, learning, and identity are shaped. [Storytelli...ations Inc]

Mind Map of Formal Axiology Critique and Value Capture and Dostoevsky Polyphony

Click Here for Expanded Mind Map

🔍 Key Characteristics of Storytelling Organizations

Narrative as Strategy
Stories are used to frame organizational goals, justify decisions, and align members around shared visions.
Multiplicity of Voices
Organizations contain official stories, shadow stories, and antenarratives—each offering different perspectives and tensions.
Temporal Complexity
Storytelling spans past, present, and future—Boje introduces antenarratives as pre-narrative fragments that forecast possible futures.
Living Stories
Stories are not static; they evolve through interaction, conflict, and reinterpretation. This aligns with Bakhtin’s concept of unfinalizability.
Restorying and Change
Storytelling is a method for organizational change, allowing members to restory dominant narratives and surface marginalized voices.
Ethical and Dialogic Engagement
Storytelling organizations are ethically committed to dialogue, resisting monologic control and deterministic systems.

🔑 Core Features of Dostoevsky’s Polyphony

Plurality of Independent Voices
Each character in Dostoevsky’s novels is treated as a fully autonomous consciousness. These voices are not subordinated to the author’s ideology or narrative control—they exist in genuine dialogue with one another.
Unmerged Consciousnesses
Unlike traditional novels where characters serve the author’s vision, Dostoevsky’s characters are not objectified or reduced to ideological types. They are subjects, capable of engaging in philosophical and ethical debate.
Dialogic Interaction
The novel becomes a carnival of ideas, where no single voice dominates. The author does not impose a final word but allows open-ended, unfinalizable dialogue among characters.
Author as a Creator of Dialogue, Not a Dictator of Meaning
Dostoevsky’s authorial role is unique: he does not resolve the ideological conflicts but creates the conditions for their coexistence. Bakhtin calls this the “polyphonic author”—one who orchestrates dialogue without collapsing it into monologue.
Ethical Commitment to Human Plurality
Polyphony is not just a stylistic device—it reflects a deep ethical stance. It honors the irreducible otherness of each voice and resists totalizing systems of thought.

🔴 1. Komarovich’s Monologic Will (Hierarchy Error)

Error Description:
Komarovich reduces polyphony to a hierarchical structure where voices are subordinated to a dominant authorial or managerial will.