Thursday, August 12, 2010

Getting CBI’s Right

I note that Great Demo! Workshop participants often write Critical Business Issue (CBI) statements for their Situation Slides that are too low level or too detailed – and that we need to remind them to think in terms of a job title’s quarterly, annual or project-based objectives. What is initially written as the CBI turns out to be the Reason/Problem.

A simple solution is to go online to find example job descriptions for target job titles – this is a terrific way to ensure that CBI’s are at the right level.

I just did this earlier this morning, when I felt a bit uncomfortable about the CBI I had written for a Payroll Manager. It only took a few minutes and now I’m confident I have the right verbiage for a good Vision Generation demo Situation Slide.

Tuesday, August 10, 2010

Very Interesting Demo – What Did You Like; What Could Have Been Done Better?

A colleague forwarded me this link to a recent video-recorded demo – it is about 10 minutes in length – and has some wonderful examples of good practices and classic demo challenges:

http://www.avc.com/a_vc/2010/08/how-to-pitch-a-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+AVc+%28A+VC%29

[You might watch it first before reading my observations…]

Observations – What I Liked:

- Very engaging style and personable.
- Cool to see him writing code in front of the audience.
- Very cool to engage the audience (on both the “call the number” and “it is calling you…” segments).
- Clever set-up (“Turn your ringers on…”).
- Great interaction with audience.
- He is clearly enthusiastic and in love with his technology.

Observations – What Could Have Been Better:

- VERY interesting to hear audience question, “Why do you need it?”…! This is a fine demo for Early Adopters (most likely much of the audience in the video), but would be a failure for everyone else. In the demo portion, the presenter never explained what applications his app could be used for!
- Should have increased his session time-out time so that he didn’t have to log in again…
- Should have used a 518 number at first (rather than finding that there were no 212 or 646 numbers available…).
- Should have tested his AT&T connection and/or used another phone that did work.
- He noted that a pile of apps are available (~85) but didn’t cite what any of them do…

The moderator, at the end, asked for an example of a use-scenario for the application – and the presenter finally offered one brief example (voting by phone).

In summary, a wonderful demo for technical early adopters but, potentially, a failure for most others. Comments?

Wednesday, July 28, 2010

Methodology Workshop Trainees’ Three Typical Groups – Coaching Suggestions for Managers

Participants completing training workshops tend to cluster into three rather distinct groups (based on our experiences with Great Demo! Workshop and other workshop trainees):

- Group 1: Those who “get it” and put the ideas into practice right away

- Group 2: Those who understand the concepts and are interested, but need encouragement to try out the new methods

- Group 3: Those who don’t care and aren’t going to change (“no-how, no-way…”)

Group 1:

The first Group generally leave Workshops motivated, willing and able to put the ideas into practice right away – they may even seek opportunities to try out the new methods as soon as possible. They are typically confident enough in their own capabilities to move forward on their own.

Coaching members of this group is easy and a delight: support their efforts, highlight their successes (extremely important), and promptly respond to their questions as they encounter new situations or challenges. Enable this group to lead the way and establish credibility for the new method and ideas. Publishing their successes both within the team and beyond is a key tactic to achieve this. Managers who hold weekly team conference calls will often use these calls as opportunities to poll for success stories and to address questions.

Group 2:

Members of this Group often like the ideas and are interested in trying them out, but may lack sufficient confidence to try them out in front of customers. They need to be gently (but firmly!) pushed, pulled and encouraged. Success stories coming from their peers (initially from Group 1 members) is one of the strongest ways to help Group 2 people move forward. Proactively harvesting and publishing successes (both verbally and in various written formats) from others is a critical step in achieving substantive implementation, particularly for Group 2.

Group 2 people can also be encouraged to “pick one idea and try it” – as opposed to putting an set of methods into practice. Success with one idea often

Managers often also use quarterly or annual objectives to drive Group 2 member behavior. For example, in Great Demo! methodology, many managers establish quarterly objectives for presales team members to harvest one or more Informal Success Stories per quarter, and/or to publish one or more Situation Slides and accompanying Illustrations to their peer group on a quarterly basis. Both of these objectives drive the behaviors needed to achieve methodology implementation.

Group 3:

Sigh. In a typical normal distribution of people there will nearly always be a few percent who simply won’t change, in spite of encouragement – even in the face of specific quarterly objectives. Members of this Group may or may not understand the concepts from the training – they simply don’t/won’t change the way they operate. They will often articulate this as, “I’ve been selling/demoing/marketing for 20 years and nobody can tell me how to do it…!”

Coaches and managers of Group 3 people generally are left with two options… If the employee is consistently achieving the key objectives (e.g., achieving sales quota if he/she is in sales), then the employee may be allowed to simply continue to produce. If the employee is not generating the desired output, it may be time to help them find a new position…!

Sunday, July 25, 2010

Phone Numbers and Conference Call Code Numbers – Terrific Examples of Chunking/Consumable Components

Recently, I noticed that I often insert spaces in conference call entry codes – and suddenly realized why I do this..! For example, I received a calendar appointment for a conference call with the following information [numbers are scrambled to protect the innocent]:


Phone Number: 800 692-5505

Meeting ID: 8931271475

Just before calling in to join the session, I quickly edited the Meeting ID number by adding a few spaces:

Meeting ID: 893 127 1475

This edited version is, in my opinion, much easier to read and to enter on my phone. Why? Because the large, unwieldy number has been cut down into small, consumable components. Interestingly, phone companies already know this – and typically present phone numbers pre-formatted into similar small chunks. It’s another terrific example of other industries re-affirming Great Demo! concepts…!

Friday, June 25, 2010

Demo Methodology Implementation Tip

Many teams that have undergone Great Demo! training use their weekly team calls to help drive implementation – and report that this small tactic has yielded rich rewards. They use part of these calls to share success stories, discuss challenges, and review demo methodology components or tips that have worked particularly well.

In the case of Great Demo! Workshop participants, they often discuss Situation Slides that are proving to be reasonably homogeneous, they share Illustrations that have been particularly effective, and outline “Do It” and “Peel Back the Layers” pathways, in addition to discussing other tips and techniques.

From time-to-time, it can also be useful to have the trainer participate in these calls, as well, to help answer questions and address new challenges that team members have encountered (I do this on request, as part of my deliverables).

Thursday, June 17, 2010

Sales Effectiveness Priorities

The recent CSO Insights report on Sales Management Optimization includes a very interesting finding:

In the section, “Sales Effectiveness Priorities Going Forward”, the results showed that “Improve Ability to Show our Strategic Benefit/Value” was top of the list – 34% of respondents rated this as their number 1 item and 68% included it in their top 3.

I’ll pose a question: How much of achieving this is embodied in presenting demos?

(And I’ll answer it…) In Great Demo! methodology, the value associated with the customer making the change from the current state to the desired future (aka the Delta) is a key component that needs to be uncovered and clearly articulated as part of the demo.

This is an area where many sales, presales and marketing organizations could clearly do better!

In traditional sales presentations and demos, the sales team often verbalizes something like, “…and using our offering will save you time and money…!” Participants of Great Demo! Workshops learn to uncover specific, tangible ways of articulating value, enabling selling teams to present information that is more concrete: “…and using our offering will enable you to redeploy 3.5 FTE and reduce your inventory by $275K on an annual basis.”

Which statement has more impact?



[The full CSO Insights Sales Management Optimization report can be purchased at http://www.csoinsights.com/Publications/Shop/sales-management-optimization]

Wednesday, June 16, 2010

Should Presales People Do Detailed Statement-of-Work Documents?

Question:


“Our company does something I have never heard of: The SC [“Solution Consultant” – our presales title] does a deep and detailed Statement of Work (SOW) for each serous prospect. The prospect typically never sees anyone from Professional Services until after the sale. Our company likes this approach – SC’s are perceived, by customers, as very detail-oriented and technically strong people, so they are trusted. The downside is that SC’s often spend a full week working on the SOW alone - which is not scalable.

Our company is now working to double in revenue in the near term. I’m concerned that we can't survive like this when the deal flow picks up. Have you ever encountered SC’s doing this level of real SOW’s?”

Answer:

Yes, I've actually seen a number of companies do extensive SOW (or similar name) work prior to a sale for each customer. The companies that do this work tend to enjoy very high win rates vs. their competition and comparatively high customer satisfaction and retention rates. It is a great approach for dealing with offerings that require a fairly intense implementation process (system set-up, data migration, customization/configuration, etc.).

The downside(s) are exactly what you note: it is very resource intensive AND there is an enormous requirement for excellent documentation and communication of the SOW information within the vendor's team (e.g., presales to professional services and customer service). At one level, this is the essence of good CRM practices (as opposed to simply a sales forecast system).

It this process scalable? Not really - you need to have a sufficient complement of pre- and post-sales people to support the required/desired sales project bandwidth, so "scaling" often means adding people.

What can be done to improve the process? A few things, possibly:

- Some of the information currently collected in the SOW process may not be material - this could be cut out of the process. You may have to look at a broad range of implementations to determine what could be cut out, however.

- Boilerplate: Good boilerplate text and structure for SOW's can save a great deal of time and effort in documenting the information. It might even get to the level of pre-defined items with check-boxes or similar to help speed the process. Take a look at how doctors document their diagnosis information as an example...

Any other recommendations or suggestions?

Tuesday, June 1, 2010

Real-Time vs. Time-Slice

Nice positioning/distinction I heard recently: What’s the difference between a dashboard and a report? Dashboards offer “real-time” views; Reports offer a “time slice”.

Thursday, May 27, 2010

Great Quote

“It is easier to extract your own molars than to extract information from this system!”

(And imagine the visual image this suggests…!) A colleague offered this comment when talking about trying to find specific patents in the US PTO database – but you can simply fill in the blank with your product/system of choice…

Wednesday, May 26, 2010

How Do We Write vs. Read Journal Papers? And What Does This Have To Do With Demos?

[Note: Skip this post if you have never read a scientific, engineering, or other “refereed” journal article…)]

Consider: How do we write journal papers in comparison with how we consume what others write?

Scientists are typically taught a process to draft papers for scientific and other refereed journals. We review the existing research in an arena, focus on a specific problem area and explore the relevant history. After careful thought (hopefully!), we form a hypothesis. We then define an experiment to test our hypothesis, execute the experiment and, if the results are interesting, draft a paper to publish what we’ve learned.

We generally draft the paper following a step-by-step process:

1. Discuss the general problem, the previous work and existing thought.
2. Offer our hypothesis, with some level of support, and introduce our general plan to test our thinking.
3. We outline the experimental plan…
4. We discuss the specifics of the procedure, materials, and conditions.
5. We present the results, often in an initial “rough” set of data followed by “refined” results.
6. We offer a discussion of what we believe we are seeing in the results and…
7. Finally, we offer a conclusion – often followed by recommendations for follow-on experimentation.

Interestingly, the last thing we often draft, forced on us by the journal publishers, is the Abstract.

Now, consider how we read journal papers:

What do we do first? We read the Abstract! Why? To see if the paper is interesting to us. If it is, we often jump directly to the Conclusion section – to find out what was learned. If we are very interested, we then go back and read other parts of the paper…

Sadly, many of us with science or related backgrounds prepare and deliver technical, marketing and sales presentations following the same strategy that we follow to write papers: we develop a long, detailed story that puts the pay-off at the end – forcing the audience to wait 20 minutes, 40 minutes (or longer!) to find out if they are interested.

The key concept of Great Demo! methodology is to “Do the Last Thing First” – and, if the audience is interested, then peel back the layers in accord with the audience’s depth and level of interest. This maps very closely to the way we read (but not write) journal papers!

Wednesday, May 19, 2010

Demo Skills Assessment - Do It Now

Some people suggest that delivering a terrific demo is an art. While there may be components of creating and presenting demonstrations that are intangible, many other demo skills can be measured. Multiple measurements done over time provide an understanding of strengths and growth opportunities; and, of course, measurements done by yourself may offer differ from those done by others!
 
[If you already agree that demo skills assessment is a good thing, you might cast your eyes to the bottom of this post where I offer an assessment tool in Excel format for your use.]

I recommend performing an assessment of your current state of practice on a regular basis. A first assessment provides a baseline; subsequent reviews can offer insight into areas of strength or opportunities for improvement:

If you are an Individual Contributor:
  • To provide a qualitative/quantitative set of measurements of your own performance for goal-setting, personal growth and to seek coaching in areas where you can improve
  • In order to compare pre- vs. post-Workshop results, if you plan attend a Great Demo! Workshop
  • In order to compare pre- vs. post-event results, if you plan to attend other related skills training (presentation skills, sales skills, etc.)

 If you are a Team Leader:  
  • To provide a qualitative/quantitative set of measurements for managing performance, goal-setting and coaching of your team
  • In order to compare pre- vs. post-Workshop results, if you plan to provide your team with a Great Demo! Workshop
  • In order to compare pre- vs. post-event results, if you plan to provide your team with other related skills training (presentation skills, sales skills, etc.)
In some organizations, assessments are done on a regular basis (quarterly, for example) and are often tied to quarterly or annual goals and objectives. There are (at least) 5 assessment perspectives worth considering:
  • The individual’s view of his/her own performance
  • His/her manager’s perspective
  • Another member of the selling team’s viewpoint
  • A customer’s assessment (it is tough to get unvarnished opinions from customers, but terrific when you can!)
  • A relatively disinterested 3rd party deeply skilled in assessing demo skills performance across a broad range of demos types, sales situations, and delivery mechanisms (e.g., me).
You are welcome use my existing Demo Skills Assessment to help “kick-start” your own assessment process. It provides a range of skills and topics rated on a 10 point scale, on either an individual or team basis, in Excel format. Contact me at PCohan@SecondDerivative.com if you’d like to receive a copy. You are also welcome to edit the Assessment as desired for your own specific situation.

Tuesday, May 11, 2010

Memory Embedding – And Its Impact on Demos

What are a few of your oldest memories? Interestingly, many people describe swimming at the beach or swimming lessons when they were very young children as some of their oldest and yet most strongly retained memories. Why is this?


It has been suggested that the strength of long-term memory is at least partly due to the degree of “embedding” that is done by our brains. Embedding includes repetition of the memory and the number of senses that were involved in the original event, plus the emotional impact of the event. For a swimming experience as a young child, then, it isn’t surprising that the memory can be strong. Consider the senses involved for child at a swimming class in a pool:

  • Sound: The sounds of splashing water, other kids yelling, the instructor’s directions…
  • Sight: The vision of the pool and water, especially the distorted effect of what is seen under water…
  • Touch: The feel of the pool water, churning, bubbles…
  • Taste: The taste and texture of the pool water…
  • Smell: The smell of chlorine and sun-block lotion….
 
Add to that other emotional components that might also be in play: the sense of accomplishment of your first lap across the pool; the desire to show your mother/father how well you can do; the fear of sinking… The sum is quite a compelling range of input which may all serve to embed that memory strongly.

An early visit to the beach may yield even stronger memories and embedding:

  • Sound: Waves breaking on the beach, sea-gull calls, kids yelling…
  • Sight: The ocean above water, the murky green underwater, breaking waves and foam, sand, birds…
  • Touch: The cold water swirling up your legs, waist, shoulders; a wave breaking over you; foam around your legs; the hot sun overhead; the sand under your feet and the weird stuff you feel (shells, kelp…)…
  • Taste: Salt sea-water, the grit of sand in your mouth…
  • Smell: Sea-shore smells of ocean, decaying sea-weed and kelp, sun-block lotions…

Again, add to these senses the other emotional components: the accomplishment of your first forays into the surf; the fear of sinking, sharks, and other scary sea things…! It is not surprising that many people describe similar scenes as some of their strongest early memories.

What does the mean for software demos? It suggests that the more embedding that occurs during the demo, the more likely the audience will remember the demo. Most demos impact only two senses: sight and sound. The use of physical props and multiple pathways to embed ideas (stories, analogies, examples) – as well as emotional embedding (things that are perceived as fun, fearful, or fantastic) may help increase the strength of the retained memory of your demo.

Monday, May 10, 2010

Remote Demos: Turn Off Cell Phone (fer cryin’ out loud…!)

I’ve heard this happen 3 times in the past 2 weeks, so I guess it needs to be said: Remember to turn off your cell phone before beginning a Remote Demo…!

Thursday, April 29, 2010

Demo Expertise – and Demo “Experts”

I’m intrigued by the concept of an “expert” – particularly as it relates to creating and delivering software demos. How long does it take to become an “expert”? Does this take a year? 2 years? 5 years? Longer?


More importantly, is length of time the key factor? For example, the ability to learn a process and execute it through a range of conditions might connote expertise. It also might simply mean that a person has learned to execute a poor or mediocre process very well.

Another view might suggest that there are two processes going on: The first is the process of the demo pathway itself; the second is the ability to bring it to life – showmanship. One person could be an expert at the demo pathway, but poor at showmanship; another might be a terrifically engaging personality, while presenting a rather boring or misaligned demo pathway.

Those who have been delivering demos for years may actually suffer another challenge. Cognitive dissonance impacts our impressions of ourselves, with respect to our abilities. For example, many sales, presales and marketing people believe that they are demo experts since they have been preparing and presenting demos for many years. Other data may suggest, however, that their demos are not particularly strong – from data such as failure to achieve quota, repeat demos for the same audience, and losses to competitors or “no decision”.

Are you a demo expert? How can you tell?

Tuesday, April 27, 2010

“Demo Day” for Remote Demo Practice

In nearly every Great Demo! Workshop, participants ask for a session on best practices, tips and methods for delivering demos and presentations remotely, over the web, using tools such as GoToMeeting, WebEx, and Adobe Connect. While a few folks are skilled at using these tools, most of us simply start a remote session and present our demo and/or PowerPoint slides using very few of the available tools or techniques.




Given that people won’t try anything new in a live session with a real customer, here is a strategy to help yourself and your team become more effective at operating via the web: A Remote “Demo Day” session. Here’s the process I recommend:



1. Organize to have an internal expert present specific tips and operation of the web collaboration software you use, in a live, web delivery, so you can see the examples in action – and learn how they are done in your specific environment.



2. Next, have the team pair-up to explore and practice using the software’s specific tools and capabilities in one-on-one sessions. A 30 minute session is typically sufficient for each person to try out and practice using the tools (screen size/resolution, annotation tools, selective sharing, giving/taking control, whiteboard, private chat, etc.).



3. Finally, organize a 1 or 2-hour Remote Demo Day session where each team member presents a 6-8 minute demo or presentation to the balance of the group to practice and take feedback. Participants should be encouraged to use a range of tools in their demo/presentation.



These sessions can be done non-consecutively, but I would recommend completing them within a single week. At the end of this process, everyone should be comfortable and ready to use the tools in live remote meetings with prospects and customers.

Friday, April 16, 2010

Demo “Capital” – An Undervalued Resource?

Consider the sum of an organization's knowledge, know-how, tools, techniques, tips and success stories related to demonstrating one's offerings. As with other types of capital, how can this best be captured, developed, and leveraged? How is it valued (how should it be valued)?


Your use of Demo Capital should yield competitive advantages and opportunities, ranging from sales successes, to productivity and efficiency gains, to attracting and retaining high-value employees. A first step is to identify what you have…


What is Demo Capital?

Here are some tangible elements of Demo Capital, as a starting point:

- Demo databases
- Demo virtual machine images
- Demo scripts
- Meeting preparation sheets and forms
- Qualification, discovery and analysis forms and documents
- CRM system fields and forms
- Situation Slides
- Illustrations
- Proscribed “Do It” pathways
- Proscribed “Peel Back the Layers” pathways
- Documented answers to typical questions
- Formal Success Stories
- Documented Informal Success Stories
- Market-specific data, notes, and materials
- Competitive strengths/weaknesses pieces
- RFP response boilerplate (and “Row Adding” opportunities)
- Documented stories, props and similar tools proven successful for demonstrations

Intangible (undocumented) Demo Capital elements might include:

- Improvements and changes made to documented materials (but not documented)
- Best practices as evolved by the team
- Tips, tricks and techniques for face-to-face demos
- Tips, tricks and techniques for Remote Demos
- Particularly successful props, stories, and related presentation “nuggets”

Clearly, these lists are not exhaustive – a brief brainstorming exercise should yield longer and more specific lists unique to your own organization. The resulting list should also alert you to the potential value of the Demo Capital you have – and the gaps associated with capture and re-use.


What is the Value of Your Organization’s Demo Capital?

A simplistic answer is the corresponding direct cost to create and accumulate your Demo Capital. This is roughly the number of people involved multiplied by the time invested, multiplied by the average FTE rate for those people. A team of 10 people operating for 10 years with an average FTE rate of $150K yields a valuation of $15M. Is this a fair estimate? Perhaps…

Another approach examines the cost of not leveraging existing capital. This could equate to sales opportunities lost to competitors or “no decision” – often a dangerously large number!

It could be measured by the time-cost and opportunity-cost of doing repeat work:

- People recreating materials or tools (they could not find or were unaware of)
- Team members developing know-how (that already exists in the organization, but has not been communicated or captured)
- On-boarding processes, where individuals may take months or years to learn methods, find tools, and develop processes on their own (that could have been taught in days or weeks)

Or it could be calculated, in the negative case, by the cost of replacing a highly-valued employee who chose to move to another company. However calculated, the inevitable question is, “Are we getting the best results from our investment?” – or, more bluntly, “Are we getting sufficient results from our investment?”

I’ve heard heads of sales observe that it takes a full year to bring a new sales person up-to-speed to be able to achieve quota – and 2 years or longer for a new presales or marketing person to support the sales process satisfactorily. Is this too long and too expensive?


Yield From Investment

Here’s the payoff – and the challenge! There are a range of strategic and tactical questions that guide us on how to get the best yield from our existing investment in Demo Capital:

Tactically:

- What do we have? What’s missing? Where is it? How is it organized, accessed?
- How do we use it today? How could it be better used?
- Are there tools available to help? Are there best practices that we can apply?

Strategically:

- Can we shorten our sales cycles? Improve our sales processes? Increase revenue per opportunity?
- How can we increase efficiency and productivity in our sales, presales and marketing groups?
- Can we improve our ability to hire and retain top-performing staff? How do we develop existing staff further?


Assessing, capturing and leveraging Demo Capital can clearly be a means to address some of the critical business challenges faced by sales, pre-sales, and marketing leadership – and at mid-management and staff levels as well.

If you feel uncomfortable with this as the end of this piece, like something is missing, then I’ve succeeded! I drafted this to stimulate thinking and begin a conversation – looking forward to hearing your ideas, suggestions, and experiences.

Wednesday, April 14, 2010

Flip-Chart / Whiteboard Version of Situation Slide

In a recent Great Demo! Workshop, a participant did a terrific and rather novel job of developing the customer’s Situation Slide dynamically on a flip chart.


Typically, we present the standard bullets to our customer via a PowerPoint Slide:

- Job Title/Industry
- Critical Business Issue
- Reason
- Specific Capabilities
- Delta

Instead, he verbally articulated these bullets while drawing a rather compelling graph of the current situation vs. the desired outcome. The audience was fully engaged and even contributed additional pieces to the graph. Wonderfully executed!

Monday, April 12, 2010

GoToWebinar “Audience View”

The current version of Citrix’ GoToWebinar offers a very useful new capability. The “Audience View” tab in the control panel provides a small view of what the audience is seeing, including the delay time (latency). Nice!

Unfortunately, this capability is not (yet?) implemented in GoToMeeting – it would be great to have it…

Tuesday, April 6, 2010

Webinar Recording – A Conversational Approach to Selling Value

The recording from today’s webinar is now available, just in case you missed it… The webinar was entitled, “A Conversational Approach to Selling Value”, hosted by Citrix, and the URL for the recording is: : http://mfile.akamai.com/23543/wmv/citrixvar.download.akamai.com/23543/www/534/195/6790754472218534195/1-6790754472218534195-127d4d4c868.asx



Hope you find it useful – I’d be happy to send the article mentioned in the webinar and/or the presentation slides. If you’d like either, send an email to me at PCohan@SecondDerivative.com.

Thursday, April 1, 2010

Stunningly Awful Sales Prevention Demos

Does your organization have a “Sales Prevention Team” – people or processes that lengthen sales cycles and lose deals? Sadly, those who present Stunningly Awful Demos are often awarded membership on this infamous team.

Here are a few true examples of Stunningly Awful Sales Prevention Demos for your shock, horror, and amusement:


The Terrible Tabs Death March

I sat in on a demo recently where the presenter navigated to a page with 10 tabs showing and the proceeded to march through each of them, one by one, in detail.

It was very interesting to watch the body language of the audience. The response to the initial page was positive – it was a well-constructed dashboard and it looked good. The next tab was received with moderate interest, but at the third tab many of the audience members visibly sagged in their seats…!

By the fourth and fifth tabs nearly everyone had checked out (perhaps even the presenter, who had clearly presented these tabs many, many times…). There was an audible sigh of relief as the final tab was described.

This was a classic case of the presenter following the old, established, traditional demo pathway – a slow, painful march towards no sale!


Buying It Back

A true story from a few years ago: Discovery had been done well, the Champion was excited, the 50 target end-users were lined-up and interested. The Solution Consultant presenting the demo had an hour for the meeting…

In the first 10 minutes, he went through the key capabilities the customer was interested in. He then said, “Hmm – looks like we’ve got another 50 minutes left in our meeting today. Why don’t I go ahead and show you some of the other capabilities, other workflows, how to configure for different users and some other custom stuff?”

And he did. He spent the next 50 minutes showing a range of functions, workflows and capabilities – many of which were demonstrated in considerable detail.

At the end of the demo meeting the Champion chatted with the target end-users, then met with the selling team.

He told the vendor, “We’ve decided to purchase a single license of your software. We’ll put it on an expert’s machine and have all of the other users come to the expert to work the problems.”

“Why?” asked the sales person. “What about the other users?”

The Champion said, “The users said your software looked too complicated – they couldn’t visualize using it themselves.”

A classic, very sad case of snatching defeat from the jaws of victory – and of a reduction of the order size by $245,000 (annual fees!). Sales prevention at its worst!

The Moral? Stop selling when the customer is ready to buy...!


“Here are all the different ways to…”

Imagine you ask the presenter how to print a document during a demo. The presenter’s face lights up and she says, “Printing is one of our real competitive advantages!”

She chooses File Print from the menu, while also noting that you can use keyboard shortcuts as well, or voice commands, if your system is configured accordingly. She then shows how to set-up the voice recognition software, does a test, and then cancels out of it.

She next selects Print Options and walks through how you can choose different printers, or add a printer, or print to file. Next she shows the paper choices, the margin options, the print quality possibilities, tray management on the printer, the print queue, print preview, and print to PDF. Another 13 minutes of your life senselessly squandered by the Sales Prevention Team…

And, fascinatingly, she never actually chose “OK” to print the document – which was the only click she needed to show!

Moral Number 1: Just Do It.

Moral Number 2: Peel Back the Layers (in accord with the customer’s level of interest).


Peeling Back the Onion

A colleague once commented that “Peeling Back the Layers” is just like peeling an onion: If you peel it back too far, what happens? You cry!


Help, Mr. Wizard…!

Wizards are designed to make a complex workflow simple to use – but only if a reasonable path is followed! Here’s another true story:

The presenter started a wizard to execute an analysis of business data – and was still walking me through the options and settings 60 minutes later!

Once he’d finally completed that portion of the demo, I asked him to show me how to complete that same workflow using the wizard in the fewest number of steps – the way someone would typically use the wizard on a day-to-day basis.

How long do you think it took? About 2.5 minutes start to finish.

Moral: [Create your own pithy saying here…]


Desperation Demos

“Wait – don’t go away, we haven’t gotten to the best stuff yet!”

Or:

“OK, so that wasn’t interesting to you? Well, how about this? Or this? Wait, we’ve got much more, and more, and more, and more…”


The Overrun Overview

“So I said we’d only take 30 minutes – but, wow, it looks like I’ve been talking for 2 hours! Um, hello, are you still there…?”


The Sales Prevention Team is, unfortunately, only too alive and well. To avoid joining this team, even briefly, we recommend a Great Demo! Workshop, Seminar or reading a copy of the Great Demo! book.

What Sales Prevention Demos have you seen? Send your horror stories to us at PCohan@SecondDerivative.com and we’ll publish (anonymously) the most frightening.

Copyright © 2010 The Second Derivative – All Rights Reserved.

Friday, March 26, 2010

PowerPoint Cheat-Sheet – Particularly Useful Items

A colleague recent sent me Cheat-Sheets for PowerPoint and other Microsoft Office products (actually called “Quick Reference Cards” – but Cheat-Sheet is much more fun). I note that the Slide Delivery Shortcuts can be particularly useful and included some that were new to me:


Slide Show Delivery

End Slide Show           "Esc"

Jump to Slide               "Slide #" + "Enter"

Toggle Screen Black    "B"

Toggle Screen White   "W"

Pause Show                "S"

Show/Hide Pointer      "A"

Change Arrow to Pen  "Ctrl" + "P"

Change Pen to Arrow  "Ctrl" + "A"

Erase Doodles             "E"  [“Doodles” are ad hoc markings]


Send me an email (PCohan@SecondDerivative.com) if you’d like to receive the full Cheat-Sheet for PowerPoint or the full set for MS Office.

Tuesday, March 23, 2010

Remote Demos – Enabling the Audience to Catch-up

Here's a simple tactic to enable an audience to "catch-up" with what you are showing on your screen, particularly when dealig with relatively slow connections: Stop and then restart screen sharing. This effectively reloads the audience session.

This tactic can be particularly useful if you have been sharing screens with a large amount of images or scrolling graphics that require sending a lot of data to the audience machines. Works nicely!

Thursday, March 18, 2010

Brain Rules - Absolutely Required Reading For Sales, Presales and Marketing People

This book doesn’t appear to be about business, necessarily, but – it definitely is!

Brain Rules provides both the explanation and, more important, clear guidance on how to help you enable your customers to remember the material you present in demos (and via other communications vehicles as well).

Particularly useful and interesting are the following chapters:

- Rule #4: We don’t pay attention to boring things (attention)
- Rule #5: Repeat to remember (short-term memory)
- Rule #6: Remember to repeat (long-term memory)
- Rule #10: Vision trumps all other senses (vision)

I feel as though I’ve slowly (over a period of many years!) been discovering many of the principles that the author presents in the book. A colleague of mine wisely commented that “An hour of research is worth a year in the lab” – but, of course, he’s a cynic.

Summary? Read it. Here’s information on the book:

Brain Rules: 12 Principles for Surviving and Thriving at Work, Home, and School, John Medina, Pear Press, Reprint edition (March 10, 2009), ISBN-10: 0979777747, ISBN-13: 978-0979777745.

Thursday, March 11, 2010

The Demo Route That Shouldn’t Be Traveled

Imagine you want to drive to the store to pick up a few things for dinner – a trip that normally should take 10 minutes one way. You get into your car, leave your driveway and proceed down the street. Your car is equipped with a very intelligent voice-controlled GPS, however, which decides that there are other options you should see on the way.

The GPS takes control and turns off from the direct route to show you an interesting restaurant it thinks you might want to try sometime in the future. You thank the GPS, and ask it to return to the original course. It does so.

A few blocks later, it once again changes direction and drives 5 minutes to show you a nice park. “Terrific…” you say, “but please return to the original course.” The GPS sighs quietly, but obediently returns to the original route once again.

After a moment of quiet, the GPS makes a left turn and proceeds 8 minutes to a new home-products and hardware store. It announces proudly that the store just opened recently and is a great option for everything from paint to plumbing. Annoyed, you tell the GPS “Please return to course!” It does so, after grumbling that you really should see all of the cool options it knows about…

At this point you disable the GPS and proceed directly to the store – dinner will be late!

What if demos were delivered in the same manner? This pathway of driving off course to show potentially appealing options is truly an example of Sales Prevention at work.

A solution? Just “Do It”. Take the direct path from a logical starting point to completing the task. Avoid the urge to take those turns off course.

Monday, March 8, 2010

A Date Nit

Given that the purpose of software demonstrations is to (1) build a vision of a solution or (2) show proof, everything we do in a demo needs to support these objectives. In demos we are working to “suspend disbelief” in our customer audience – in other words, we need to make the demo appear to be as close as possible to real life. Anything we do or show that is obviously fake hurts our cause.

Two examples of making a demo obviously appear to be fake are:

- The use of silly or obviously fictional names (e.g., “Mary Manager”, “Dave Departmenthead”, “Sarah Superuser”).
- Naming files or processes “demo” or “test”.

To these I add a third, slightly less obvious item:

- Dates and date ranges.

I was watching a demo recently and noted that all of the reports that were run and presented showed data from 1998 and 1999. This automatically makes one wonder about the software: Has it been updated since then? Are their QA test suites that old? Have they tried the system with current data?

The old data also impacted my attention. Instead of listening and watching the next steps in the demo, I found myself wondering and thinking about data from 1998…

The morals are clear: Use real-life names (people, files and processes) and use dates that are contextually relevant for the customer’s situation.