After answering a question, in the midst of a demo, most presenters simply turn back to their flow and pick up where they left off. This makes sense to the presenter (who knows the demo and the product), but it is very likely that the audience has lost track…
Instead, after answering a question, do a quick recap of the steps you’d just completed (before the question) to re-set and re-engage your audience. Works wonderfully!
Tips, thoughts, tools, techniques and practices to increase success rates with software demonstrations
Sunday, January 31, 2010
Tuesday, January 26, 2010
We Are Programmed To Forget - And Its Impact on Our Demos
Indeed we are – and consider the impact this has on traditional software demos!
Imagine you are driving home from work or on an errand… What do you remember about the cars and signs you see, the road-side debris, people, buildings and the roads you pass? How much of that information is retained?
Very little is actually remembered about what you saw along your way. Our brains are continuously evaluating what we see and hear as we move through our day – and continuously discarding anything that is not considered important, threatening, or particularly interesting.
What don’t we remember? Everything that is typical, expected, or normal.
What do we remember? Remarkable events, problems, danger and close calls, humor (things that made us laugh), anger (things that made us mad) and other emotional experiences (things that caused a strong emotional reaction).
What’s Forgotten?
How does this impact our demos and what audiences remember? In an hour-long traditional demo, we shouldn’t expect our audiences to remember very much:
- They won’t remember long sequences of features, functions and options…
- They won’t remember complex workflows, loops and multiple “if” cases…
- They won’t remember the confusing interdependencies of configuration choices, multiple roles, and intertwined pathways…
What’s Remembered?
What will audiences recall from traditional demos? The beginning, the end, and the ugly:
- They will remember the first and last few things that are shown…
- They will remember the bugs, crashes, ignored or poorly handled questions, the amusing distractions from other audience members, and particularly stunning fumbling for features.
- And they will remember an overall impression of the demo – as being boring, confusing, and complicated.
They may also remember the absence of capabilities they were looking for – in many cases, even if these capabilities were, in fact, presented!
What can we do to improve our success rates?
Memory Management
Here are three simple (yet very effective!) tactics to help your customers retain the key ideas you want them to remember:
[Shall we all say it together? “Do the Last Thing First!”] When presented with a long list of ideas, people remember the first few items very well and the last few items moderately well – and the material in between generally gets lost. This is the “Attention-Retention” principle (also known as the Serial Positioning Effect).
Take advantage of this and start your demos with the most compelling, most interesting deliverables for each audience. If the audience remembers nothing else, they will remember the most important part of your demo – the payoff, the visual evidence of the solution to their problem.
Along similar lines, people absorb and retain information best when it is presented in discrete “chunks”, as opposed to a long linear flow. Organize and present your demos accordingly – in consumable components – and use a roadmap to help manage the delivery of your component chunks.
Summarize…! Adults learn by repetition – so when you complete a demo segment, summarize. Repeat, verbally, what you just showed them. If you are face-to-face, you should see your audience nodding their heads – this means they have heard you, they understand, and they have a higher likelihood of remembering.
How can you tell if your audience will remember the key points? You’ll see them making notes – writing things down.
We combat our “programming-to-forget” by making notes of the major ideas, issues and questions we want to remember. For software demos, if you are doing well, you’ll see your audience making notes about key capabilities and writing comments about what they find particularly interesting.
I Really Remember…
What else can we do to help audiences remember our demos? Anything that is perceived as remarkable is memorable – for example:
- A unique presentation of a solution to a problem – “Wow! – They showed us the key reports that we need to produce right up front, at the beginning of their demo. And they showed generating those reports in 3 mouse clicks, as opposed to what is taking us a week to do today…!”
- Engage the audience – “That was so cool – they had John drive a portion of their demo, and John still types in all caps…!”
- Develop concepts or materials ad hoc – “It was great when they built a new form for us, first on a whiteboard and then right in their software…!”
- Make it a two-way conversation – “We were really engaged – asking questions and even coming up with new ideas for our process…”
- Finish the demo early – “Wow – they finished early and I had time to get some real work done…!”
- Be humorous, but effective – “It was funny when the sales guy said, ‘The bad news is I have a 60 slide corporate overview presentation to show – the good news is that I’m not going to inflict it on you…!’”
- Use props – “Do you remember when their technical guy came into the room with this huge stack of documents and folders spilling all over the place? Looked like our day-to-day lives, to me…!”
- Run their examples – “That was really nice – we rarely take something of value away from a demo…”
Humans are, by nature, programmed to forget. Causatively forgetting the unimportant, the uninteresting and the unremarkable is how our brains are able to handle the enormous volume of information we encounter every day.
Make your demos memorable by Doing the Last Thing First, organizing your delivery in consumable components, and by summarizing – as basics. Make your demos truly unforgettable by doing the unexpected, the noteworthy, and the remarkable.
Imagine you are driving home from work or on an errand… What do you remember about the cars and signs you see, the road-side debris, people, buildings and the roads you pass? How much of that information is retained?
Very little is actually remembered about what you saw along your way. Our brains are continuously evaluating what we see and hear as we move through our day – and continuously discarding anything that is not considered important, threatening, or particularly interesting.
What don’t we remember? Everything that is typical, expected, or normal.
What do we remember? Remarkable events, problems, danger and close calls, humor (things that made us laugh), anger (things that made us mad) and other emotional experiences (things that caused a strong emotional reaction).
What’s Forgotten?
How does this impact our demos and what audiences remember? In an hour-long traditional demo, we shouldn’t expect our audiences to remember very much:
- They won’t remember long sequences of features, functions and options…
- They won’t remember complex workflows, loops and multiple “if” cases…
- They won’t remember the confusing interdependencies of configuration choices, multiple roles, and intertwined pathways…
What’s Remembered?
What will audiences recall from traditional demos? The beginning, the end, and the ugly:
- They will remember the first and last few things that are shown…
- They will remember the bugs, crashes, ignored or poorly handled questions, the amusing distractions from other audience members, and particularly stunning fumbling for features.
- And they will remember an overall impression of the demo – as being boring, confusing, and complicated.
They may also remember the absence of capabilities they were looking for – in many cases, even if these capabilities were, in fact, presented!
What can we do to improve our success rates?
Memory Management
Here are three simple (yet very effective!) tactics to help your customers retain the key ideas you want them to remember:
[Shall we all say it together? “Do the Last Thing First!”] When presented with a long list of ideas, people remember the first few items very well and the last few items moderately well – and the material in between generally gets lost. This is the “Attention-Retention” principle (also known as the Serial Positioning Effect).
Take advantage of this and start your demos with the most compelling, most interesting deliverables for each audience. If the audience remembers nothing else, they will remember the most important part of your demo – the payoff, the visual evidence of the solution to their problem.
Along similar lines, people absorb and retain information best when it is presented in discrete “chunks”, as opposed to a long linear flow. Organize and present your demos accordingly – in consumable components – and use a roadmap to help manage the delivery of your component chunks.
Summarize…! Adults learn by repetition – so when you complete a demo segment, summarize. Repeat, verbally, what you just showed them. If you are face-to-face, you should see your audience nodding their heads – this means they have heard you, they understand, and they have a higher likelihood of remembering.
How can you tell if your audience will remember the key points? You’ll see them making notes – writing things down.
We combat our “programming-to-forget” by making notes of the major ideas, issues and questions we want to remember. For software demos, if you are doing well, you’ll see your audience making notes about key capabilities and writing comments about what they find particularly interesting.
I Really Remember…
What else can we do to help audiences remember our demos? Anything that is perceived as remarkable is memorable – for example:
- A unique presentation of a solution to a problem – “Wow! – They showed us the key reports that we need to produce right up front, at the beginning of their demo. And they showed generating those reports in 3 mouse clicks, as opposed to what is taking us a week to do today…!”
- Engage the audience – “That was so cool – they had John drive a portion of their demo, and John still types in all caps…!”
- Develop concepts or materials ad hoc – “It was great when they built a new form for us, first on a whiteboard and then right in their software…!”
- Make it a two-way conversation – “We were really engaged – asking questions and even coming up with new ideas for our process…”
- Finish the demo early – “Wow – they finished early and I had time to get some real work done…!”
- Be humorous, but effective – “It was funny when the sales guy said, ‘The bad news is I have a 60 slide corporate overview presentation to show – the good news is that I’m not going to inflict it on you…!’”
- Use props – “Do you remember when their technical guy came into the room with this huge stack of documents and folders spilling all over the place? Looked like our day-to-day lives, to me…!”
- Run their examples – “That was really nice – we rarely take something of value away from a demo…”
Humans are, by nature, programmed to forget. Causatively forgetting the unimportant, the uninteresting and the unremarkable is how our brains are able to handle the enormous volume of information we encounter every day.
Make your demos memorable by Doing the Last Thing First, organizing your delivery in consumable components, and by summarizing – as basics. Make your demos truly unforgettable by doing the unexpected, the noteworthy, and the remarkable.
Thursday, January 21, 2010
Presales On-boarding Training Novel Concept
Here’s a terrific idea for training new presales staff: Teach them your discovery/qualification process before teaching how to demo your software… Why consider this approach?
- It models the principle of doing discovery/qualification before presenting your solutions.
- It teaches new hires how to put together summaries of customer-specific situations (“Situation Slides”).
- It breaks the tradition of “Here’s our standard demo script… Learn it!”
This method also helps put your software in context:
- What specific customer problems does it solve?
- What specific capabilities are needed to solve these problems?
- What customer job titles are involved, and in what specific way?
If anyone (else) is already doing this, please let me know how it has been working for you…
- It models the principle of doing discovery/qualification before presenting your solutions.
- It teaches new hires how to put together summaries of customer-specific situations (“Situation Slides”).
- It breaks the tradition of “Here’s our standard demo script… Learn it!”
This method also helps put your software in context:
- What specific customer problems does it solve?
- What specific capabilities are needed to solve these problems?
- What customer job titles are involved, and in what specific way?
If anyone (else) is already doing this, please let me know how it has been working for you…
Wednesday, January 13, 2010
“Controlled Vocabulary”
Years ago, a colleague introduced me to the concept of “Controlled” vs. “Uncontrolled Vocabulary”. Watching a series of demos recently reminded me of the importance of this concept. Very simply, with Controlled Vocabulary, everyone in the meeting has a mutual understanding of all words and phrases used in a presentation or demo. Uncontrolled Vocabulary are words and phrases that are introduced by the vendor that are NOT understood by the customer.
Uncontrolled Vocabulary includes (but is not limited to!) words and phrases such as:
- Company-specific acronyms
- Company-specific terms
- Product feature names
Don’t use these in demos and presentations if you want to be most effective in your communications!
Uncontrolled Vocabulary includes (but is not limited to!) words and phrases such as:
- Company-specific acronyms
- Company-specific terms
- Product feature names
Don’t use these in demos and presentations if you want to be most effective in your communications!
Friday, January 8, 2010
Warning – Shameless Self-Promotion Alert! Great Demo! Open Workshop
We are holding an open 1-Day Great Demo! Workshop March 17, 2010 in San Jose, California. The event is co-sponsored by SKMurphy (www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice. Contact me for an overview, agenda and pricing information at PCohan@SecondDerivative.com.
Wednesday, January 6, 2010
Remote Demos – Don't Forget to Disconnect!
While this is certainly obvious, I’m occasionally amused – and sometimes astonished – by vendors who forget to close their Remote Demo meetings (e.g., via WebEx, GoToMeeting, Adobe Connect, etc.) and corresponding phone connections.
Amused – when a vendor forgets to close the session(s) and the collaboration tool window remains open/active.
Astonished – when a vendor forgets and, still sharing his desktop, starts to write email messages about the results of the web meeting! As a customer, it can be very interesting to see how the sales rep describes what a “great” meeting it was and how the “business is in the bag…!” I’ve heard the same with conference calls that remain open and active after the meeting has completed.
Amused – when a vendor forgets to close the session(s) and the collaboration tool window remains open/active.
Astonished – when a vendor forgets and, still sharing his desktop, starts to write email messages about the results of the web meeting! As a customer, it can be very interesting to see how the sales rep describes what a “great” meeting it was and how the “business is in the bag…!” I’ve heard the same with conference calls that remain open and active after the meeting has completed.
Monday, January 4, 2010
Understanding Before Proposing Solutions
We all know that we need to gain a sufficient understanding of our customers’ needs and specific situations before proposing solutions – and before presenting most demos. Here’s an additional reason to do this:
Miller Heiman, Inc. reports in their Executive Summary of their 2009 Sales Best Practice Study that 93% of “World Class” vendors vs. 50% of “All” vendors do “Clearly understand our customers’ issues before we propose a solution”. “World Class” organizations achieved stronger results in five areas measured:
- Average account billing
- Sales force quota attainment
- Number of qualified opportunities/leads
- Customer retention
- Forecast accuracy
Not surprising…!
Miller Heiman, Inc. reports in their Executive Summary of their 2009 Sales Best Practice Study that 93% of “World Class” vendors vs. 50% of “All” vendors do “Clearly understand our customers’ issues before we propose a solution”. “World Class” organizations achieved stronger results in five areas measured:
- Average account billing
- Sales force quota attainment
- Number of qualified opportunities/leads
- Customer retention
- Forecast accuracy
Not surprising…!
Subscribe to:
Posts (Atom)