Key Takeaways
Use a short story to make a complex change imaginable from inside.
A story can start movement. Stephen Denning calls a springboard story a brief account that helps listeners grasp how an organization could change by imagining an analogous situation in their own work. His first example came from a colleague: a health worker in rural Zambia used the US Centers for Disease Control website to find guidance on treating malaria. The episode made knowledge sharing tangible. Instead of defining a large organizational program, it invited listeners to picture expertise reaching someone who needed it.
The listener completes the leap. The story’s purpose is not to prove that one online answer can transform an institution. It gives people a vivid starting point for imagining similar possibilities in familiar settings. A story can illuminate a sound idea, but it cannot rescue a bad one or substitute for evidence.
The useful shift is from treating communication as a delivery problem to treating it as a sense-making problem. Listeners do not simply receive a finished proposal; they supply context, implications, and possible applications. That participation helps explain why a tiny anecdote can matter more than a dense briefing. It also creates a responsibility: leaders should distinguish a compelling possibility from demonstrated results. A story can open inquiry, but the inquiry still has to test whether the proposed change works.
Redefine the problem before repairing the system.
The initial assignment was too small. Denning was asked to examine the World Bank’s information systems. Their failures were familiar: repeated reports documented problems, yet each cycle led to another study. Even routine loan disbursements could take weeks as paper applications moved through offices and queues. Fixing those systems might improve efficiency without changing what the institution offered.
The deeper opportunity was knowledge. The Bank’s clients increasingly wanted access to the best expertise across the organization, not only the advice of whichever specialist happened to be assigned. Denning argued that the Bank needed to act more deliberately as a knowledge broker. The Zambia anecdote showed that expertise could cross vast distances, while a visit to a software firm suggested how professionals might get relevant guidance at the moment of need. The strategic question shifted from managing information to sharing know-how with clients and partners.
This is a distinction between repairing a process and reconsidering the value an organization exists to provide. Better technology can speed an old model without making it more useful to the people it serves. Denning’s pivot is persuasive because it begins with changing client expectations, not with enthusiasm for a new management label. Still, declaring knowledge the new strategic center does not make expertise easy to organize. It requires curation, trusted contributors, and incentives that make sharing part of real work.
Make the story familiar enough to connect, strange enough to wake people.
Build around one recognizable predicament. In one example, a World Bank task manager in the Central African Republic needed advice about a minority shareholder’s rights while helping a government privatize a telephone company. Rather than wait until returning to Washington, he asked a professional network for help. He received relevant experience from Kenya and, unexpectedly, Morocco’s oil industry. Advice arrived quickly enough to inform the next day’s discussion.
The construction matters. The protagonist’s problem resembles situations the audience knows, so listeners can imagine being in that position. The quick response violates their expectation that expertise will be slow or hard to find. The story should be simple enough to follow, unusual enough to attract attention, and relevant enough to suggest how the audience’s own work could change. Too much technical detail can distract listeners into debating the case instead of grasping the principle.
The story’s tension comes from a useful combination: recognition of the problem and surprise at its resolution. This resembles good case teaching, where a concrete dilemma gives abstract principles something to attach to. The discipline is in choosing details that serve the transfer, rather than displaying everything known about the episode. But relevance is audience-specific. A predicament that feels ordinary to one group may seem remote to another, so storytellers need to test their examples instead of assuming universal resonance.
Leave gaps so listeners build the change into their own work.
Do not script every conclusion. A story about a World Bank team in Chile showed how a client’s question about teachers could be answered by gathering experience from colleagues working in other countries. The client received a useful response within hours. Denning then extended the account: if the experience were organized for reuse, other teams might find it through an internal knowledge base, and clients might eventually access it online. That second part was a projection, not an accomplished result.
The gap invites ownership. Listeners could imagine what comparable knowledge sharing might mean in their own jobs. This is the implicit story: the listener’s own account of how the change might work in a familiar setting. Denning found that people sometimes responded as if they had generated the idea themselves. That ownership can encourage action, but storytellers must mark the difference between what happened and what they are extrapolating.
Leaving interpretive room turns communication into a form of participation. The audience can adapt an idea to local knowledge that the presenter does not possess, which is especially valuable when a change is still taking shape. The Chile example also exposes an ethical boundary: productive ambiguity is not the same as blurred truth. Clearly labeling a projection preserves trust while still allowing imagination. The strongest stories invite listeners to complete the design, not to mistake an aspiration for a delivered service.
Test the audience’s context; the same story can inspire or alienate.
One presentation met two different rooms. In London, Denning spoke to people already wrestling with knowledge management and struggling to explain it to their organizations. They welcomed his account of using stories and quickly saw its relevance. In Bern, he delivered essentially the same presentation to employees who had been told to attend. Some were uneasy about digital technology, and organizational politics were already in play. Their questions focused on the technology and whether the idea suited Switzerland. The presentation did not create the same shared understanding.
Readiness is part of the message. The Bern audience did not necessarily reject change itself; the story failed to connect with their assumptions, anxieties, and immediate concerns. Denning concluded that he should have learned more about the local situation and tailored the account to it. A story that works in one organization is not automatically portable to another.
This contrast makes audience analysis more than a presentation technique. People interpret a proposal through their sense of identity, risk, and institutional history. A leader who labels every objection resistance misses information about what the change threatens or fails to address. At the same time, tailoring should not become simple appeasement. The aim is to make the idea intelligible in local terms, then allow genuine questions to surface. A story’s failure can be useful feedback about the relationship between the proposal and its audience.
Let narrative open the door, then use analysis to check the idea.
Charts struggled with a living system. Denning had relied on diagrams to explain knowledge sharing, but as the program grew, the charts became harder to follow. Adding communities of practice and other missing elements made them still more complicated. A presentation about education work in Yemen proved clearer: a team needed advice, a help service connected it to a professional community, and expertise from Kenya helped the team respond to its client. The story made the human relationships visible without requiring listeners to decipher a crowded diagram.
Narrative is a complement, not a replacement. Denning argues that stories help people imagine complex, changing relationships, while analysis can make implications explicit and test whether the underlying proposal is sound. The Yemen account opened the conversation; it did not establish that every part of a knowledge-sharing program would succeed.
The distinction is not between emotional stories and rational analysis. It is between modes of understanding that serve different purposes. A narrative helps people perceive relationships and possibilities; analysis can examine costs, conditions, and evidence. The sequence matters when an audience is disengaged: a diagram may demand abstraction before listeners understand why the subject matters. Yet vivid stories can also overemphasize unusual successes. Analytical follow-through is essential for checking representativeness and preventing a compelling example from carrying more evidentiary weight than it deserves.
Perform the story live; a booklet cannot recreate the encounter.
The telling mattered more than the artifact. Denning’s team collected examples of knowledge sharing and distributed them in newsletters and a booklet. The material attracted some interest but did not generate the energy of live presentations. Video also had limited impact in his experience. He concluded that the audience’s response to a story depended partly on the interaction: a speaker could adjust tone, pacing, and emphasis while noticing listeners’ reactions.
Prepare the setting, not just the words. Before an important presentation, Denning checked the room, projector, screen, lighting, and visibility, then rehearsed with smaller audiences. A knowledge fair produced a different kind of storytelling: informal conversations let staff discover relevant tools, expertise, and communities through many brief encounters. Formal performance and open exchange were distinct ways of bringing stories to life.
This account treats communication as an event rather than a document, which explains why the same text can land differently when spoken to a responsive audience. Preparation frees the speaker’s attention for that interaction. The limitation is obvious: a strategy that depends on a particular presenter’s presence can be difficult to scale. Organizations can preserve the interactive quality by helping more people tell and discuss examples, rather than assuming that a polished recording or an archive of stories will do the work on its own.
Choose your structure to match readiness, urgency, and what remains unknown.
The order can change the reception. Denning used four practical shapes for presentations:
1. Begin with a story, then draw out its implications when the audience is ready to listen.
2. Tell several stories when the change is emerging and its implementation details are not settled.
3. Describe a familiar problem first when an unreceptive audience does not yet see a reason to consider change.
4. Tell one concise story when time is extremely limited.
Sequence shapes attention. When Denning began with analysis, listeners could focus on whether his diagnosis was accurate. Starting with a story could instead establish a shared point of reference, so later analysis addressed problems the audience could picture. The forms are options, not a fixed recipe. The presenter must judge what the audience knows, what it is ready to hear, and whether the change itself is sufficiently clear.
This is a communication strategy based on diagnosis rather than a universal formula. It recognizes that readiness, urgency, and uncertainty are different constraints, and that a presentation can be arranged to meet them. The multi-story approach is especially apt when the organization has not worked out all the details, since pretending to possess a complete blueprint can close down useful contributions. Still, structure cannot compensate for a weak proposal. The audience’s response should inform both the message and the underlying plan.
Resource the communities behind the story, not just the story itself.
A compelling example needs an operating system. During a period of global financial turmoil, Denning used a Pakistan highways case to show knowledge sharing in action. A task manager asked a network of specialists and partners for advice about pavement technology. Experience from Jordan, Argentina, South Africa, and New Zealand helped inform a timely response to the government. The example renewed senior-level interest in the knowledge program.
Momentum needs structure. Denning’s account also shows the work required beyond persuasion: communities of practice needed support, budgets had to reach their intended purpose, and staff needed ways to find and reuse expertise. As the program matured, measurement and administration became more important, but overly rigid systems could constrain the collaboration that made sharing valuable. The story can catalyze a change; people, resources, and adaptable processes must carry it into practice.
This is the operational test of the book’s central claim. If a story generates enthusiasm but no time, funding, or access to colleagues, it has changed perceptions without changing the work. Conversely, turning every exchange into a metric or formal repository can smother the voluntary relationships that make expertise travel. Leaders need both accountability and room for adaptation. They should verify what the story demonstrates, fund the collaboration it depends on, and keep listening for problems that the official success narrative might conceal.
Analysis
The book’s strongest insight is that organizational communication is not simply the transfer of a proposal from an informed speaker to an uninformed audience. People interpret change through experience, identity, and local knowledge. A brief story can give them a situation to inhabit, then prompt them to connect it to concerns the speaker could not have anticipated. In that sense, storytelling is not merely a softer form of explanation. It is a method for eliciting distributed understanding and, sometimes, distributed design.
Denning’s World Bank narrative also makes the mechanism unusually concrete. The change began amid institutional inertia, repeated reports, and uncertainty about the organization’s purpose. The Zambia, Chile, Yemen, and Pakistan examples each made a different aspect of knowledge sharing visible. Their effect depended on a recognizable protagonist and a practical problem, not on a grand definition. The contrast between London and Bern is especially important: a story’s effectiveness belongs to the relationship between story and audience, not to the words alone.
The same mechanism creates risks. A memorable success can be mistaken for evidence that a system works generally. An incomplete account can direct attention toward a preferred future while muting costs, failures, or competing interests. Listeners may co-create the idea, but they do so within unequal organizational settings where some voices carry more authority than others. Narrative participation is not automatically democratic.
The soundest use of Denning’s method is therefore staged. First, choose a real, relevant story and clearly label any imagined extension. Next, use the audience’s response to identify assumptions and practical questions. Then test the underlying proposal with analysis, counterexamples, and operational evidence. Finally, resource the communities and processes required to make the promise real. Stories can help people see a new organizational possibility, but sustained change depends on whether the institution builds conditions that let the possibility survive scrutiny and everyday work.
Glossary
Springboard story
Story that catalyzes understandingA brief, relevant account that helps an audience imagine how a complex organization or community might change. It does not primarily communicate a large body of information. Instead, it gives listeners a starting point for creating an analogous story from their own work and experience, making a possible change easier to understand and act upon.
Implicit story
Listener-created story of changeThe account listeners construct in their own minds as they connect a springboard story to their circumstances, concerns, and goals. It is distinct from the explicit story told by the speaker. Because listeners supply local context and implications, the implicit story can make a proposed change feel self-generated and relevant to their work.
Narrative rationality
A story’s felt plausibilityA way of assessing a story by whether its events and relationships form a coherent, believable account that makes sense to an audience. It differs from scientific proof or legal verification. A story can possess narrative rationality and help listeners interpret a situation, but that quality alone does not establish that its claims are empirically representative or correct.
Community of practice
Group sharing professional know-howA group of people connected by a shared area of work or expertise who exchange experience and help one another solve problems. In Denning’s account, these communities helped locate knowledge across the World Bank and its partners. They were not merely databases: human relationships, coordination, and a supportive setting made it possible for expertise to be requested and shared.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.