Beyond Bullet Points Summary: Build a Decision Storyboard

Key Ideas

1. Write the story before investing in the slides

Atkinson’s first principle puts story planning ahead of slide creation. The practical advantage is that you can examine the relationship between ideas before layouts and images make the existing order feel expensive to change. A collection of attractive slides can still contain a missing argument. Removing bullet points does not by itself supply that argument.

Our library coordinator begins with inherited slides on visitor counts, the building, staff rotas and community events. Every section contains useful information, but the proposed evening pilot appears only at the end. Set the deck aside and write a short account of the audience’s situation: some residents cannot visit during existing hours; the committee can authorize a limited test; the test needs a staffing plan and a review rule. That account identifies the work the presentation must do.

Next, write the ending privately. In this scenario it is a request to approve two later openings each week for six weeks, within a stated staffing allowance, followed by a review. These invented conditions give the story a destination. If the coordinator cannot specify the request, the deck is premature; the proposal itself needs more thought.

Use a plain document or index cards to arrange the explanation. Ask what each part contributes to the route from situation to decision. Move a building-history anecdote to the appendix unless it supplies relevant evidence. This first pass is not an exercise in making the talk entertaining. It is a way to decide what the audience needs before you become attached to an existing collection of slides.

2. Anticipate a reasonable no before asking for yes

The fourth edition explicitly connects decision-oriented information with imagining an audience’s refusal. The publisher’s decision principle and objection principle make this an audience-planning task. It is not permission to pressure someone past an objection that remains unanswered. A well-founded no may reveal a weakness in the recommendation.

In our original case, the coordinator initially assumes the committee simply needs to care more about access. But a committee member could support access and still reject the pilot because the staffing request is unclear. Another might ask whether evening visitors would be new users or merely people shifting their usual visits. These objections concern the proposal’s design, not necessarily resistance to the library’s mission.

Write two plausible reasons for refusal before adding supporting slides. For each, identify what evidence or condition could answer it. The coordinator might show the actual staff coverage arrangement, explain the attendance measure and acknowledge that some effects will remain uncertain after six weeks. If the requested evidence does not exist, state the uncertainty or alter the proposal rather than manufacturing reassurance.

This exercise makes the presentation more specific. It can also reduce unnecessary material: an audience worried about recurring cost does not need ten general slides about the value of libraries. They need an intelligible account of the trial’s cost and limits. Finish by asking whether your imagined objection resembles what these particular listeners would say. Consult a real stakeholder where possible, without presenting the imagined refusal as research you conducted.

3. Make the opening connect the situation to the audience

Atkinson names four early building blocks: Hook, Relevance, Challenge and Desire. The publisher’s explanation relates them to establishing a situation, giving the audience a reason to care and connecting a problem with a desired outcome. They give the beginning work to do beyond announcing the presenter’s name and agenda.

For the library committee, an opening could describe a concrete access difficulty using verified local information. In this fictional application, imagine a documented request from residents whose working hours overlap with the branch’s opening times. The hook draws attention to that situation. Relevance explains why the committee’s decision matters. The challenge is the gap between access needs and existing hours. The desire is a practical way to test broader access without committing to a permanent schedule immediately.

Keep those distinctions clear while writing. A dramatic anecdote may attract attention but fail to establish how widespread the issue is. A desired outcome may sound appealing while hiding its cost. Our coordinator should identify what the anecdote illustrates, what it does not establish and what evidence supports the scale of the problem. Story structure should organize facts rather than promote an isolated example into a general finding.

Read the opening aloud without its illustrations. Can a listener explain whose situation matters, what the difficulty is and what improvement is being considered? Then check the same opening against the eventual request. If it raises a problem the pilot cannot plausibly address, revise either the opening or the proposal. A compelling start earns its place by leading into the actual decision.

4. Use a map and anchors to prioritize the explanation

The fourth edition’s Map, Anchors and Explanation organize the middle of the presentation. The map orients the audience, the anchors identify the major points and the explanation supplies support. Atkinson’s template uses a hierarchy and three principal anchors. The useful discipline is to distinguish a reason from the details that explain or substantiate it.

Our library coordinator chooses three invented anchors: the pilot addresses a specified access gap, existing staff arrangements can support the limited test, and a clear review rule prevents an automatic permanent commitment. Each anchor needs its own explanation. Visitor records may help with the first. A rota and cost assumptions belong under the second. Attendance measures and a review date belong under the third. A statistic does not become an anchor merely because it is interesting.

Test the hierarchy by asking how a detail supports the point above it. A photograph of a crowded event might illustrate activity but say little about routine evening demand. A table of staff hours might answer feasibility, provided that its assumptions are visible. Place material where it explains something, and remove unsupported jumps between a fact and a recommendation.

This organization also helps when time changes. If the committee chair shortens the presentation, preserve the main reasoning and reduce optional detail rather than dropping the final request. Keep backup material available for questions. Three anchors are part of this book’s method, not proof that every subject naturally has exactly three truths. If your argument resists the structure, examine whether it needs narrowing instead of forcing unrelated claims together.

5. Make headlines, narration and visuals work together

Atkinson’s final building blocks connect Headlines, Visuals and Flow. His headline guidance favors concise complete sentences and clear links between ideas. A headline should state a point, while narration and the visible material help listeners understand it. The screen is not simply a storage place for the entire spoken explanation.

In our case, a slide labeled Staffing leaves the conclusion unstated. A more useful original headline is that the proposed pilot fits the temporary staffing allowance, if that is supported by the actual plan. A simple rota can then show the coverage. The coordinator explains the assumption and the exception aloud; necessary qualifications remain visible where a misleading impression would otherwise result. Do not hide a crucial cost condition in notes that the committee never sees.

Lay out the slide headlines in order and read them as a continuous argument. Then sketch a visual for each before searching for polished assets. Some points need a diagram, a small comparison or a clearly labeled number. Others may be better explained without an illustration. Decorative stock photography can fill space without carrying any of the reasoning.

Finally rehearse the transitions. What must the audience understand from the current slide to make sense of the next? If a spoken bridge repairs a gap that the storyboard itself hides, revise the sequence. Prepare a separate readable record when the deck will circulate without you. The live audience and the absent reader have different access to narration, so the same file may need additional explanation to serve both responsibly.