Presenting to Persuade

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.

"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?  Top    Next Issue

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

About Point Lookout

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:

Shining Some Light on "Going Dark"

If you're a project manager, and a team member "goes dark" — disappears or refuses to report how things are going — project risks escalate dramatically. Getting current status becomes a top priority problem. What can you do?

Controlling Condescension

Condescension is one reason why healthy conflict becomes destructive. It's a conversational technique that many use without thinking, and others use with aggressive intention. Either way, it can hurt everyone involved.

Inbox Bloat Recovery

If you have more than ten days of messages in your inbox, you probably consider it to be bloated. If it's been bloated for a while, you probably want to clear it, but you've tried many times, and you can't. Here are some effective suggestions.

Social Transactions: We're Doing It My Way

We have choices about how we conduct social transactions — greetings, partings, opening doors, and so on. Some transactions require that we collaborate with others. In social transactions, how do we decide whose preferences rule?

Remote Hires: Communications

When knowledge-oriented organizations hire remote workers, success is limited by the communications facilities they provide. Remote hires need phones, computers, email, text, video, calendars, and more. Communications infrastructure drives productivity.

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

Forthcoming issues of Point Lookout

Coming December 11: White Water Rafting as a Metaphor for Group Development

Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.

And on December 18: Subgrouping and Conway's Law

When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

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