Sunday, December 12, 2010

How Do Customers “Score” Scripted Demos?

It can be very interesting to compare how different customers score scripted demos in general – and it is important to understand how your customers are planning to score your upcoming scripted demos…

There are at least three scoring methods that are typically used:

1. Efficacy: How well does the vendor’s offering match the requirements – often done on a 5-point or 10-point scale.
2. Ease-of-use: How easy does it appear to use to accomplish each task – again often done a 5-point or 10-point scale.
3. Counting Clicks: customers often count the number of clicks or steps required to complete particular tasks – often as a way of normalizing and removing some level of subjectivity.

Some customers will subtract “points” for not following the proscribed script or other perceived deviations from their process.

Any other scoring methods you’ve come across?

Monday, December 6, 2010

What’s the Difference Between a Business Issue and a Critical Business Issue?

If you have ever “lost” business to “No Decision”, the following may be one reason:

All of us have “Business Issues” that we face every day – and that we do nothing about. “My laptop is slow, my cube is small, the commute traffic is terrible…” and so forth. We just live with these Business Issues. We may not like the status quo, but we don’t take action. A Critical Business issue is one that we are willing to address through the application of tangible resource – time, people, or money – to get it fixed or solved.

Here’s a wonderful example of the difference:

How long would you continue to drive your car with a slightly annoying squeak coming from the front wheels? A few days? A week? Month? Longer? Very few people will take their car to have the squeak diagnosed right away. Many more will do nothing, unless the squeak gets (markedly) worse. Others won’t do anything until something overt (and most likely bad!) happens… It is simply another “Business Issue” as long as the situation doesn’t change.

On the other hand, what if the brake warning light came on or the squeak changed to a horrible howl? Most people would get their car looked at right away, even if it meant taking time from work or home life, and spending a few hundred dollars for the repair. That’s because the issue is now critical – a Critical Business Issue!

Many sales opportunities go to “No Decision” because the customer didn’t consider the problem to be sufficiently important to address – it wasn’t perceived as a Critical Business Issue.

Tuesday, November 30, 2010

Encrispen

I’d like to propose a new word: “Encrispen” and suggest defining it as “the process and action of making something crisp, clear and focused”. It is the essence of a Great Demo!

If you were trying to communicate this idea to others, what words or images might you use? Here are a few starters:

Words:
- Crisp
- Concise
- Pointed
- Quick
- Focused
- Clean
- Swift
- Short
- Get-to-the-Point
- Brief
- Succinct
- Terse

Images:
- A camera lens (expressing focus)
- A crisp handful of paper money folded in half
- Origami items, similarly crisply folded
- A raft of razor-sharp pencils
- Potato chips (“crisps”, in the UK)
- A raptor focused on its target
- A vanishing point (an empty subway tunnel that vanishes to a point…)
- The business end of an X-acto knife
- A dart about to strike a dart-board dead-center

What other words, images or ideas might you suggest?

Monday, November 29, 2010

Buying an ERP System – Recommendations for Customers

A recent checklist from Inside-ERP (“ERP To-Do Checklist: Things to Ask Before You Write That BIG Check To A Vendor”) included four items that really resonated with me:

“What are the specific business problems you need to solve with ERP? For instance, do you need to shorten product lead times or improve communications with your suppliers? Are there industry regulations to which your company must adhere?”

Sounds very much like statements of CBI’s (Critical Business Issues) or underlying Problems/Reasons, used in creating Situation Slides for demos.

“What are the goals and metrics that you will use to measure the business benefits of your organization’s new ERP solution? A good starting point for these metrics are the KPIs — such as inventory accuracy, cost reductions and month-end closing processes — that your company is already tracking.”

Wonderful examples of possible measurements of the Delta – the value of making the change.

“What features and functions do you need from a new ERP solution that will help increase users’ productivity and provide access to the business data users most need?”

Simple statement of the Specific Capabilities needed.

The fourth recommendation promoted the idea of an implementation timeline – Transition Vision – and the concept of Early Wins “to allow you to implement them in phases... Taking the implementation in prioritized steps gives IT managers and ERP users a chance to learn new processes.”

Wednesday, November 24, 2010

“That’s Too Bad…”

A number of years ago I was part of a sales team presenting a demo to a large prospect in Houston (no names…). Things were going great – the end-users were loving the software and management heads were nodding in agreement.

The prospect’s IT manager asked, “Can our users store their data locally, in addition to on corporate server?”

Our presales guy, who was presenting the demo, quickly responded, “Yes, absolutely. Users can download and save datasets locally on their laptops in a few simple steps. Here – let me show you…” And he did.

The IT manager then said, “That’s too bad… We have a strict policy of no corporate data on local machines. We won’t be able to use your software…!” [Ouch!] A sad example of snatching defeat from the jaws of victory… What should the presales person have done?

Before jumping to answer “Yes!” (and rushing to demo the feature), he should have asked, “Why do you ask – what are you looking to accomplish?”

Friday, November 19, 2010

Making the Complex Seem Simple

In many demos, vendor software offerings are perceived by prospects as being “too complex; too complicated”. One of our objectives is to avoid this perception: Instead of making the simple look dangerously complex, we want to make the complex look wonderfully simple (while having great potential depth).

This is a key idea in Great Demo! methodology – and the “Do It” pathway is one example of how to achieve this. Another is to avoid words like “if” and “or” when presenting demos. What else can be done to help improve the perception of being wonderfully simple, yet with depth when needed?

Tuesday, November 9, 2010

New YouTube Great Demo! Videos

We’ve posted 4 new videos on YouTube at www.youtube.com/user/PCohan.  The first three are testimonials from our recent Great Demo! Public Workshop (September 2010) and the fourth is an interview done by DreamSimplicity (www.dreamsimplicity.com) at the same event.

Monday, November 8, 2010

Remote Demos – What If the Host Isn’t There?

What if you have been scheduled to join or present in a Remote Demo, but find that the host is late and has not started the online meeting on time? (Has this ever happened to you?)

One simple solution is to ensure that the host grants alternative host rights to a second person (e.g., you) so that you can start the meeting even if the host is late. This is a current capability in many of the online collaboration tools (e.g., WebEx, GoToMeeting, etc.).

Sunday, November 7, 2010

What Happens If You Peel Back the Layers Too Far?

A colleague once noted that Peeling Back the Layers is like peeling the layers of an onion – if you peel it back too far, you cry.  At a recent Great Demo! Workshop, a participant added that if you continue to peel, you not only cry but you’ll find you have nothing left!

Thursday, November 4, 2010

Great Demo! Example of Using Prop/Technology

A recent Great Demo! Workshop participant presented a demo to a large audience using a wonderful prop/technology combination – she used a webcam to show the live use of an iPhone application.  While there are very nice emulators that could have presented the app, using a webcam from her laptop to show the live video of her hands and fingers running the iPhone was very compelling.  It had everybody’s attention riveted!

Monday, October 25, 2010

What’s the Opposite of “Dumb-it-Down”?

Frequently, I hear Great Demo! Workshop participants comment that their software is often perceived as too complex, as overkill for many prospects – and that they need to “dumb-it-down” in their demos.  I’d like to suggest that an alternative, potentially more apt phrasing could be to “Smarten-it-down”…! 

Friday, October 22, 2010

“How Many Sales People Work for You?”

When asked, “How many sales people work for you?”, a VP of Sales replied, “About half of them…”!

Thursday, October 21, 2010

“What would happen if you do nothing?”

Far too often, sales opportunities result in losing to that most common of all competitors: “No decision”. During a discovery or qualification discussion, the question “What would happen if you do nothing?” is an excellent way to test the importance and impact of a situation – and to determine whether the business issue is sufficiently important to the prospect to pursue.

A follow-on question could be, “Would that be acceptable to you?” if the answer is “Yes”, then the business issue is likely not a Critical Business Issue – and would have a strong probability of resulting in “No decision”.

Tuesday, October 19, 2010

Remote Demos Team Practice

Here’s a simple, pragmatic tip: I have seen geographically distributed sales, presales and marketing teams use WebEx/GoToMeeting/Live Meeting (etc.) to conduct their weekly status/progress meetings on-line. This is a great way to build skills with the tools, with passing control among meeting attendees and practicing the use of the various annotation, white-boarding and other capabilities.

There is often a great deal of cross-learning that takes place – “Wow, I didn’t know WebEx/GoToMeeting/Live Meeting (etc.) could do that… Please show us how you do that!”

Monday, October 11, 2010

Remote Demos – the Role of the “Active Conduit”

[I'd promised to publish a more complete version of this some time after my initial post - here it is.  It is also available in article format as a PDF - send me an email at PCohan@SecondDerivative.com and I'll send it to you.]


The (very) best practice for Remote Demos is to split your forces – to have a representative from your organization at the customer site to serve as the eyes for the person presenting the demo remotely. The person at the customer site needs to be an Active Conduit of information to the demonstrator – he/she needs to be the demonstrator’s “eyes” on-site.

The lack of this Active Conduit feedback results in poor communication, confused presenters and audiences, and inconclusive results. Executing the role of the Active Conduit is critical to the success of Remote Demos – a passive representative from your company at the customer site is insufficient and a waste of resource!

For many vendors it is the sales person who typically sits with the customer at the customer site. Next best, if you cannot have one of your representatives present, is to ask your champion or coach to be your “eyes” for the meeting.

Here’s a brief list of the items that need to be communicated by the person at the customer site to the remote individual:

Before the demo:

1. Arrive at the customer’s conference room 15 minutes before the formal meeting is scheduled to begin to get things set up and operating correctly:

a) Start the collaboration tool (e.g., GoToMeeting, WebEx, Live Meeting, etc.) session on the customer side.

b) Help test and confirm screen resolution issues – “Yes, I can see your mouse across the full diagonal and we’ve maximized the screen here on the receiving end”.

c) Help test and confirm audio – “Yes, I can hear you fine… Here, let me move the conference phone microphones to better positions so that you can hear us better.”

d) Help test “latency” – “Looks like we have about a 2 second delay right now…”

2. Plan for managing questions – “Can you please plan to capture questions in a Word document from your laptop during the session?”

3. Review any other pre-meeting plans or issues.

During the demo:

1. Alert regarding “latency” – “Looks like you are about 3 seconds ahead of what we are seeing here… You may need to slow down.”

2. Somebody new arrives at the meeting – “Before you go on, we have a new participant in the room…” [And to ask the three questions:

a) What is your name?

b) What is your job title?

c) What would you like to accomplish during our session today?]

3. Somebody leaves – “Just to let you know, Bob had to leave the meeting….”

4. Unspoken questions – “Hang on, it looks like Jennifer has a question [furrowed brow, raised hand, look of confusion, etc.].”

5. Inability to hear – “John, let me repeat that question for you…”

6. Manage and alert during side conversations – “Hold on, we have a side conversation going on about the capability you just presented…”

7. Provide “color” commentary, as appropriate, e.g., “I want to let you know that they are all smiling and nodding their heads…!”

After the demo:

1. Debrief with the customer – face-to-face feedback provides nuances often missed via the phone.

2. Listen for “casual” conversations – what else are the audience members saying about the demo, the product, the company…

3. Afterwards, communicate this information back to the balance of the selling team.

You can train your own representatives to execute these items – or your champion/coach – by reviewing this list with them ahead of your demos. Following these practices will improve the outcome of your Remote Demos markedly!

Monday, October 4, 2010

Demo Self and Team Improvement Suggestion

Participants at Great Demo! Workshops often note that they rarely have a chance to see one another deliver demos to customers – to see and hear how colleagues present, and manage questions and situational challenges – and that this cross-exposure is often one of the most interesting outputs from Workshops.

Here’s a simple (but surprisingly effective) recommendation: schedule to do at least one “ride-along” on another team member’s demo each quarter. Ride-alongs can be done face-to-face or, much less expensively, via a remote demo using WebEx, GoToMeeting, or similar tool. The folks who participate in these sessions should also schedule time for a mutual debrief discussion: “What do we do well; what could we have done better?”

Some presales managers also include this idea as a quarterly

Thursday, September 30, 2010

Pre-Filled Login Dialog – Fewer “Clicks” and No Errors

I can’t tell you how many times I’ve seen a demo begin with, “Now I’ll log into the application…” – followed by one or more rounds of typing, correcting, being rejected (miss-entered login or password), followed by more typing (much more carefully the second – or third – time around)! I often suggest to start your demo already logged in, as a result.

However, many applications will time-out and require you to log in again if you don’t start your demo rapidly enough after introductions, etc. Here’s a simple solution to minimize the typing seen by the customer and to reduce the risk of login errors: enter your login and password – but don’t click on “login”. Simply leave it so that you have only a single click to login once the demo “proper” begins. Nice!

Tuesday, September 28, 2010

RFP – Acronym Alternative

Just heard at a recent Great Demo! Workshop:  RFP = “Request For Pain”.

Friday, September 17, 2010

A Cure for Zippy Mouse Syndrome

Record a few of your demos using Camtasia (or similar tool) to track your mouse movements – play them back and be prepared to be shocked...! Use what you learn to adjust and to slow your mouse movements down to make them smooth and d-e-l-i-b-e-r-a-t-e.

Friday, September 10, 2010

Remote Demos – the role of the “Active Conduit”

I note that the (very) best practice for Remote Demos is to split your forces – to have a representative from your organization at the customer site to serve as the eyes for the person presenting the demo remotely. The person at the customer site needs to be an active conduit of information to the demonstrator – he/she needs to be the demonstrator’s “eyes” on-site. Here’s a brief list of the items that need to be communicated by the person at the customer site to the remote individual:

Before the demo:

1. Arrive in the customer conference room 15 minutes before the formal meeting is scheduled to begin…
2. Start the collaboration tool (e.g., GoToMeeting, WebEx, Live Meeting, etc.) session on the customer side.
3. Help test and confirm screen resolution issues – “Yes, I can see your mouse across the full diagonal and we’ve maximized the screen here on the receiving end”.
4. Help test and confirm audio – “Yes, I can hear you fine… Here, let me move the conference phone microphones to better positions so that you can hear us better.”
5. Help test “latency” – “Looks like we have about a 2 second delay right now…”
6. Plan for managing questions – “Can you please plan to capture questions in a Word document from your laptop during the session?”
7. Review any other pre-meeting plans or issues.

During the demo:

1. Alerts regarding “latency” – “Looks like you are about 3 seconds ahead of what we are seeing here…You may need to slow down.”
2. Somebody new – “Before you go on, we have a new participant in the room…”
3. Somebody leaves – “Just to let you know, Bob had to leave the meeting….”
4. Unspoken questions – “Hang on, it looks like Jennifer has a question [furrowed brow, raised hand, look of confusion, etc.].”
5. Inability to hear – “John, let me repeat that question for you…”

Any others?

Sunday, September 5, 2010

Dessert Tray – Terrific Example of Vision Generation

A waiter in a nice restaurant wants to sell desserts to a dining party at a table. Compare the following approaches:

Option 1: The waiter says, “Are you interested in dessert? We have some really nice ones…”

Vs.

Option 2: The waiter brings a tray of fabulous-looking desserts to the table, presents them for visual inspection to the dining party and says, “Are you interested in dessert? We have some really nice ones…”

Which approach will generate more sales of desserts? Why? How can we apply this to demos? (Hint: Think Illustrations and the “Menu Approach”)

Sunday, August 29, 2010

Demo Calendar Madness

Many presales people find that they are often overscheduled with demos – I’ve heard numerous situations where demos are scheduled back-to-back. This can be particularly challenging for teams with highly transactional sales processes. Here’s some self-defense against Demo Calendar Madness (a horrifying affliction!):

Block your calendar with buffer time both before and after each demo.

[After you’ve said, “Duh…!”, allow me to continue…]

In my experience, sales people will hungrily consume all possible demo time from their presales counterparts. And any unoccupied calendar time is considered fair game. Sales folks often don’t know (or care) that the slot before their desired demo is a really tough two hour demo for one our your roughest prospects. They simply see the open slot – and grab it!

So, consider blocking 15-30 minutes ahead of any upcoming demo as your time to prepare – and another 15-30 minutes after each demo to debrief, decompress and restore your laptop/files/demo image to its normal pristine condition.

Your sanity will thank you for this…

Monday, August 23, 2010

Are You a Demo Expert? – Why Experts Should Feel Uncomfortable

That’s right. If you are a Demo Expert, you should be consciously uncomfortable. You should always be alert to find ways to improve your practice.

Some seasoned veterans – those with 5 or more years of experience – are often the least likely to change their ways. Many perceive themselves at the top of their game; many believe they are experts. They are the skeptics in many training workshops, the ones who arrive thinking, “I’ve been doing this for 10 years – what could they possibly teach me?”

Given the (shockingly) large number of demos that don’t achieve the desired objectives, is it possible that some seasoned veterans – the putative experts – are part of the problem?

 
[This is the intro to an article I just completed - it is too long to post in a blog - but send me an email PCohan@SecondDerivative.com and I'll send it to you...]

Thursday, August 19, 2010

Public (Open) Great Demo! Workshop

[Warning: Shameless Self-Promotion Alert!]

Our next Public Great Demo! Workshop is scheduled for September 15, 2010 in San Jose, California, 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. An overview, agenda, location and pricing information is available here: http://www.skmurphy.com/blog/2010/04/14/great-demo-workshop-on-sept-15-2010/.

Tuesday, August 17, 2010

Post-Demo Email Practices

What should you include in a post-demo email to the customer, beyond “thank you”?

Clearly, it should include any materials or information promised during the demo meeting – or, at minimum, a listing of the items promised. It should also, in my opinion, include any action items promised by the customer, along with the dates agreed upon for completion of both sets of items (vendor and customer).

A more “complete” version of a post-demo email can include a summary of the key capabilities that were demonstrated. This listing helps to reinforce the customer’s memory and can also serve as a vehicle to support vision generation, up-selling/cross-selling and out-flanking competition.

Additionally, I often suggest wording along the lines of “I’m glad we were able to invest the time together yesterday in our demonstration meeting…” as opposed to “Thank you for giving us your time yesterday”.

Any other ideas?