Presentation as Persuasion

The dominant failure mode of business presentations is category confusion: presenters think their job is to transfer data, but their actual job is to move their audience from one mental or behavioral position to another. Jerry Weissman’s Presenting to Win and Garr Reynolds’ Presentation Zen address this failure from different angles — Weissman from the architecture of persuasion, Reynolds from the design of visual communication — and together constitute a comprehensive framework for presentation as a specifically persuasive act.

Weissman: The Point A to Point B Framework

Weissman’s organizing principle is deceptively simple:

“Every communication has as its goal to take the audience from where they are at the start of your presentation, which is Point A, and move them to your objective, which is Point B.”

Point A is the audience’s current state: their existing beliefs, assumptions, level of understanding, and emotional orientation toward the subject. Point B is where the presenter needs them to be: persuaded, decided, enrolled, ready to act.

The framework is important because it forces the presenter to answer three questions before designing the presentation:

  1. Where is the audience now? (Point A diagnosis)
  2. Where do I need them to be? (Point B definition)
  3. What is the most direct route between the two?

These questions are often skipped. Presenters who are primarily subject-matter experts tend to design presentations around their knowledge rather than around the audience’s journey. The result is a presentation that exhaustively covers the subject from the expert’s perspective and fails to move the audience because it was never designed to.

“The only sure way to create a successful presentation is to begin with the goal in mind.”

Weissman invokes Aristotle’s concept of teleology — defining matters by their end or purpose — as the philosophical foundation. A presentation defined by its goal (Point B) will be structured entirely differently from a presentation defined by its content (the expert’s knowledge). The former includes only what moves the audience from A to B; the latter includes everything the expert knows about the subject.

The Three-Stage Journey

“To reach Point B, you need to move the uninformed audience to understand, the dubious audience to believe, and the resistant audience to act in a particular way. In fact, understand, believe, and act are not three separate goals, but three stages in reaching a single, cumulative, ultimate goal.”

The three stages map the full persuasion arc. Understanding alone is insufficient — an audience that understands the evidence but doesn’t believe it won’t act. Belief alone is insufficient — an audience that believes the claim but doesn’t act has been persuaded of nothing useful. The full journey requires all three, in sequence.

The WIIFY: The Foundation of Audience Advocacy

Weissman’s most operationally important concept is WIIFY — “What’s In It For You” (the audience). He treats WIIFY not as a rhetorical technique but as the ethical core of effective presenting:

“A Feature is a fact or quality about you or your company, the products you sell, or the idea you’re advocating. By contrast, a Benefit is how that fact or quality will help your audience.”

“Features are of interest only to the persuader; Benefits are of interest to the audience. Go with Benefits every time.”

The feature/benefit distinction exposes why most business presentations fail to persuade: they are feature-intensive and benefit-sparse. The presenter talks about what they have (the product’s specifications, the plan’s components, the team’s credentials) rather than what the audience gets (the problem solved, the outcome enabled, the risk removed).

“For people to act on anything, they must have a reason to act, and the reason must be theirs, not yours.”

Audience Advocacy is the commitment to designing every element of the presentation around the audience’s interests and perspective:

“Audience Advocacy: convincing your audience that what you want will serve their interests, too.”

The practical test: can the presenter answer, for every major point in the presentation, “Why does this matter to the audience in front of me, right now?”

The Presenter as Storyteller, Not Slide-Reader

Both Weissman and Reynolds insist on the primacy of the presenter over the visual aids:

Weissman:

“You are the storyteller, not your slides.”

“The overwhelming majority of business presentations merely serve to convey data, not to persuade.”

“The slides or other graphics are there to support the presenter, not the other way around.”

Reynolds (the sole highlight from Presentation Zen):

“Your own presentations, look for contrasts such as before/after, past/future, now/then, problem/solution, strife/peace, growth/decline, pessimism/optimism, and so on. Highlighting contrasts is a natural way to bring the audience into your story and make your message more memorable.”

The slide-as-document failure mode is endemic. When slides contain all the information — dense text, detailed tables, comprehensive coverage — they replace the presenter rather than supporting them. The audience reads the slides instead of listening to the presenter, and the presenter becomes a voice-over narrator of their own visual aids.

Weissman on the consequences:

“When your story is not clear, when it’s fragmented or overly complex, the audience has to work hard to make sense of it. Eventually, this hard work begins to produce first resistance, then irritation, and then loss of confidence.”

The design implication is specific: slides should contain headlines, not body text. The body text is spoken by the presenter:

“The optimal presentation is composed of a presenter providing spoken body text for headline-style bullets on the slides.”

“When designing graphics, I rely on the wisdom of Less Is More, and its corollary, When in doubt, leave it out.”

Structural Clarity: Roman Columns and Flow

Weissman’s structural model uses the metaphor of Roman columns — the main supporting pillars of the argument:

“What are your Roman Columns? Why have you put the Roman Columns in a particular order? In other words, which Flow Structure have you chosen?”

The Roman Columns are the three to five central claims that support the presentation’s Point B. Everything else in the presentation is supporting material for one of the columns. This structure prevents the sprawl that undermines most business presentations: too many equally-weighted points that the audience cannot organize or remember.

The choice of Flow Structure determines how the Roman Columns are sequenced:

  • Chronological: events in order, suited for change narratives
  • Problem/Solution: issue then resolution (with the warning not to dwell too long on the problem)
  • Form/Function: central concept with multiple applications radiating from it

“Choosing one or two Flow Structures for the entire presentation” provides the consistency of structure that allows the audience to follow.

Weissman’s test for structural clarity:

“The ultimate technique for checking your flow is to read only the titles of your slides. If you can trace the logic of your entire presentation by reading these few words, bypassing the bullets, graphs, or other content, you’ve created clarity.”

The Opening: 90 Seconds to Capture the Audience

“But if you capture your audience’s attention, define your Point B, and establish your credibility in those same 90 seconds, the audience is yours, and they will follow you wherever you want them to go.”

Weissman’s Opening Gambit framework — the first 90 seconds — is the presentation equivalent of Zinsser’s and McPhee’s lead. It must:

  1. Capture immediate attention (the hook)
  2. Establish the presenter’s credibility and relevance
  3. State or imply the Point B — where this presentation is going and why it matters to this audience

Weissman identifies several Opening Gambit techniques: the rhetorical question, the surprising statistic, the relevant anecdote, the bold claim. All must fulfill the same function: create in the audience a desire to know what comes next, specifically because what comes next is relevant to them.

Verbalization: The Practice Imperative

One of Weissman’s most operationally specific recommendations:

“The only way to prepare a Power Presentation is to speak it aloud, just as you will on the day of your actual presentation.”

“Verbalization means turning your outline into a full-fledged presentation by practicing it beforehand. Speak the actual words you will use in your presentation aloud, accompanied by your slides.”

The reasoning parallels Zinsser’s prescription to read writing aloud: the ear catches problems the eye misses. A sentence that looks fine on paper may be impossible to say clearly; a transition that seems logical in text may produce confusion when spoken; a slide that appeared informative in design may overload the audience when encountered in real time.

Verbalization also produces command over the material:

“When you feel in command of your material, you communicate a sense of confidence to your audience and heighten the power of your presentation.”

“A well-prepared story enhances a presenter’s delivery skills.”

The inverse is also true: a presenter who has not verbalized their presentation will be processing the presentation and managing their anxiety simultaneously, which reduces the cognitive resources available for actually connecting with the audience.

Customization vs. Polish

Weissman warns against the “windup doll” speech — a perfectly polished presentation delivered without connection to the specific audience in the room. The solution is External Linkages: references to things specific to the audience, the day, the context that make the presentation feel freshly made rather than pre-packaged. “Be in the moment. Concentrate on your audience during the presentation.” The well-rehearsed story is the foundation; the live connection is what makes it work.