Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 6, Issue 26;   June 28, 2006: Presenting to Persuade

Presenting to Persuade

by

Successful, persuasive presentations involve a whole lot more than PowerPoint skills. What does it take to present persuasively, with power?

The video ended, Ginny clicked the window closed, and swiveled her chair to face Sid and Mort. Sid was staring at the screen, in awe of what he'd just seen — a master at work. Mort was gazing out the window, in thought.

Presenting to persuade"Now that presentation worked," Ginny said, "and it wasn't much different from ours."

Sid was puzzled. "Let's watch it again," he said. "I can't figure this out."

Mort returned from wherever he'd been. "I remember a presentation training from awhile back," he said. "This guy we just watched was following the same pattern they taught us. You remember, Ginny, you were there, I think."

"Right…a four-step framework, wasn't it?"

Between the two of them, Mort and Ginny reconstructed the four-step framework for presenting to persuade. Here it is:

Start with their pain
Begin by connecting the audience with the parts of their pain that you can address. This motivates them. It gives you credibility, because it proves that you've been there, too.
For example, if you're talking to a group about designing presentations, you could remind them how hard it is to achieve connection and credibility, especially when the audience doesn't really know you. You're showing them that you share their pain, and you're reminding them of the problem, too.
Feature your features
Too much emphasis
on features per se
is a common mistake
Once you've identified their pain, talk about the features of your solution, describing how those features address their pain. For extra punch, show how other solutions that lack those features might not address the pain as effectively. In other words, show how the features of your solution are both necessary and sufficient.
Feature your features, but take care to connect each one to the pain. Too much emphasis on features per se is such a common mistake that it has a name: feature-mongering.
Brag about benefits
Bragging can be hard for some of us, but people do tend to discount whatever presenters say. If you don't emphasize strengths (pre-discount) then after the discount, most of the audience will have an inaccurate picture of the value of the solution.
The benefits of the solution are direct benefits from the audience's point of view — not yours. Lower maintenance cost for future versions is not a direct benefit, but faster introduction of new capability and faster repair of design problems are direct benefits.
To find the underlying benefit of any feature, repeatedly ask yourself "So What?" When the answer to this series of questions stops changing, that answer is the end-user benefit. See "Deliver the Headline First," Point Lookout for May 3, 2006, for more.
Provide proof
Finally, give some proof that the benefits are attainable with your solution. Proof can be a demonstration, a survey, a prototype, measurements, customer endorsements, endorsements of authorities, whatever you think will work.

You'll attend many presentations over the next few months. Notice which ones have real impact, and notice which ones follow this framework. Does it work? Go to top Top  Next issue: Are You a Fender?  Next Issue

Terrific Technical Presentations!Are your presentations — technical or otherwise — all they could be? Audiences at technical presentations, more than most, are at risk of death by dullness. Spare your audiences! Captivate them. Learn how to create and deliver technical presentations with elegance, power and impact. Read Terrific Technical Presentations, a stand-alone Web site filled with tips and techniques for creating powerful performances. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Effective Communication at Work:

What not to eat on the phone: Peanut butterVirtual Communications: III
Participating in or managing a virtual team presents special communications challenges. Here's Part III of some guidelines for communicating with members of virtual teams.
The robotic explorer OpportunityDefinitions of Insanity
When leaders try to motivate organizational change, they often resort to clever sloganeering. One of the most commonly used slogans is a definition of insanity. Unfortunately, that definition doesn't pass the sanity test.
Humans aren't the only species that communicates by facial expressionsDismissive Gestures: II
In the modern organization, since direct verbal insults are considered "over the line," we've developed a variety of alternatives, including a class I call "dismissive gestures." They hurt personally, and they harm the effectiveness of the organization. Here's Part II of a little catalog of dismissive gestures.
The musical energy behind "Shall We Dance" (1937)What We Don't Know About Each Other
We know a lot about our co-workers, but we don't know everything. And since we don't know what we don't know, we sometimes forget that we don't know it. And then the trouble begins.
The first page of Thomas Paine's pamphlet Common SensePublish an Internal Newsletter
If you're responsible for an organizational effort with many stakeholders, communicating with them is important to success. Publishing an internal newsletter is a great way to keep them informed.

See also Effective Communication at Work and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

The Eisenhower Matrix of Urgency by ImportanceComing January 29: A Framework for Safe Storming
The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
People in a conference roomAnd on February 5: On Shaking Things Up
Newcomers to work groups have three tasks: to meet and get to know incumbent group members; to gain their trust; and to learn about the group's task and how to contribute to accomplishing it. General skills are necessary, but specifics are most important. Available here and by RSS on February 5.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.