Business storytelling, visual communication, and presentations

Everyday Business Storytelling Summary: From Data to a Decision

*Everyday Business Storytelling* offers a practical way to organize business information around people, a consequential problem, a central idea, and a resolution an audience can understand.

One-Sentence Answer

Everyday Business Storytelling offers a practical way to organize business information around people, a consequential problem, a central idea, and a resolution an audience can understand.

What The Book Is About

Janine Kurnoff and Lee Lazarus, co-founders of The Presentation Company, address a familiar problem: a communicator has collected useful information, but the audience cannot see what it means or why it matters. The answer is to construct a narrative before decorating the information.

The authors' book page presents the approach as usable across ordinary business formats, including project updates and quarterly reviews. That everyday emphasis distinguishes the book from advice focused entirely on a memorable keynote or an inspirational personal story.

Their company's explanation of the framework names four signposts—setting, characters, conflict, and resolution—alongside a big idea. These are not five equivalent stages: the big idea connects the problem with the proposed response. The five reading priorities below are editorial groupings for applying the approach, not a replacement model invented by the authors.

Who Should Read It

This is a strong fit for someone who has enough information but struggles to make a recommendation easy to follow. Analysts, project managers, sales teams, and department leaders can all encounter that problem. The method is especially relevant when audiences must move between data, interpretation, and action without having time to reconstruct the reasoning themselves.

Read it with a real communication task beside you. A weekly update or a single proposal section may be more useful practice material than a hypothetical conference speech. The book's visual emphasis will appeal to people who work with slides, but the underlying organization also suits short documents and conversations.

Choose another resource first if your main need is advanced chart construction, statistical analysis, or a systematic review of research on memory. The book includes science-based explanations for storytelling; this guide does not treat simplified brain descriptions or recall figures as universal proof. Its recommendation rests on the practical communication method. It is also not a license to turn uncertain evidence into a smooth, overly conclusive story.

Main Summary

Kurnoff and Lazarus distinguish possessing information from communicating an insight. A pile of findings, even attractively presented, asks the audience to perform the difficult work of identifying the important problem and deciding what follows. A business story gives those findings a relationship: something is happening, someone is affected, an obstacle matters, and a response deserves consideration.

The four signposts provide that relationship. Setting supplies enough context to understand the situation. Characters identify who or what the audience should care about. Conflict reveals the tension that makes a response necessary. Resolution explains how the proposed action addresses the problem. The big idea gives the story a memorable center rather than leaving the audience with a collection of disconnected details.

This is not a demand for fictional drama. In a business setting, a character might be a customer group, an operating team, or the audience itself. Conflict might be the gap between a service promise and the process available to deliver it. The storyteller's responsibility is to make the real relationship visible, not manufacture danger or invent a heroic success.

Visuals then serve the story. A chart, diagram, or short heading should help the audience see a relevant relationship. Its purpose is weakened when it merely proves that the presenter has done extensive analysis. The same logic travels between a deck, a one-page note, and an email: the expression changes while the central reasoning remains recognizable.

The book is most useful as a working method for ordinary communication. Its limits become important when narrative tidiness hides uncertainty, alternative explanations, or tradeoffs. This guide therefore pairs its narrative approach with an editorial evidence check. The original application below turns a confusing appointment update into a bounded proposal, while keeping the distinction between observed facts, hypotheses, and the action being requested.

Key Ideas

1. Give The Audience A Situation And Someone To Care About

Setting and characters answer two basic questions: what is happening, and to whom does it matter? Without that grounding, even an accurate metric can feel arbitrary. A presentation may display a decline in completion rates while never explaining which customers are affected or what they are trying to accomplish. The information is visible, but its significance is difficult to locate.

In the authors' framework, characters do not have to be named protagonists in a personal anecdote. They can be an identifiable group whose needs make the decision meaningful. This allows business storytelling to remain factual. A support team handling repeated questions can be a relevant character without inventing a composite employee or putting words in a customer's mouth.

The practical choice is how much context this audience needs. A working team already familiar with an issue may need only one orienting sentence. A new executive may need an explanation of the service and the affected group. More background is not automatically more helpful; include the information that makes the coming problem intelligible.

An editorial check is to remove the chart and ask a reader to describe the situation in plain language. If they cannot say who faces what difficulty, the communication probably needs grounding before additional detail. Avoid selecting a sympathetic character merely to steer emotion. The person or group should have a real relationship to the decision, and the evidence should support the way their situation is described.

2. Make Conflict A Real Decision Problem

Conflict supplies movement because it explains why the current situation cannot simply continue unchanged. In business communication, that tension can be small and practical. A team has promised a response time that its current routing process cannot consistently meet. A customer can begin a task online but must repeat the same information by phone. Neither situation requires a villain to become worth discussing.

The danger is overstating the conflict to make the story more compelling. An inconvenience is not automatically a crisis. A short observation period does not establish a long-term trend. If the evidence shows a problem in one group, the story should not quietly expand it to the whole organization. Narrative emphasis must remain proportionate to what is known.

A useful editorial question is what choice becomes necessary because of the tension. If no action, investigation, or tradeoff follows, you may have selected an interesting fact rather than a business problem. Conversely, if your proposed action could fit any problem, the conflict is probably too vague.

Describe the gap in terms the audience can examine. State the current condition, the desired condition, and the relevant constraint. Then show the evidence for the gap and identify anything still uncertain. This application preserves the authors' emphasis on an audience having a reason to care while giving readers a way to resist inflated drama. Good tension clarifies a decision; it does not pressure people to accept an unsupported conclusion.

3. Let One Big Idea Connect The Problem With The Response

The big idea is the central point the audience should retain. It is more useful than a topic label because it expresses an interpretation or direction. A heading such as customer onboarding identifies a subject; a statement that onboarding needs one clear owner expresses something the audience can examine and debate.

In the authors' explanation, the big idea forms a bridge between conflict and resolution. That role helps distinguish it from both the supporting evidence and the detailed action plan. The evidence shows what is happening. The big idea says what matters about it. The resolution explains the proposed way forward. Collapsing these functions can produce either an unsupported slogan or a recommendation buried under findings.

Try writing the idea without a chart or slide title. Can you express the point in a complete sentence that a colleague could repeat? Then ask what evidence would make that sentence wrong. This second question is an editorial addition: it prevents the search for a memorable line from hardening into a refusal to consider contradictory information.

The big idea should also survive compression. A short email may omit several examples from the longer presentation, but it should not reverse or exaggerate the conclusion. If the longer analysis recommends testing a change, the email should not announce that the change is proven. Consistency across formats is valuable only when the shared idea remains faithful to the underlying evidence and decision.

4. Make Visuals Explain A Relationship

The authors emphasize developing the story before selecting visuals. That order matters because a large existing slide collection can dictate the argument by accident. The presenter assembles available charts, adds transitions, and hopes the audience discovers a conclusion. Starting from the story makes it possible to choose which evidence needs to be seen and what the visual must help explain.

A visual earns its place when it reveals a relationship that matters. It might show where a process breaks, how two options differ, or which part of a trend deserves attention. A decorative photograph may add atmosphere but cannot substitute for that explanation. Likewise, a complicated chart can be accurate while imposing unnecessary interpretation work on the audience.

An editorial test is to complete the sentence: this visual helps the audience see that. If the sentence ends with a vague claim about professionalism or engagement, reconsider the visual. If it names a specific comparison, check that labels, scale, and context make the comparison fair. Simplification must not conceal a denominator, omit a relevant category, or make a small difference appear enormous.

A helpful working sequence is to state the point, select the smallest adequate display, and add an explanation of its implication. Keep detailed evidence available when the decision warrants scrutiny. The book's practical value lies in coordinating narrative and display; the responsible application is to make information easier to understand without making it harder to challenge.

5. Adapt The Story To The Conversation

Everyday business communication rarely happens as an uninterrupted performance. An executive interrupts, a colleague asks for the recommendation first, or an email recipient already understands the context. A useful narrative framework should help the speaker navigate these conditions rather than demand that every audience sit through the same sequence.

Lee Lazarus's article on pivoting a presentation applies the framework to that problem. When people need more context, return to the situation and conflict; when they are ready for the recommendation, move toward it. Preparation gives the communicator a map, not a reason to ignore the people in front of them.

An editorial practice is to prepare three versions: a one-sentence central idea, a short explanation, and a fuller argument with evidence. The short version should orient the listener and invite the next useful question. It should not replace a needed risk explanation. The fuller version should answer questions without forcing everyone to receive every detail at once.

Across those versions, preserve the meaning of the request and the limits of the evidence. You may shorten the setting for a knowledgeable audience or explain terminology for a new one. You should not tell one audience that an outcome is uncertain and another that it is guaranteed. Adaptation is successful when different listeners can understand the same responsible recommendation in forms suited to their needs.

Practical Takeaways

  • Draft a plain-language situation. Describe what is happening before opening the slide template. Include only the background this audience needs.
  • Identify the affected group honestly. Use a real audience or customer category; label an imagined example rather than presenting it as a quotation or actual case.
  • State the consequential gap. Explain what is obstructing a desired outcome and why the audience needs to consider a response now.
  • Write one central sentence. Replace a topic heading with an idea that could be accepted, challenged, or refined.
  • Separate facts from interpretation. Mark what the data show, what you infer, and what remains a hypothesis.
  • Assign each visual a job. Choose the relationship it should make visible, then check scale, labels, and missing context.
  • Make the resolution actionable. Name the proposed step, decision owner, and condition for evaluating it. A hopeful ending is insufficient.
  • Prepare a shorter route. Practice explaining the idea without the full deck, while keeping its uncertainty and requested action intact.

These exercises are this guide's applications. They are not evidence that storytelling will produce a particular conversion rate, memory improvement, or business outcome.

How To Apply It

An Original Case: Explaining A Booking Problem

This is an imagined editorial example, not a case from the book or a report of customer testing.

A training provider has a confusing appointment report. The original update includes website visits, calls, cancellations, staffing notes, and a screenshot of the booking form. It ends with a request for a new website. The directors cannot tell why that investment follows from the information.

The writer starts with setting and characters: new customers try to book an introductory session, and the service team handles questions when the process is unclear. The conflict is a mismatch between the provider's promise of easy booking and the sequence of explanations customers must follow. In this hypothetical case, a review of the form shows that availability is explained only after contact details are submitted. That observation can be stated directly. It does not prove why every customer leaves.

The central idea becomes a proposal to make availability clear before asking people to commit their information. This is narrower than replacing the entire website and easier to connect with the observed problem. The proposed resolution is a limited change to the booking explanation, followed by an agreed evaluation. The writer includes the possibility that some difficulties may arise from scheduling capacity rather than page design.

Turn The Same Reasoning Into Three Formats

For a short email, the writer gives the problem, the central recommendation, and the decision required. For a one-page note, they add a diagram of the current sequence and the proposed sequence, along with the limits of the evidence. For a presentation, they prepare additional detail about alternatives and implementation questions.

The diagram has a specific job: reveal when customers learn about availability. It is not decorated with invented percentages or a fictitious satisfied customer. The recommendation is framed as something to test, since the imagined evidence does not establish the eventual effect.

A colleague then reads the note and answers three questions: who experiences the difficulty, what change is proposed, and what would count against the explanation? If the answers differ from the writer's intent, the draft needs revision. This informal comprehension check can expose a missing link, but it is not a substitute for investigating the actual service problem.

Keep The Story Open To Correction

Before presenting, the writer lists alternatives the narrative could obscure: limited appointment supply, confusing terminology, or customers who are browsing without intending to book. The note need not become a research report, but decision makers need to know which alternatives remain plausible.

This is the guide's main safeguard. Story structure can make reasoning accessible; it can also make an untested explanation feel complete. Use the framework to clarify the next responsible action, then let new evidence change the story.

Notable Ideas, Paraphrased

Information needs a meaningful relationship, not just a more attractive container. Context and an affected group give a problem significance. A central idea helps connect the tension with a response. Visuals should illuminate that reasoning. These are thematic paraphrases, not quotations from Kurnoff and Lazarus.

Best Related Books

  • The Leader's Guide to Storytelling offers a broader leadership storytelling comparison, especially when the purpose extends beyond organizing a business update.
  • The Storyteller's Secret is useful for readers interested in the role of stories in public persuasion. Compare its broader examples with this book's everyday work formats.
  • Storytelling with Data is a more focused route when the display of quantitative evidence is the main challenge.
  • The Presentation Coach helps readers concentrate on preparing and delivering the presentation in which their narrative will be used.

Internal Links

Find more reading paths on the Communication Books home page, or compare different communication problems in best books to improve communication. For the wider responsibility of leadership messaging, explore The Power of Communication.