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.

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:

When Naming Hurts

One of our great strengths as Humans is our ability to name things. Naming empowers us by helping us think about and communicate complex ideas. But naming has a dark side, too. We use naming to oversimplify, to denigrate, to disempower, and even to dehumanize. When we abuse this tool, we hurt our companies, our colleagues, and ourselves.

Encourage Truth Telling

Getting to the truth can be a difficult task for managers. People sometimes withhold, spin, or slant reports, especially when the implications are uncomfortable or threatening. A culture that supports truth telling can be an organization's most valuable asset.

Decision-Making and the Straw Man

In project work, we often make decisions with incomplete information. Sometimes we narrow the options to a few, examine their strengths and risks, and make a choice. In our deliberations, some advocates use a technique called the Straw Man fallacy. It threatens the soundness of the decision, and its use is very common.

When You Aren't Supposed to Say: I

Most of us have information that's "company confidential," or possibly even more sensitive than that. When we encounter individuals who try to extract that information, we're better able to protect it if we know their techniques.

Virtual Meetings: Indicators of Inattention

If you've ever led a virtual meeting, you're probably familiar with the feeling that some attendees are doing something else. Here are some indicators of inattention.

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

Forthcoming issues of Point Lookout

Coming September 26: Congruent Decision-Making: I

Decision-makers who rely on incomplete or biased information are more likely to make faulty decisions. Congruent decision-making can limit the incidence of bad decisions. Available here and by RSS on September 26.

And on October 3: Congruent Decision-Making: II

Decision-makers who rely on incomplete or biased information are more likely to make decisions that don't fit the reality of their organizations. Here's Part II of a framework for making decisions that fit. Available here and by RSS on October 3.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenMNSCsqPBaEabypXpner@ChacwMyhbRzRFOUNrXzzoCanyon.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, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

10 Non-Technical Phenomena That Lead to Technical Debt

When organizations set about gaining control of their accumulated and newly incurring technical debt, a common error of thinking is that the problem can be addressed by modifying their technical processes alone. That can be effective in cases in which the causes of technical debt are found only in the engineering and IT organizations. But those cases are rare. This program surveys ten examples of organizational phenomena that lead to technical debt and which are not restricted to the engineering or IT organizations. Indeed, many of these phenomena cannot be found in the engineering or IT organizations, or if found there, they have relatively small effects on technical debt. For each of the ten phenomena, we describe how it leads to technical debt formation or persistence, and what can be done to mitigate its effects. Most important, we explain how effective control of technical debt requires contributions from a broad array of organizational roles. Read more about this program. Here's a date for this program:

• Wherever you are: it's a teleseminar: September 20, Teleseminar, Computer Aid, Inc. (CAI). Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.