As the visitors filed out of the room, Glenn caught Cynthia's eye. Yep, she was just as disturbed as he was. "Buy you a cup a coffee?" he asked. She nodded, without energy, and looked down. Everyone else started to leave, so Glenn and Cynthia walked wordlessly together to San Jose, the coffee bar on Three West.
They poured two talls and sat down in a booth out of the way around the corner. She opened with "Well, that was a disaster. Why don't we cut out the middleman and just shoot each other in the feet?"
Glenn smiled. It would be funny, if it weren't true. They had just given a demo to top management of what everyone hoped would become their biggest customer, and things hadn't gone well. "What could we have done differently?" Glenn asked.
So over those two cups of coffee, and two more, they made up a list of tips for giving small demos, to avoid a disaster next time.
You could make a tip list, too. Here are some to get you started.Small demos should be
- Avoid swarming
- If the size of your team is about the same as the size of the audience, they can feel overwhelmed, and they're unable to take in your carefully crafted message. In effect, you undermine your own effort. Find a way to limit the number of people in your organization who can attend, without offending anyone or making people feel excluded.
- Don't surround the audience
- Everyone on your team should sit or stand in a single arc that covers no more than a third of the circle around the audience. Surrounding creates a sense of danger — subliminal, but real.
- Have at most two designated speakers
- Let the conversation happen between the audience and the presenter. Occasionally, one other member of the presenter team might have something to add, or might answer a question. But if more than two people from the presenter team speak — not simultaneously of course — the message tends to cloud and you confuse the audience.
- Designate one speaker as primary
- When there are two speakers, contention and confusion is possible. To limit this, define roles. Let one person wear the "business" or "program" hat (B), and the other the "technical" hat (T). B should be primary, and T should defer to B.
- Let each other speak
- B should never interrupt T, and T should never interrupt B. Work out a gesture signal to indicate "stop talking" but don't interrupt each other.
- Support each other
- No matter what your partner says, let it stand. Chances are the audience will never remember it anyway. If you must comment, find a way to make your comment a supportive addition rather than a correction.
These tips are excerpted from Terrific! Technical Presentations, my new ebook, which is filled with tips for people who give technical presentations large and small.
- John Brtis
- Reminds me of an old joke…
- An old cow farmer goes to Sunday service and when it's time to start the preacher enters and sees that the cow farmer is the only person present. Rather flustered about what to do with only one other person in the church the preacher asks the farmer, "How do you think we should handle this?" The farmer drawls back, "Well…all I know is cows, but I know that if I go out to bring hay to the herd and I only find one cow, I still feed that cow." With a now clear understanding of what he needed to do, the preacher launched into a full service, including half a dozen songs, and a particularly well crafted thirty-minute sermon. At the end of this extravaganza, the preacher was saying his goodbyes to the farmer and asked him how he liked it. "Well," said the farmer, "all I know is cows, but if I go out to feed the herd and find only one cow, I don't dump the entire truck load of hay on her."
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? rbrenvrGnyGNUjOvKbkspner@ChacFZdMKrAjmGAWtoqcoCanyon.comSend me your comments by email, or by Web form.
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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- My Right Foot
- There's nothing like an injury or illness to teach you some life lessons. Here are some things I learned
recently when I temporarily lost some of my independence.
- Healthy Practices
- Some organizational cultures are healthy; some aren't. How can you tell whether your organizational
culture is healthy? Here are some indicators.
- Hill Climbing and Its Limitations
- Finding a better solution by making small adjustments to your current solution is usually a good idea.
The key word is "usually."
- The Power and Hazards of Anecdotes: II
- Anecdotes are powerful tools of persuasion, but with that power comes a risk that we might become persuaded
of false positions. Here is Part II of a set of examples illustrating some hazards of anecdotes.
- Ethical Debate at Work: II
- Outcomes of debates at work sometimes favor one party, not only at the expense of the other or others,
but also at the expense of the organization. Here's Part II of a set of guidelines for steering debates
toward wise outcomes.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming December 20: Conceptual Mondegreens
- When we disagree about abstractions, such as a problem solution, or a competitor's strategy, the cause can often be misunderstanding the abstraction. That misunderstanding can be a conceptual mondegreen. Available here and by RSS on December 20.
- And on December 27: On Assigning Responsibility for Creating Trouble
- When we assign responsibility for troubles that bedevil us, we often make mistakes. We can be misled by language, stereotypes, and the assumptions we make about others. Available here and by RSS on December 27.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbreniKZAgrihBdJWhABaner@ChacIjPmnADAYftzqFWLoCanyon.com or (617) 491-6289, 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
- Person-to-Person Communications: Models and Applications
- When we talk, listen, send or read emails,
read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person.
And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling
hurt, and being confused. There are so many ways for things to go wrong that we could never learn how
to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes
their occurrence. In this very interactive program we'll explain — and show you how to use —
a model of inter-personal communications that can help you stay out of the ditch. We'll place particular
emphasis on a very tricky situation — expressing your personal power. In those moments of intense
involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive.
Read more about this program. Here's a date for this
- Embassy Suites by Hilton Jacksonville Baymeadows, 9300 Baymeadows
Road, Jacksonville, Florida, 32256, USA: January 15, 2018,
Monthly Meeting, Northeast Florida Chapter of the Project Management Institute. Register now.
- Embassy Suites by Hilton Jacksonville Baymeadows, 9300 Baymeadows Road, Jacksonville, Florida, 32256, USA: January 15, 2018, Monthly Meeting, Northeast Florida Chapter of the Project Management Institute. Register now.
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- 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.