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.

Tuesday, February 3, 2015

Great Demo! – DemoChimp Webinar

Avoid the Tyranny of One-Size-Fits-All Demos! 

The recording is now available from the brief, but surprisingly compelling Great Demo! overview along with the balance of the webinar delivered with the folks at DemoChimp on February 19:  http://bit.ly/1AUUt37  

Wednesday, January 14, 2015

How Much Demo Do You Need? (“Just the right amount, please…”)

Imagine yourself as a customer in the following situation:  You’ve decided you need to improve your sales forecast and pipeline management system – you are using Excel today and it just isn’t sufficient anymore.  You’ve just started to explore what kinds of new tools are available and what options they provide.  You visit a number of vendors’ websites to learn about their offerings – you’d like to get an idea of what is out there and kinds of solutions are available. 

What level of demo from these vendors do you need at this stage?

Time passes, you’ve done more investigation, reduced your list of candidates and had discussions with a few vendors about their offerings – one of which did an excellent job doing “Discovery” with you.  You are interested in seeing how their offering might really work in your environment. 

What depth of demo are you looking for now?

Let’s compare these two scenarios:

In the first situation, you are looking for a “Vision Generation” demo – just enough to give you an idea of what is possible.  You are not interested in how to set things up, how things work “behind the scenes”, and all of the customization and configuration options.  Vision Generation demos should be crisp – and brief…!  Just a few key screens that illustrate what a solution might look like in your hands.  And, at this point, most likely you are only going to be willing to invest a few minutes to explore any particular product.

In the second situation, you’ve selected one or a few products as good possible solutions for your organization and now you want to how well they will really fit.  Will this product map to our specific sales process steps?  How about the way our regions are organized – and can it handle the products and licensing strategy that we use?  Your vendor should have invested a good chunk of time doing Discovery with you to discuss and understand your specific situation.  The demo that results from this discussion is called a “Technical Proof” demo and should be focused entirely on the specific capabilities you are looking for in a solution.  These demos might run much longer than Vision Generation demos.  Depending on your job title and depth/breadth of needs, a Technical Proof demo might run 30 minutes, 60 minutes, 2 hours, or longer.

DemoChimp (www.DemoChimp.com) provides a delightful solution for Vision Generation demos.  The ability to enable customers to choose the segments of interest to them maps wonderfully to the idea that “One Size Doesn’t Fit All”.  The solution envisioned by a VP of Sales for a sales forecast and pipeline management system is likely different from that of a sales person, and different again to someone supporting channel partners, and different yet again to someone in sales operations or product marketing. 

So how much demo do you need?  Just the right amount.  For Vision Generation, demos need to be brief, to the point, and focused on “what” good things the offering can do to help customers visualize solutions to their problems.  For Technical Proof, the resulting demo should address the specific capabilities uncovered in a Discovery conversation. 


Tuesday, January 6, 2015

What’s the Difference Between a Demo and a Joke?

In some cases, nothing!  The best part of a joke comes (wait for it…) at the end.  However, the best part of a demo should be presented in the first few minutes (within 6 minutes, in the best cases).  Those who “save the best for last“ suffer from exhausted audiences (who are too tired to appreciate the best part), reduced audiences (the highest ranking customers have likely left the room), and running out of time (“Sorry, we didn’t have time to show you our reporting capabilities – our best stuff – but trust me, they’re really great…”).


So, if you want your demo to be perceived as a (sad) joke, save the best for last…!

Monday, December 29, 2014

Land and Expand: The Importance of the Delta

No CFO will approve a major expansion of software without a clear understanding of the value equation.  The challenge, often, is that the people who bought the 1 or 2 seats of the original “Land” purchase generally don’t have the experience to uncover and communicate the value.  The vendor may be required to help the buyer with the process since many of these buyers have never orchestrated a large purchase. 

Buyers who go to their CFO’s with incomplete information are likely to be denied their request.  I’ve seen inexperienced managers present to their CFO’s with statements like, “We need a new sales process system; the old Excel system doesn’t really work…”

CFO responds, “Well, you’ve been using the Excel system for the past 5 years…  This doesn’t really seem compelling.”  [Rejected!]

Here’s a simple checklist (for the buyer) to help them with the purchasing process:

Critical Business Issue:  What over-arching objective or challenge are we [the customer organization] seeking to address?
Problems / Reasons:  What is getting in the way?  What systems or workflows are insufficient, and in what way? 
Specific Capabilities:  Here is the list of specific capabilities we are looking for in a vendor’s offering.
Delta:  This is the tangible value we expect to gain as a result of making the change – expressed in specific terms of time, people and/or money.
Critical Date:  The date by when we need to have a solution in place and driving force for that date.

Quick example:  A Director of Sales Operations of a large software company purchased a few licenses of a new sales process tool to try out, liked it, and now wants to deploy it across the full sales organization. Here’s what his summary checklist might look like:

Critical Business Issue:  Achieve 2015 sales revenue objectives; expand pipeline; reduce the number of “No Decision” outcomes.
Problems / Reasons:  Current sales process tool is an Excel application; hard to use, takes forever to roll-up; lots of errors and inaccuracies; actuals vs. forecast numbers rarely match.  Sales people hate it and reports are difficult to generate and distribute; sales managers are unable to accurately assess real opportunities vs. those that will likely end as “No Decision”.
Specific Capabilities:  Simple, fast, web-based entry and tracking of sales opportunities and process steps; clearly defined stages; simple checks on data and process accuracy; reports of weekly, monthly and quarterly forecasts, with highlighting of key projects and issues; rolling 3, 6, 9 and 12 month pipelines on per-rep and per-region basis.
Delta:  Reduce “No Decision” category results by 50%; increase overall revenues by 15% and 6-month pipeline by 25%.  Recover and redeploy 1.5 FTE currently consumed with the Excel system.
Critical Date:  February 13, 2015 for roll-out at 2015 sales kickoff event.

Now the case is much clearer:  The CFO knows why a new system is needed – what goals and objectives are at risk, what specifically what capabilities are needed, and (importantly) what value is expected as a result of implementation, as well as when (and why) implementation needs to take place.  The Delta – the value component – is key.  A CFO is much more likely to say “Yes” to this…!


[For more specific tips on uncovering the Delta, see my blog post on March 20, 2014 “Let’s Talk About Value – Uncovering the Delta”]

Monday, December 22, 2014

The REAL Buyer Stages...

Traditionally, vendors identify a set of Buyer Stages – the steps and thinking that a customer goes through en route to purchasing a product.  I think the traditional list is inaccurate and doesn’t reflect reality.  Here’s one example of the traditional list:

“Classically, there are four main stages:
- Awareness: Identify a business need;
- Consideration: Determine possible solutions;
- Research: Evaluate different solutions;
- Purchase: Select a solution and negotiate purchase.”

I’d suggest the following customer stages are more likely in buying enterprise software:

- Cluelessness:  the customer has no idea that he/she even has a problem…
- Semi-Awareness:  the customer realizes that there is a problem, but doesn’t care…
- Denial:  the customer prefers to ignore the problem and assume that it isn’t really an issue…
- Reluctance:  the customer agrees there is a problem, but wishes it would simply go away…
- Transference:  the customer blames another department/group/person/he/her customers for the problem and hopes they will take care of it…
- Acceptance:  the customer agrees that the problem is his/hers to solve…
- Cycling:  oops – “missed the budget cycle, guess we’ll have to wait until next year” (and maybe the problem with go away in the meantime)…
- Mandate:  senior management makes it a project and gives the customer a goal to solve the problem with an end-of-year deadline…
- Whining:  “I already have too much on my plate…”
- Delay:  “I’ll get to it later this year…”
- Sleep:  customer forgets about the problem for the next 10 months..
- Awareness:  customer realizes, 10 months later, that he/she needs to start working on solving the problem…
- Delegation:  customer forms a team of minions to define the problem and propose solutions…
- Bickering:  each team member proposes a different solution and defends said solutions in a life-or-death corporate struggle of power, intrigue, manipulation and warfare…
- First-Cut:  a set of three candidate vendor solutions are chosen…
- Research:  (by the vendors including, but not limited to, doing Discovery)…
- Vendors’ Presentations:  corporate overviews followed by product line overviews followed by infrastructure overviews followed by overview demos (oh god oh god no no no no no)…
- Deep Dive Vendors’ Presentations:  to an expanded set of players, repeat line above, but in four-part harmony…
- Proposals:  Vendor A:  “Pleeeeeeeeeeze be my customer….!”, Vendor B:  “Pleeeeeeeeeeze be my customer….!”, Vendor C:  “Pleeeeeeeeeeze be my customer….!”…
- Second-Cut:  one vendor removed, customer requests POC’s from the final two…
- POC 1:  three months of inactivity followed by one day trial, followed by “what’d you think?” from the vendor…
- POC 2:  three months of inactivity followed by one day trial, followed by “what’d you think?” from the vendor…
- No Decision:  both vendors are “OK”, but not “great”…
- Readjustment:  customer’s goals are reset for the next calendar year…
[Repeat from Delay as necessary…]
- Selection:  3-5 years later, a winning vendor is chosen…
- Negotiation:  customer agrees to price and terms; purchasing takes a piece, legal takes a piece, the CFO takes a piece; disgruntled players try to torpedo the deal…
- EOQ:  customer delays until December 30, negotiates an additional sizeable discount, plus training and implementation services “thrown in” for free…
- Purchase!  License agreement is back-dated to enable vendor to make his numbers; deal is signed December 35th.

[There are likely more stages, but this is a sufficient start – your add-ons are welcomed…!]

Of course, that is the set of stages for a seasoned veteran that has been with his/her company for many years.  Here are the stages for a newly hired VP or C-level Leader (yes this is cynical, but I believe we’ve all seen this happen!):

- Press Release:  new VP or C-Level Leader just hired!  
- Early Action!  he/she just came aboard and wants to establish presence through implementing a new sweeping program…
- Purchase:  buys the same system he/she bought at the previous company…
- Implementation:  rolls-out to team, followed swiftly by…
- Confusion:  things don’t work as expected…
- Blame:  fingers are pointed in all directions…
- Professional Services:  the vendor’s professional services team is called in to make things work as visualized by the Leader…
- Discovery:  an analysis of the customer’s people and processes reveals that the system will never work as desired – not now, not never…
- Sacking:  several middle managers and numerous staff are sacked, followed a few months later by…
- Resignation:  Leader resigns, citing “cultural differences”…
- Press Release from a different company:  new VP or C-Level Leader just hired!  
- Early Action!  [Rinse and repeat…]

Monday, December 15, 2014

Cold Calls - Do Vendors Research You Before Calling? (Nope)

I am amazed at how many vendors cold-call me, without doing ANY prior research on me or my company.  A little web searching (very little, frankly) would have revealed that I am NOT a good prospect for these vendors.  In spite of that, they call to talk about their products and services (“Hey, we’ve just had a new release and I want to tell you all about it!  It’s all about us, and nothing about you…”).  Most callers offer a demo of their offering, nearly right away – and very frequently offer a free trial or evaluation. 

I often take them up on their offers to see how their “sales” process operates and to stay up-to-speed with current products and services.  (I use “sales” in quotes because any opportunity that lists me or my company is HIGHLY likely to end as a “No Decision” – so sad!)

Typical triggers to receive this type of cold call, in my experience, include:

-          Signing up for a webinar
-          Downloading a paper or article from a vendor’s website
-          Having ever answered my telephone…

What’s been your experience? 


[I wonder how many of these cold calls are driven by “activity”-based metrics, such as “You need to make 20 calls and do 15 demos per day…”?  Sigh…]

Monday, December 8, 2014

Great Demo! and Stunningly Awful Demos Articles - What Have You Missed?

Hi All,

Here’s the current list of articles on demos in case you’ve missed any, organized by topic.  

They are available on this website the Articles page (www.SecondDerivative.com/Articles.html).  Each article has its own page and a link to a downloadable PDF version.  Feel free to forward them on to others, as well.

If you have ideas or suggestions for new articles, please let me know.  I’ll list a few candidates at the bottom – you can vote for the ones you’d like to see!

The “Stunningly Awful Demos” Series (a perennial favorite!)
Stunningly Awful Sales Tactics – The Future-Sales Prevention Team
Stunningly Awful Demo Communication – Unencrispening the Demo
Stunningly Awful Sales Kickoff Demos:  Selling to Your Sales Force – the Toughest Customer of All!
Stunningly Awful Demo Outcomes – Why Objections Shouldn't Need To Be Overcome
Stunningly Awful vs. Truly Terrific Competitive Differentiation – What, When and How
Stunningly Awful Demos – Two Words to Avoid
Stunningly Awful Web "Overview" Demos – The Gruesome Anatomy of a 1-Hour Web Overview
Stunningly Awful Demos – Insufficient Discovery
Stunningly Awful Demo Evolution – Have You Ever Seen Demos Get Shorter? 
Stunningly Awful Demos – The Great Demo! Top Ten List of What NOT To Do
Stunningly Awful Demos – Debilitating Demo Diseases
Stunningly Awful Demos – Debilitating Demo Diseases Additional Afflictions
Stunningly Awful Sales Prevention Demos
Stunningly Awful SaaS Demos – Lost in the Clouds
Stunningly Awful Remote Demos – The Top Ten List of Inflicting Pain at a Distance
Stunningly Awful Demo Situations – The Horror of Scripted Demos
Stunningly Awful Software Evaluations – A Strategy of Hope?
Stunningly Awful Demos Team Practices – Where 1 + 1 = 0

Great Demo! Core Concepts
Let's Talk About Value – Uncovering the Delta
Surprisingly Delectable Demos – Delightful Dining Analogies
Why Structure a Demo Like a News Article?
The Great Demo! Top Ten List
Stunningly Awful Demo Evolution – Have You Ever Seen Demos Get Shorter? 
Stunningly Awful Demos – The Great Demo! Top Ten List of What NOT To Do
Stunningly Awful Demos – Debilitating Demo Diseases
Stunningly Awful Demos – Debilitating Demo Diseases Additional Afflictions
Stunningly Awful Sales Prevention Demos
Attention Retention in Demonstrations
Too Complex – A Demo Disaster Story
Stand Away From The Mouse! – Letting Your Champion Drive

Advanced Topics
Stunningly Awful Demos – Insufficient Discovery
The Menu Approach – A Truly Terrific Demo Self-Rescue Technique
Stunningly Awful vs. Truly Terrific Competitive Differentiation – What, When and How
Stunningly Awful Demo Outcomes – Why Objections Shouldn't Need To Be Overcome
Stunningly Awful Sales Tactics – The Future-Sales Prevention Team
Stunningly Awful Demos – Two Words to Avoid 
What Makes a Demo Truly Remarkable? 
Demo Capital – Underutilized, Undervalued and Often Insufficient
Stunningly Awful SaaS Demos – Lost in the Clouds
Storytelling and Demos
Why Don't They Get It – Are They Stupid Or What?
Are You a Demo Expert? Why Experts Should Feel Uncomfortable
We Are Programmed to Forget - And Its Impact on Our Demos
Four Opportunities to Harvest – The Value of Informal Success Stories
Transition Vision - "We Love It – But How Are We Going To Get There?" 
The Database Break-Even Point

Remote Demos
Stunningly Awful Web "Overview" Demos – The Gruesome Anatomy of a 1-Hour Web Overview
Stunningly Awful Remote Demos – The Top Ten List of Inflicting Pain at a Distance
Remote Demos – The Role of the Active Conduit
Remote Demonstrations – What Can We Do Better? 
Demos to Mixed Local and Remote Audiences – Tips to Handle Combination Situations

RFP’s, Scripted Demos, POC’s, Trials and Evaluations
Stunningly Awful Demo Situations – The Horror of Scripted Demos
Stunningly Awful Software Evaluations – A Strategy of Hope? 

Team Topics
Stunningly Awful Sales Tactics – The Future-Sales Prevention Team
Stunningly Awful Demo Communication – Unencrispening the Demo
Death By Corporate Overview
Stunningly Awful Demos Team Practices – Where 1 + 1 = 0

New Product Roll-out 
Stunningly Awful Sales Kickoff Demos:  Selling to Your Sales Force – the Toughest Customer of All!
Why Don't They Get It – Are They Stupid Or What?

Presentation and Delivery Tips
The Meaningless-Filler Gratuitous-Phrases Vocabulary List
The Content-Free Buzzword-Compliant Vocabulary List

Growth and Development
Demo Skills Assessment – Do It Now

Recorded and Website Demos
Auto-Demo Hell
More Auto-Demo Hell – A "Customized" Recorded Demo? 
[On the positive side, check out DemoChimp at www.DemoChimp.com]

Trade-show Tactics
Trade Show Demonstrations – The Menu Approach

Just For Fun
'Twas the Night Before the Big Demo

And In the Future…
Here are a few candidate topics for my next articles:

- Stunningly Awful On-Boarding Demos – The Trouble Begins
- Stunningly Awful Demo Environments – Failing Early and Far Too Often
- Eight Engaging Examples (What Does “Great” Look Like?)
- Workflow Analysis – Uncovering Four Delightful Pieces of Information (That You Need)
- The Delusion of Product-Centric Demos
- Stunningly Awful Demo Detail – Let Me Explain What Happens Behind The Scenes
- The Terrible Tabs Death March

Vote for the ones you’d like to see and/or suggest others…!

Best Regards,
Peter


Copyright © 2014 The Second Derivative – All Rights Reserved.

Thursday, December 4, 2014

Fabulous Recorded Demos – Is This Possible? (Yes!)

Until recently, I have generally cautioned against using recorded demos (e.g., from AutoDemo) in marketing and sales processes, as it is unlikely that one recorded demo will fit the broad range of customers’ interests.  However, a bright young company has created a wonderful offering that enables recorded demos to automatically be tailored to address specific customers’ interests – really well done!  

Check out DemoChimp at www.DemoChimp.com.