Presentation structure and visual storytelling

Show and Tell

Name: Show and Tell
Author: Dan Roam

Show and Tell helps readers turn a presentation into a visible story with a clear destination, not a sequence of disconnected slides.

One-Sentence Answer

Show and Tell helps readers turn a presentation into a visible story with a clear destination, not a sequence of disconnected slides.

What The Book Is About

Dan Roam's Show and Tell belongs in the site's public speaking, visual explanation, and presentation cluster. The book's core value is that audiences need a path. A presentation should show what matters, tell why it matters, and guide people toward a point they can remember.

For communicationbooks.space, the useful angle is presentation design before slide design. The reader is not learning decorative graphics; they are learning how to decide what kind of story the audience needs and how visuals support it.

Who Should Read It

Presenters whose slides contain useful material but no memorable path.
Founders and team leads preparing a pitch, update, lesson, or change case.
Teachers and trainers who want visuals to support learning rather than distract.
Readers who like The Back of the Napkin and want a presentation-specific follow-up.

Main Summary

Show and Tell is about designing the audience's journey before designing slides. Dan Roam's presentation advice starts from a simple communication problem: many speakers collect content, arrange it in roughly logical order, and hope the audience finds the point. Roam asks the presenter to choose the kind of story being told and to build the talk around what the audience must see, feel, understand, and do.

The book is especially useful because it treats presentation as a visual and verbal experience. A presenter is not only transferring information. They are guiding attention. That guidance changes depending on whether the speaker is reporting results, explaining an idea, teaching a process, pitching a proposal, or inviting change. A report may need a clean situation-complication-resolution flow. A lesson may need examples and progressive complexity. A pitch may need contrast between the current pain and the promised future.

For readers, the practical value is the planning discipline. Before making slides, write the ending. What should the audience remember or decide? Then identify the story path that gets them there. Only after that should the speaker sketch visuals, choose evidence, and rehearse transitions. The book is a strong companion to Presentation Zen, which emphasizes simplicity and restraint, and Resonate, which goes deeper into persuasive presentation arcs.

Show and Tell should be treated as a pre-slide planning book. Its strongest value appears before the presenter commits to a deck, because it helps decide what kind of story the audience needs. A report, pitch, explanation, and lesson can all look like slide decks, but they ask the audience to do different work. Roam's framing helps the speaker select a path, choose visuals that support that path, and end with a memorable action or idea. That makes it especially useful for speakers who have good material but weak sequence.

Key Ideas

1. The audience needs a path

A presentation works when listeners can feel where they are in the journey. Random facts create effort; sequence creates comprehension.

The path is what stops a presentation from becoming a pile of facts. The audience should know why each section follows the last one. A good path gives listeners confidence that the speaker is taking them somewhere worth reaching.

Why it matters: a path gives the audience confidence that the speaker is not simply browsing through material. Apply this by naming each section as a step in the journey, then cutting slides that do not move the audience toward the promised endpoint.

A Roam-style path can be tested with sticky notes before slides exist. Write one note for the audience's starting belief, one for the problem, one for the new picture, one for proof, and one for the ending. If the speaker cannot place a slide idea on that path, the slide is probably material, not story.

For a product strategy talk, the sticky notes might read: current confusion, customer cost, new model, proof from research, and decision requested. This low-fidelity sequence exposes missing logic before the speaker spends hours polishing slides.

This also helps with timing: the speaker can see which section deserves five minutes and which section only needs one transition sentence.

2. Seeing supports believing

Simple visuals help an audience hold relationships, tradeoffs, and movement in mind. A visual should clarify the point, not decorate it.

A picture can make an abstract relationship visible: before and after, problem and solution, parts and whole, journey and destination. Roam's approach is not about artistic skill. It is about giving the audience a simple visual object to understand and remember.

Why it matters: a picture can hold a relationship in memory longer than a paragraph can. Apply it by sketching the core idea as a journey, contrast, or system before deciding whether it deserves a polished slide.

A visual in this book's spirit should clarify the journey. A product roadmap talk might need a before-and-after map; a training talk might need a simple model that learners revisit; a change presentation might need a gap between current and future state. The visual is useful because it carries the audience through the talk.

A visual journey might show a customer's path from signup to first value, with the failure point highlighted. That picture gives the talk a spine. The presenter can then use stories, numbers, and recommendations to support the same visible path.

For internal strategy talks, that picture can become a shared artifact the team revises during discussion instead of a fixed slide nobody questions.

3. Story type changes structure

A sales pitch, lesson, report, and transformation story do not need the same arc. Choose the story type before building slides.

A pitch, explanation, report, training session, and change story each need a different emphasis. If the speaker chooses the wrong story type, the talk may feel polished but mismatched. For example, a change case needs emotional contrast and action, while a technical explanation needs sequence and clarity.

Why it matters: story type prevents mismatched presentations. Apply this by choosing whether the talk is a report, explanation, pitch, lesson, or change case. The answer determines what the opening must promise and what the ending must ask for.

Choosing the story type changes what evidence belongs. A report needs what changed and why; a pitch needs why now and why us; a lesson needs sequence and practice; a change case needs tension and commitment. Naming the type prevents the speaker from using the same agenda for every communication job.

A training session, for example, should not copy the rhythm of an investor pitch. Learners need concept, demonstration, practice, and correction. A pitch audience needs urgency, credibility, differentiation, and action. Roam's story-type distinction protects those differences.

A speaker can test the choice by asking what the audience should do afterward: understand, remember, decide, practice, or commit.

4. The opening sets the contract

The audience should quickly know the problem, promise, and reason to care. A weak opening forces later slides to repair attention.

The first moments should tell the audience why this presentation deserves attention. That may mean naming the problem, promising a useful answer, or showing a contrast that creates curiosity. A slow administrative opening wastes the audience's highest attention.

Why it matters: the opening is where the audience decides how much effort to invest. Apply this by replacing background throat-clearing with a direct problem, surprising contrast, or useful promise in the first minute.

A stronger opening can be built from a contrast: 'Our customers complete onboarding, but they do not reach the first value moment.' That opening gives the audience a reason to listen. It is more useful than starting with agenda logistics because it creates the question the presentation will answer.

The opening can also use a simple drawing or object. A sketch of the current process with one obvious bottleneck may create more attention than a title slide. The test is whether the opening creates a question the audience wants answered.

The opening should make the audience curious about the same problem the speaker intends to solve, not a more dramatic but unrelated hook.

5. The ending needs action or memory

A presentation should close with the decision, behavior, or idea the audience should carry forward.

Why it matters: weak endings make useful talks hard to retell. Apply this by writing the final decision, action, or image before designing the deck. Then make the last slide carry that point instead of fading into generic Q&A.

The ending should not fade into 'any questions?' before the main point lands. The audience needs a final sentence, decision, or image that anchors the presentation. A strong ending makes the talk easier to retell.

For the ending, write the sentence the audience should repeat to someone who missed the talk. If that sentence is vague, the close is not ready. The last slide should anchor the decision, behavior, or mental model, so Q&A extends the point instead of replacing it.

A strong close might return to the opening visual with the missing piece filled in. That creates closure without adding another concept. The audience leaves with a before-and-after picture instead of only a list of slide titles.

This is why a close should usually be rehearsed word for word; the final sentence carries more weight than most middle slides.

The close should also tell the audience what not to do next, such as avoiding another analysis cycle when the talk has already established the decision.

Practical Takeaways

Write the ending before designing the first slide.
Choose the presentation story type before choosing visuals.
Use sketches to test the flow before opening slide software.
Make every visual answer a question the audience has.
Remove slides that do not move the audience toward the ending.
Rehearse the transition between ideas, not only the words on each slide.

How To Apply It

For your next presentation, draw the journey as five boxes: audience now, problem, discovery, proof, and next action. If a planned slide does not fit one box, cut or move it.

A useful way to apply the book is to diagnose the presentation before writing speaker notes. If the talk is a report, the audience needs situation, change, implication, and decision. If it is a teaching talk, the audience needs a simple model, worked example, practice, and recap. If it is a pitch, the audience needs current pain, better future, proof, and next step. Those distinctions keep the presenter from using the same slide rhythm for every situation. Show and Tell is strongest when the speaker has too many possible slides and needs a story spine. Once the spine is clear, Presentation Zen can help simplify the deck and Steal the Show can help rehearse the delivery.

Original Value: When This Book Is Most Useful

Read Show and Tell when your slides are presentable but the talk still feels shapeless. It is less useful if you need advanced visual design rules or performance coaching. Its sweet spot is the planning stage: choosing the story type, sketching the audience journey, and making sure every slide has a reason to exist.

Do not use it as a replacement for audience research or evidence. The book helps shape the story, but the presenter still needs a real claim, credible support, and enough knowledge of the audience's constraints. If the problem is fear of speaking, start with a confidence book first; if the problem is data proof, pair it with a chart or data-story guide.