Monday, July 27, 2015

Projector Connection Unpleasantness - And Related Surprises

I rarely write about hardware issues, but this has become so prevalent that I find I must take (virtual) pen to (virtual) paper…

How many times do we or a colleague connect a laptop to a meeting room projector (“Beamer” for some of our European friends…) and are surprised to find that screen resolution on the projector looks like 5 pixels by 3 pixels?  And the presenter can’t even FIND some of the commands that would normally appear on the bottom-right portion of their screen?  Or the “Extended” desktop has been moved somewhere but can’t be found?  Or that PowerPoint Slideshow mode does unexpected things like showing a neutral desktop (instead of the presentation)?

Laptop computer screen resolution has increased faster (much faster, in many cases) than for projectors.  What appears as a gorgeous, crisp, high-definition screen on your laptop (especially new Mac laptops) looks muddled, unreadable and truncated on the far end of the projector.  You may be trying to squeeze a 2880 x 1800 pixel display down to an 800 x 600 projector (and consider:  800 x 600 projectors are still being sold!).

Here are some cures for Projector Malitia (Projector Badness):

- Buy your own projector.  While (potentially) expensive, you will have control over your situation, at least for face-to-face demo meetings.  You’ll be able to pre-prepare your laptop screen resolution and know exactly what will be visible and how to find/work with the limitations of your specific projector.  Consider:  if you are selling software that runs $100K’s for each deal, don’t you want your software to display as beautifully as possible in a demo meeting?  If you can’t do this, then…

- Test your laptop with the projectors found in a pile of conferences rooms.  Go around your own organization and practice connecting your laptop to projectors in various meeting rooms.  Note what happens and generate a plan for the typical environment – and the worst environment.  Then go around a second time to test and make sure your typical and worst-case plans work!

- Now, generate a font-size eye chart.  Use PowerPoint, for example, and type a short sentence or word phrase (no longer than 1 line) into the content portion of the slide.  Choose a fairly large font size for this line.  Then copy and paste it below your first version and reduce the font by 1-2 points.  Repeat several times.  Connect to the projector, go into Slide Show mode, move to the back of the room and see which line you can read comfortably – that’s your minimum font size for that room/projector combination!

- Next, practice presenting portions of your demos with the reduced resolution.  Connect to a range of projectors and practice finding commands and screen locations that would normally be “right there”, but now need to be accessed via scroll bars (so much more fun when operating in VM’s…).  Contemplate adjusting your laptop screen resolution to find a best fit or sadly-happy medium.

- Turn off Presenter View in PowerPoint.  I can’t tell you how many times I watch presenters go into Slide Show mode and then cannot get the presentation to display through the projector – or they “Escape” out of Slide Show mode and suddenly can’t seem to display their normal, working desktop and only see a “sanitized” desktop.  The more recent versions of PowerPoint offer a sophisticated (?) “Presenter View” that can be confusing – and the default, as installed, is to have it “on”.  A solution?  Turn it off…!  (Go to the Slide Show tab, uncheck the “Use Presenter View” checkbox).  Now Slide Show mode should operate in the simpler, (hopefully) more predictable manner.


Hope these ideas help – any others to suggest?

Tuesday, July 21, 2015

Getting Pre-Demo Info from Sales People

Unfortunately, one of the biggest challenges faced by presales folks is the lack of information provided by sales before a demo.  “Just give them an overview” is what we often hear – resulting in the dreaded Harbor Tour demo...  Here are a few suggestions to address this challenge:

Call your sales person as soon as you receive the request for a demo and try to get the key pieces of information needed to complete a Situation Slide (Job Title and Industry, Critical Business Issue, Problems/Reasons, Specific Capabilities, Delta, Critical Date).  Often, sales people have this information in their heads but won’t write it down or send it to you in an email message (or enter it into the CRM system).  However, by interviewing your sales colleague and asking the questions, you may get what you need to prepare a reasonably focused demo.

A stronger approach is to do the same thing, but also open a WebEx or GoToMeeting session and share your screen with your sales counterpart.  That way they can see you typing the answers they provide to your questions – and they often take a stronger level of ownership of the results, accordingly.  In the best case, you’ll get what you need.  In some cases, you may both recognize that you don’t have sufficient information for a demo and that the next call with the customer should be a Discovery session, instead of a demo.  I recommend using double question marks “??” to indicate areas where more information is needed – this seems to help drive the realization that these gaps need to be filled before a demo…

Next, if you have sales people who consistently do not provide sufficient Discovery information prior to a demo, you should go to your manager and have him/her “push back”.  Your managers should (and need) to support a culture of Discovery first, demo next (if needed)…

In many organizations, the presales team has greater longevity with the company than the sales people – many of later may be relatively new hires.  A terrific approach is to simply state that “We always work to complete a Situation Slide prior to presenting a demo” or “We always do Discovery before delivering a demo…”  Make it a part of the corporate culture.

Finally, there may be situations where you still can’t get a reasonable amount of Discovery information prior to a demo (in spite of the selling team’s best efforts).  The Menu Approach is an excellent self-rescue technique that should help to avoid delivering a mechanical Harbor Tour demo.  You can find an article on the Menu Approach on my website at www.SecondDerivative.com/Articles.html.  (It is called, “The Menu Approach - A Truly Terrific Demo Self-Rescue Technique”.)

Other suggestions? 



Monday, July 6, 2015

Asking More Questions – Why?

Surprisingly, I often hear the following observation from Great Demo! Workshop alumni:  “Some of our sales people are concerned when we start asking questions about customers’ Critical Business Issue vs. pains, Problems and Reasons. They say we are digging too deep with questions for each opportunity…”

Keep asking – it’s the right thing to do..!   Here are two reasons why:

(1)    No Decision and
(2)    Not The Real Issue


No Decision:  One of the major reasons why sales opportunities result in a “No Decision” is that the customer agrees they have a problem, but don’t see it as critical.  They are willing to live with and stay with the status quo.  Here’s what can happen in these cases:

Customer says, “Yes, we are using Excel and we hate it – takes way too long and has far too many manual steps, plus errors creep in all the time…” 
Traditional Sales Team Response:  “Great, let us show you a terrific solution…” 

The customer sees a demo and says it looks great.  Customer does a POC and says it worked fine.  But the opportunity never closes.  Why?  Because in many cases, the customer is comfortable with the Excel Hell they know – and making a change is actually harder for them, from their perspective, so they stay with the current Excel environment.  It is only when something really critical is sufficiently impacted that they will make a change.  Otherwise, this sales opportunity is a candidate for No Decision.


Not the Real Issue:  When doing Discovery, you might compare the way you ask question with the way a doctor asks questions.  Many times a patient will describe certain symptoms and pains, but they are only indicators and are not necessarily the real, core issue.

For example, a patient could say, “I have a headache…”  For the doctor to accurately make a diagnosis and offer a prescription, the doctor needs to ask many more questions to determine the cause for the headache.   That symptom could be part of a cold or flu; it could be the result of an injury from being hit in the head; it could be a brain tumor (hope not!); it could be stress; it could just be a hangover.  The doctor needs to ask more questions to uncover enough information to make an accurate diagnosis.

Note that simply prescribing aspirin for the headache pain may not be the right solution for many of the cases above; the correct prescription will depend on accurate diagnosis of the real problem…! 

The same idea is also true in business – the symptoms (Problems/Reasons) generally have an underlying (and more important) Critical Business Issue.  Addressing the customer’s stated Problems may be insufficient to address the underlying Critical Business Issue. 



So, keep asking those questions…!

Monday, June 8, 2015

The Value of Reducing Risk – Difficult Deltas

What is the value, to a customer, of software tools that help reduce risk?  This is often difficult to uncover and convey, but the good news is that organizations need to manage and reduce risk.  Interestingly, the higher the level of the job title, the more clearly this is understood. 

Software that helps to manage and reduce risk is often equated to buying insurance – we’d rather pay a small amount each year to make sure we are protected against accidents, malicious acts and natural disasters rather than risking the full cost of replacement or repair of our house, car, or our health.  Typical business risks include, along with the costs:

-          Risk of data breach:  costs of suits and damage to corporate image
-          Risk of non-compliance:  fines, additional audits (often costly), possible damage to corporate image
-          Risk of natural or man-made disaster:  lost records (compliance risks), loss of productivity, costs of rework
-          Risk of human resources or customer interaction errors (another form of non-compliance, really):  costs of suits and damage to corporate image
-          Risk of project failure or delay:  loss of investment and/or rework costs, possible suits

One simple way (a good starting point) to assign a value to these risks is to research what has happened to other, similar organizations to your customer and use those specific fines and costs as real-world examples.   I did a quick Google search using “cost of data breach” and found the following:

1.    “The risk and cost of a data breach continue to grow. The recent Ponemon Institute Cost of a Data Breach study found the average cost of a data breach to be $5.5 million with average cost per compromised record more than $194.”

That’s from www.databreachcalculator.com/GetStarted.aspx (Ponemon Institute/Symantec).   

Other thoughts on this?


Tuesday, June 2, 2015

Revelation: Why So Few Pre-Demo Prep Calls


I have often wondered why, in many organizations, there are few or no pre-demo meeting preparation calls (between sales and presales folks).  The answer suddenly became clear:  it is because there is no point to a pre-demo prep call if:

- You always do the same exact demo each time…
- There is never any information about the customers’ needs, objectives or situation – and the plan is to simply “Show them a demo…”
- In spite of completing some degree of Discovery and uncovering some useful information, you still show the same exact demo each time…

The resulting demos will likely be perceived by the customers as one of the following:

- Show Up and Throw Up
- Spray and Pray
- Tech Splatter
- A Wet Noodle Demo
- A Museum Tour Demo
- The Talking Brochure
- A Harbor Tour
- Product Vomit
- The Hope Demo
- The “Hail Mary” Demo
- A Visit to IKEA
- The Core Dump
- The “Where is this going…? Demo aka
- The “Whiskey Tango Foxtrot” Demo [translation available privately…]

In case 1 above, there is little point in discussing the objectives for the meeting or the customer’s situation if the same demo is presented every time, regardless of customer needs or desires.  In case 2 above, you are clearly “living in the Land of Hope…”

Note that in case 3 above (where some Discovery is done), it is HIGHLY insulting to customers form them to invest time answering a number of Discovery questions and then have the demo IGNORE what had been discussed:

- Imagine going to a nice restaurant:   the waiter asks if there are any specific needs (vegetarian, vegan or gluten-free, for example) and learns that the group is strictly vegetarian – and the waiter then proceeds to describe “tonight’s specials, featuring the rack of lamb, filet of beef, venison sausage, duck breast and roast pork…"
- Imagine going to a doctor with a splitting headache:  and the doctor proceeds to put your arm in a cast, because that’s what he wants to do…
- Imagine going to a hardware store for a replacement lightbulb:  you ask, “Can you please direct me to the lightbulbs?” and you are told, “We’ve got a great selection of loose screws, nuts and bolts – I’ll take you to that area…”


The take-away message?  If your demo meetings fall into cases 1, 2, or 3 you should rethink your sales and demo processes!

Tuesday, May 26, 2015

Getting Better - Why I Write Things Down

When I’m delivering Great Demo! Workshops, I write down new ideas and thoughts to improve the Workshop – right then and there.  Why do I do this?  I do it to get better. 

Far too often, we think of a great new idea – and then later on we can’t remember what it was…!  (Has this ever happened to you?)  So I make a brief note, right away, so that the thought is captured and doesn’t get forgotten.

I find that this is key to making positive changes and improving my practice.  I set myself a personal objective to capture one or two new ideas, tips, or changes I want to make in each Great Demo! Workshop that I deliver.

- What new thing went really well that I want to repeat?
- What new idea did I encounter or learn that I want to try or develop?
- What bad thing happened that I want to avoid repeating in the future?

You might apply the same principle with your demos:  when you stumble upon something that works really well, or slam into something you never wish to repeat, or have an idea you’d like to try in the future – write it down!


[Note:  if your demos are simply running the same pathway over and over and over and over, you can ignore this suggestion – getting better will be tough!]

Wednesday, May 20, 2015

Frightening Statistics on Doing Discovery

I’ve done some informal interviews with heads of sales and presales recently and uncovered the following, rather consistent statements:

- Heads of sales and presales tell me that about 10% of their teams actually do Discovery very well.  [Group 1]
- They also say that about 70% of their team THINK they do Discovery well, but actually do not (in the eyes of their senior managers).  [Group 2]
- The remaining 20% of their teams do realize that they don’t do Discovery well.  [Group 3]

This reveals an interesting and rather frightening gap that deserves additional thought – and action to address…!  Looking at these three groups again:

- Group 1:  These people are either consciously or unconsciously competent.  Their knowledge and process steps need to be captured and taught to the balance of the team.
- Group 2:  These people are unconsciously incompetent.  This is extremely dangerous – they don’t know that they aren’t doing a good job.  As a result, they don’t realize what they lack and aren’t willing to take time to learn.
- Group 3:  These people are consciously incompetent.  They recognize that they lack certain skills and knowledge and may be interested or willing to learn.

[Quiet question:  which group are you in?  (Be honest with yourself…!)]

A few ideas to close the gap:

1.  Gather your best sales and presales people together (the Group 1 folks) for a half a day or so, have them generate Discovery Documents and outline the key process steps that they follow when doing Discovery.  Distribute to the balance of the field.  Train managers and mentors to coach Discovery role-play sessions for their team members (first making sure that the managers and mentors can use the Discovery Documents and execute the process steps well before they work with their teams!).  Consider hiring a 3rd party to facilitate and teach the above (hint hint).

2.  Track closed business when Discovery was sufficient (as measured, for example, by a completed Situation Slide) vs. where Discovery was insufficient.  This will help identify who is in Groups 1, 2 and 3…  It will also underscore the importance of doing sufficient Discovery, when the numbers are compared at the end of a quarter or two!

3.  Consider using a tool like DemoCoach (http://factorlab.com/demo-coach) to develop and reinforce good habits, and to share ideas with colleagues.

4.  Read the article, “Stunningly Awful Demos – Insufficient Discovery” for more ideas on doing Discovery and on the impact of not doing it well!  www.SecondDerivative.com/Articles.html

5.  Require reasonably complete Situation Slides prior to assigning resources for any demo scheduled to run more than 6 minutes.

Some additional observations I’ve heard from senior sales and presales management:

- Doing Discovery minimizes surprises – especially negative surprises.
- Many sales and presales teams believe they have and use a consultative model – but they really don’t!
- Many people THINK they have been learned how to do Discovery, since they’ve been through one or more sales methodology training courses – but most sales methodologies only scratch the surface.  Even worse, most sales methodologies focus on qualification questions as opposed to really doing Discovery.
 One senior manager positioned a lack of sufficient Discovery beautifully.  He said, “What you don’t know will hurt you…!”
- Another head of sales commented, “In corporate America, successful sales people are promoted – and are expected to manage their teams.  In the military, those same successful soldiers are first brought back to teach the other soldiers how to win…”


How do you successfully teach and reinforce Discovery skills in your organization today?

Tuesday, May 12, 2015

Stunningly Awful Car Sales Demo

This is a great (sad) story, contributed by Mike Horsfall, a Great Demo! Workshop alumnus:

Recently we had a hail storm and there was so much damage to my car that the insurance company “totaled” it, thus I had to look for a replacement.

So we went to the same dealer and explained the situation, that we were looking for a newer model of the same car, we know what it is like “all the features, as they are on the web”; we just want to drive it.

So the sales person proceeded to leave us for 15 minutes while he got the demo ready and “car brought around”.  He then proceeded to:

1.     Open the hood and explain how the VVT Variable Valve Timing worked
2.     The motor mounts are now break away so in the case of a front end collision the motor would break away and drop down and to the side to not impact the passenger compartment
3.     The front quarter panels are designed to collapse and take the force of a collision so again to not impact the passenger compartment
4.     The side walls of each door are equipped with 3, yes 3, not just 2 cross bars to protect the passengers
5.     Opening the rear hatch, he explained that it was the same size as the previous model, but now the door swung up, rather than sideways as the spare tire was under the rear floor mat
6.     Now on the rear roof, you will notice that the antenna is now about 6” inches tall not the typical 24” so it provides, less air turbulence and wind noise
7.     On the passenger side you will notice a slight ridge beside the side mirror, this is to streamline the airflow and provide better flow down the side of the car and make it quieter
8.     Opening the passenger compartment you will notice that we now have intermittent wipers, with not the typical 3 setting but 4 settings to allow much more flexibility to deal with rain
9.     Did I mention that we now have 6 way driver seat adjustments

We are now 25 minutes into the demo – and I still don’t have an answer to my Critical Business Issue: “Does it have the power of my old car?”

Finally I got in the driver seat, drove off the lot, tromped on the gas pedal, came back to the dealer lot and said, “Nope I want a V6 instead of the V4, this doesn’t solve my need!”


Monday, May 4, 2015

Fewest Number of Clicks

In Great Demo! Workshops, I urge participants to reduce each pathway they demo to the fewest number of clicks.  One of the (many) reasons for this is that people have surprisingly few “active” memory slots that they can use.  Here’s an example – I believe this has happened to most of us (only once, hopefully):

You are given a list of 5 items to buy at the grocery market by your spouse, partner or better-half.  Being an intelligent human, you think, “5 items, no problem – I can remember these…” and you don’t write them down.

You get into your car to drive to the market – and the list is still present and correct in your mind.  You arrive at the market and the list is still there.  You get out of your car and walk towards the market – and the list is still fully intact.  You go through the doors into the market – and 2 of the 5 items disappear, flushed from your brain!

You wander through the market and cannot recall the missing items, but pick up a few other items that weren’t on the original list.

You arrive back home with only 3 of the original 5, plus some bottles of beer (more likely if you are male).  Your spouse/partner says, “Why’d you get beer?  Beer wasn’t on the list…”  You respond, “Beer is always on the list…”

Everyone:  have you ever had this happen to you (or similar)?

In a demo, every click and step you show is filling up your customers’ brains and the limited number of “active”, available memory slots.  The longer the pathway, the more clicks or steps, the more likely you’ll have the following results:

-  It is harder for your customers to remember what you did.
-  It makes it look too complicated.
It seems like only an expert could use your software.


Solution?  Fewest number of clicks.

Monday, April 20, 2015

Checklists and Demos

Airplane pilots use checklists to make sure they do the right things as much of the time as possible (like always).  Checklists dramatically reduce the risk of bad things happening.  Should we apply the same principle to the wonderful world of demos?  (Everyone, say “yes!”…)

Perhaps a failed demo is not quite as bad as crashing an airplane, but consider:  Are there any demos that you don’t care about them being successful, similarly?  Assuming not, you may want to follow the same idea and use a checklist before the demo to make sure you are prepared – and post-demo to see if your preparation was really complete.

I’ve been delivering demo skills training as a business for 12 years and I still use checklists for many of my activities.  Doing Discovery (especially) warrants a checklist; preparing for trips; preparing for Workshops (several lists – my prep, room  infrastructure, etc. etc.).  I also follow a checklist process to debrief from Workshops, with an emphasis on constantly trying to improve the content, my delivery and (especially) seeing the participants implement the key ideas. 

There are (at least) four take-aways here: 

First, when learning a new process, a checklist helps you do the right things and avoid unnecessary errors or omissions. 

Second, “building great habits” implies many repetitions that will (hopefully) result in consistency.  Checklists enable consistency to take place – we are able to refer to checklists to make sure we’ve done the right things in the right order. 

Third, to get better.  In many disciplines where practitioners want to continue to improve, checklists are used both before and after sessions.  Before, to make sure they are properly prepared; after, to evaluate their performance (“what did I do well; what could I have done better?”).  An honest assessment of performance right after a demo can be surprisingly effective in driving improvement.

Finally, should a checklist (for demos) remain a constant?  (Say, “No”).  Checklists should evolve as practices change and improve.  New items should appear, older items may change of disappear, and more subtle items may surface as new areas of focus. 


We built DemoCoach to help Great Demo! practitioners achieve these objectives.  Great Demo! Workshop and Seminar alumni, and readers of the Great Demo! book will find  DemoCoach a gentle, personal coach – available on our smart phones (or via the web) to remind us of key preparation elements for a demo and to help us review how we did, post demo.  [DemoCoach is available at http://factorlab.com/demo-coach.] 


For non-Great Demo! alumni and readers, I encourage you to create your own checklist(s) and use them similarly to establish and improve your own practices.

Monday, March 30, 2015

Stunningly Awful Demo Phrases

Here are a handful of phrases that we often hear from software vendors in demo meetings, followed by what the customer thinks in response…

Vendor Says:  “Let me tell you a bit about our company…”
Customer Thinks:  Nope, no need to – we wouldn’t have agreed to invest our time in a demo if we didn’t already know about you…

Vendor Says:  “Let me give you a product overview…”
Customer Thinks:  Is this for our sake or yours?  Which of these products are relevant to us and our specific situation?

Vendor Says:  “And we’ve just re-named our products, as follows…”
Customer Thinks:  Oh joy, more useless things to remember…

Vendor Says:  “And we’ve created some product bundles as well – let me share these with you…”
Customer Thinks:  Why?  Am I doing proof-reading for your marketing department?

Vendor Says:  “Let’s go through a day-in-the-life…”
Customer Thinks:  Oh god, no.  My day is painful enough already, why would you want to walk me through it again?

Vendor Says:  “So we’ve created 7 fictional characters:  Mark the manager, Angie in accounting, Isaac in IT, Candace the CFO, Oscar in operations, Eustace the end-user…”
Customer Thinks:  Wait – you want me to remember each of these names?  I don’t even know all of the folks in my department…!

Vendor Says:  “One of the questions I get a lot is…”
Customer Thinks:  Sure, but did WE ask it?

Vendor Says:  “The other question is…”
Customer Thinks:  Ditto..

Vendor Says:  “And this is really important…”
Customer Thinks:  Thanks – good to know what YOU think is important, as opposed to us…

Vendor Says:  “Another really important thing is…”
Customer Thinks:  Sounds like everything in your software is important – which means that none of it is…

Vendor Says:  “The other nice thing…”
Customer Thinks:  How many nice things are there?

Vendor Says:  “Oh, and this is really cool…”
Customer Thinks:  In whose opinion?

Vendor Says:  “Now, if you want to…”
Customer Thinks:  But what if I don’t?

Vendor Says:  “Or, you can also do this by…”
Customer Thinks:  Please just show me the fastest way to get it done…

Vendor Says:  “There are three ways you can do this – let me show you…”
Customer Thinks:  Will these be on the test?  Please just show me the one fastest way that I’d use in my day-to-day work.

Vendor Says:  “Let me show you how to…”
Customer Thinks:  Did I ask?  Do I care?  Am I interested?

 Vendor Says:  “What we call…”
Customer Thinks:  Who cares what YOU call it…  I’ll never remember those terms anyway.

Vendor Says:  “We have the concept of…”-
Customer Thinks:  Great – and how is this important for us?

Vendor Says:  “Gee, I’ve never seen that happen before…”
Customer Thinks:  We have…  All the time!

Vendor Says:  “Let me try that again…”
Customer Thinks:  To prove that it REALLY doesn’t work you, the technical expert, don’t know it?

Vendor Says:  “Remember when I said….”
Customer Thinks:  Nope.

Vendor Says:  “Let me show you what happens behind the scenes…”
Customer Thinks:  Did I ask?  Do I care?  Am I interested?  I like sausage, but I’m not really interested in seeing how it was made…!

Vendor Says:  “Let me explain how this works…”
Customer Thinks:  Did I ask?  Do I care?  Am I interested?

Vendor Says:  “We’re running short on time, so I’ll have to go really fast, but I want this to be interactive, so stop me if you have any questions…”
Customer Thinks:  Oh god no – the run-on demo…!

Vendor Says:  “Oops – looks like we ran out of time before we got to the best stuff…”
Customer Thinks:  Too bad – looks like we won’t ever see your best stuff…

Vendor Says:  “I’ve saved the best for last…”
Customer Thinks:  When our management team is gone and the rest of our brains are mush…  Why didn’t you do the Last Thing First?



Any additional to add?

Monday, March 16, 2015

Observations, Progress and Habits - Accelerating Learning For Demo Skills

Interestingly, it turns out that nearly every culture around the world uses onions as one of foundation ingredients in cooking.  Why?  the compounds that make us cry when cutting onions become preservatives and/or antibacterials/antifungals when cooked – making cooked food last longer and safer to eat.  How did our forefathers (and foremothers) figure this out?

Many, many (many) observations.  As a result of tracking various ingredients and their impact on dining “efficacy”, people eventually noticed that when onions were incorporated in cooked food, the food lasted longer and produced fewer sick people than with non-onion preparations.  This must have required the observations and experiences of many people over many years – ultimately resulting in developing good habits (“cook with onions”) and progress towards improved living (safer food, healthier people).

Corollary:  The people that didn’t track their observations didn’t come to the conclusion to include onions in their cooking – leaving them at an evolutionary disadvantage (e.g., they died off while the onion eaters thrived, everything else being equal…).

The change from random ingredients to developing and practicing the habit of incorporating onions must of taken many generations – perhaps thousands of years.  (Why?  Because apparently early mankind did not have smart phones to help them remember things…!)

Do you see where I’m going here? 

Developing good habits for demos can take a long time, as well, if we use only our brains to remember the key steps and practices.  However, using a tool like DemoCoach on an iPhone helps us develop great habits much more rapidly than relying on memory alone.

DemoCoach used before a demo serves a similar purpose as a checklist.  (Note that airline pilots, in spite of having flown their aircraft hundreds of times, still use checklists to make sure they have prepared everything correctly before a flight.  Similarly, even after operating this business for nearly 12 years, I still use a Discovery document to help guide me in my Discovery conversations with my customers.)

Here’s an example of why checklists are important:  How many of us took a trip to market without a shopping list (“Gosh, it’s only 5 items – I can remember those…”) and then forgot two of the items that were on the list (“Honey, where is the ice cream I asked for…?”).  Note that NOT having a list doesn’t keep you from shopping; but you are likely to forgot what you came for and bring home items that weren’t on the list in the first place…  (Spouse:  “Honey, why did you buy beer – it wasn’t on the list…” Reponse:  “I thought beer was always on the list…”)

DemoCoach used after a demo provides the observations that drive awareness and the formation of great habits.  (“What did I do well; what could I have done better?”) 

Tracking observations and trying to remember process steps using one’s brain can take years – using a tool like DemoCoach can compress this time to a few weeks… The whole objective is to accelerate learning.


Onion soup, anyone?  

Tuesday, March 10, 2015

Great Demo! Self-Coaching Tool - Building Great Habits

Hi All,

Many of you have asked for a way to help refresh and reinforce the ideas we covered in our Great Demo! Workshops and Seminars – some way to support you when you are preparing demos, working with your colleagues (e.g., in sales), and post-demo to reflect on how things went.  Now, there is…!  Presenting:  your personal DemoCoach!

My colleagues at FactorLab (www.FactorLab.com) have created a wonderful way for you to reinforce the key parts of the Great Demo! methodology.  DemoCoach is being offered by FactorLab to Great Demo! Workshop and Seminar alumni for your use for free.  It is a personal tool to help you establish and improve practices and to develop truly terrific Great Demo! habits.

- Do I have a complete Situation Slide?
- Is that really a Critical Business Issue for this customer?
- Was the demo really a two-way conversation with the customer?

These are the kinds of questions we often ask ourselves before and after demos.  DemoCoach enables you to track your own progress – and, as the community of DemoCoach users grows, you’ll be able to compare your results anonymously with your peers.

Using DemoCoach takes about the same effort as sending a text message or two – and that small investment will likely pay sizeable dividends in terms of improved demos…!

We’d like this tool to truly enable the Great Demo! Community – we look forward to your feedback, comments and suggestions.  Looking forward to your ongoing improvement…!


Get started now!  http://factorlab.com/demo-coach

Thursday, March 5, 2015

[Warning: Shameless Self-Promotion Alert!] 2015 Great Demo! Public Workshops

There are two Great Demo! Public Workshops currently scheduled for 2015, as follows:

-          May 14-15 – Near Salt Lake City, UT.  Registration and additional information can be found here.
-          October 14-15 – San Francisco Bay Area.  Registration and additional information can be found here.

These are excellent opportunities for individuals, small groups or for teams that have new hires. Both are 1.75-Day Workshops, with the first day focusing largely on core Great Demo! material and the second ¾ day addressing more advanced topics and techniques. 

The May 20-21 and October 14-15 Public Workshops will take place in the San Francisco Bay Area (Sunnyvale), in conjunction with the folks at SKMurphy.  

We’ve found that these sessions are most productive when there are two or more participants from each organization – and best when a combination of sales and presales participants are present (singletons are also fine). This helps to mimic real-life interactions as much as possible, both when preparing demos and delivering them in the role-play sessions.

PS - If you do decide to register for the San Francisco Bay Area Public Workshops and are coming from out of town, you might want to make reservations now at the hotel where the Workshop will take place (or nearby), as hotels in the area tend to fill up rapidly. 


Wednesday, February 25, 2015

Holy Cow…! Over 20,000 Copies of Great Demo!

I am amazed (and quietly proud) to report that well over 20,000 copies of Great Demo! have been purchased (not including re-sales of used copies or hard copies or PDF’s that get  passed around). 

The question is now becoming:  how well do you (and does your team) implement and practice the methodology? 


The Great Demo! methodology enables differentiation; the degree to which one applies the methodology determines the amount of differentiation!

Monday, February 16, 2015

Stunningly Awful On-Boarding Demos – The Trouble Begins

“Learn the demo…” the group of newly hired presales folks are told, “and when you think you’re ready, we’ll have you present the demo back to us.  If you do well, you’ll be certified and ready to start presenting to customers.”  What’s wrong with this picture?

It’s a terrific approach if all customers are exactly the same – otherwise, it forces the tyranny of a one-size-fits-all demo upon a broad range of customers, ignoring the specifics of their situations.

Would one size and style of shoe fit all feet?  (“Gentlemen, I invite you to contemplate your shoe:  a women’s faux suede leopard skin 6 inch heel size 6 pump…”) 1

Would one dining choice fulfill all appetites?  (“Folks, our offering tonight is lightly larded lima beans in a spinach puree…”) 2

Clearly not!  But wait, there’s more…

Nine Months Pass…

And now our team, having delivered dozens of demos, becomes very comfortable with presenting – so much so, in fact, that they begin to ignore the customer. 

True story:  I didn’t need to be at my laptop for this demo… 

It was delivered to me over the web, via WebEx.  The presenter talked, pointed and clicked for 1.25 hours without ever checking in with me!  I truly didn’t need to be at my laptop – he was just fine going through his talk-track by himself. 

In fact, during the session his voice cut out – twice –and both times after several long minutes I finally had to use “Chat” to let him know I could no longer hear him…!  He never checked in to get my response, he never engaged me in a conversation; he didn’t even ask if I had caught up on my email (I did).

We are victims of momentum – we do the same things the same way unless someone gives us a shove in a new direction.  [~97.5% of us resists change – Evert Rogers.]

1 Actually exists – Amazon.com “Ollio Women's Shoe High Heel Platform Faux Suede Multi Color Pump”.

2 Made this one up… 



Deconstruct – And Reconstruct

Is it OK to learn the standard demo?  Certainly, but be prepared to use it as a starting point – one example of what could be many demos… 

So does that mean that you have to learn dozens of demos, one for each customer situation?  Possibly, but that’s a rather tough course to take. 

Here’s an alternative:  think in terms of deconstructing your standard, end-to-end, day-in-the-life demo into component pieces – “chunks” – and then reassemble these component chunks as needed to fit each specific customer situation you face. 

[Many software vendors present this same idea as configuration vs. customization, where configuration is the process of assembling a solution from pre-built components that then appear to be customized for specific customer requirements, rather than coding each specific solution individually (and potentially painfully for all parties involved!).]

For example, contemplate a standard CRM system demo, which might consist of the following (which I am NOT advocating as a good sales process or a plan for a demo!):

1 - System admin and set-up options
2 - Enter a new record as a lead
3 - Include in marketing campaign
4 - Track responses to campaigns
5 - First call with inside sales
6 - Promote to qualified lead, pass to field sales
7 - Call with field sales person
8 - Schedule demo
9 - Send proposal
10 - In negotiation
11 - Close sale
12 - Include in upsell/cross-sell marketing campaigns
13 - Roll up quarterly forecast and 6-month pipeline
14 - Dashboard and report creation and editing
15 - Dashboards and reporting (forecast, pipeline, key opportunities, campaigns)

A traditional demo would walk the customer through each of these steps, generally consuming the full amount of time allocated for the demo.  The example above could easily take an hour of more – and presenters often run out of time before being able to present the reporting capabilities.

This means that the most important people (e.g., the Head of Sales), won’t see what is most important to him/her until the very end of the demo (if he/she is still present in the room!).

Very Scary – And Liberating

Now consider the following job titles and select the chunks relevant to each:

System Administrator:
Inside Sales Person:
Field Sales Person:
Marketing Manager:
Head of Sales:

Here’s one set of slice-n-dice reconstructions of the chunks that map to the specific interests for each job title (how did yours compare?):

System Administrator:  1-15
Inside Sales Person:  2, 4-6
Field Sales Person:  6-11
Marketing Manager:  3, 4, 12, 14, 15
Head of Sales:  15 and maybe 14

There is likely only one person who is really interested in all 15 steps – which one?  The System Administrator, who also likely has the least impact in the decision-making process.

If you are presenting to the Head of Sales, your demo (chunk 15 and perhaps 14) might only take a few minutes.  Does he/she want or need to see the other chunks?  Nope, not necessarily. 

[You can always ask, of course, but be prepared for the Head of Sales to say something delightful such as, “No, I’m good – I’ve seen what I wanted to see and this looks like what we need.  I have another meeting to go to; the rest of you can stay and torture the vendor as long as you wish…!”]

Why is this both very scary and liberating?  Because it requires us to think!  It’s liberating because it frees us from the tyranny (and boredom) of presenting the same one-size-fits-all demo over and over and over.  It’s scary because, yes, it requires us to think and reconstruct our demos in accord with the specific interests of our audiences.

The Standard Demo Revisited

One simple (and rapid) way to put this deconstruct/reconstruct principle into practice is to teach new-hires to apply it to the standard demo for their certification sessions. 

When preparing for the certification, have your new folks break the standard demo into chunks and organize those chunks in accord with the job titles the certification team is modeling.  They get bonus points, of course, for “Doing the Last Thing First” for each chunk.  Each chunk should likely be about 3-4 minutes in length, for most software.

A colleague pointed out to me that habits are established very early in an on-boarding process, so the earlier we teach new team members to deconstruct/reconstruct the standard demo, the sooner they will apply these new habits with customers!

New Directions – Boldly Exploring

Overall, one objective of on-boarding demo training should include collecting and learning to deploy a set of demo chunks – stand-alone portions of demos that represent high-probability use-cases, workflows, and deliverables. 

Here are a few ideas to help broaden perspective and begin to collect these chunks…

[A colleague of mine phrased this as, “Your five-year mission:  to explore strange new demos, to seek out new demo chunks and deliverables, to boldly demo where no man has demoed before!”].

Go sit with a few of your current (happy) customers and see how they use your offerings today.  You might consider a structured approach to meeting with these customers and use a format such as:

-  Job Title/Industry:  For each individual you interview…
-  Critical Business Issue:  What top level goal or objective was at risk?
-  Problems/Reasons:  What did they have in place before; what were the "pain" points, what was taking too long, too many people, was too hard, etc.?
- Specific Capabilities:  What capabilities, in particular, was this person looking for as a solution?  What workflows, what reports, what deliverables?  These represent likely demo chunks for this job title.
- Delta:  What was the value of making the change (best expressed as a tangible number)?
- Critical Date:  Was there a date or event that drove a need to have a solution place?

Collect these for a series of individual job titles – and very rapidly you'll have a set of chunks you can draw from – chunks that will likely resonate with prospects that have similar job titles and situations.

Let Your Customer Do the Demo

Here’s a wonderful approach:  ask your existing customers to demo to you!  Ask them how they are using your software today:

- What workflows?
- What outputs and deliverables?
- What do they really find terrific?

You’ll typically learn two sets of scenarios when you apply the approach:

-        Set 1:  Your customer shows you workflows and deliverables that you expected them to use.  That’s good – and each piece that you see represents a chunk that you can add to your collection.

-        Set 2:  Your customer shows you workflows and deliverables that you had no idea customers might use.  That’s truly terrific!  Now you have some new, never-before-seen chunks to reuse.  You can harvest these success stories and share them with your team and, as appropriate, with other customers.

Along similar lines, attend and/or watch recordings of customers’ User Group Meeting presentations and demos – fabulous!

Learn From (Some of) the Best

There are likely a number of seasoned, well-respected – and most important – high-in-demand presales folks in your organization.  They may offer a rich resource for demo chunks proven to be successful.  Contemplate doing “ride-alongs” with these people, either in person and/or over the web.

Other Vendors' Demos

Watching demos from other vendors is a terrific way to regain a customer’s perspective.  I suggest that you watch demos from vendors where you actually have an interest in their products – this helps to make the interaction as real as possible – be a customer. 

Sign up for a demo from the vendor’s website and see how you are treated as a customer:  Did they just schedule a demo without asking any questions or doing Discovery?  Was “Discovery” simply a set of 3-4 quick questions – and the presenter couldn’t wait to dive into the demo?

How about the demo itself:
- Was it engaging?
- Did it address your interests?  Did they present just the chunks you were interested in or an entire, standard, end-to-end, day-in-the-life, kill-me-now demo?
- Was it interactive – or was it a furious fire-hose delivery of flying features and functions flung frantically?  Frankly frightening,
- Did you find your attention wandering – did you “check out”?  (And if so, how long did it take?  Were you able to catch up on your email during the demo?)
- What could have made the experience for valuable for you, as the customer?

You may wish to apply what you learned to your own demos and processes!

[I’m occasionally surprised to find presales and sales staff who have never seen another vendor’s demo – not even demos from a competitor…  So, if you haven’t seen demos from other vendors, it is time to do so!]

Configure and Customize

Habits are often established during the on-boarding process – and can become the norm for years following after.  The earlier that new hires are taught to deconstruct standard demos into component pieces – chunks – and to learn how to reconstruct and reassemble those chunks to meet specific customer situations, the better.

There is nothing inherently wrong with the standard demo or certification process.  But use it as a starting point – collect and create a library of demo chunks that you can draw from and assemble demos for specific job titles and situations.  Having a library of demo chunks enables you to configure your demos from pre-built pieces, while giving your customers the impression that you have painstakingly customized the demo just for them!



Copyright © 2015 The Second Derivative – All Rights Reserved.