Heard from a very wise presales manager recently: “Presales folks are not paid by the word…!”
Tips, thoughts, tools, techniques and practices to increase success rates with software demonstrations
Thursday, June 26, 2014
Wednesday, June 18, 2014
Another Cooking Analogy for Demos – Length of the Recipe
A recent Great Demo! Workshop participant observed that for
most home cooks, a recipe that has a long list of ingredients and a long set of
instructions is less likely to be chosen over one that is shorter. He also pointed out that the longer, more
complicated recipe presents more chances to make mistakes (“Damn, it wasn’t
supposed to look like that…!”).
Clearly these ideas are directly applicable to demos!
Monday, June 9, 2014
“A Day in the Life…” Reduced to “A Few Minutes in Your Life…”
Many vendors’ software demos present “A day in the life” for
a customer – generally consisting of trying to follow the activities of a
series of confusing fictional characters as they work through a set of somewhat
interrelated tasks, interspersed with loop-backs, “remember this from earlier?”
statements, “if” and “or” pathways (“Now, if
you want to do this, then you…” and “Or, here is another way to do the same
thing…”), extensive excursions into “Setup Mode”, and lost time getting dragged
off-track into the deep, thick weeds…
Yes, these demos are still (unfortunately) very much alive –
just suffered through one a few days ago…!
But there is a remedy: A recent Great Demo! Workshop participant just reported that
Doing the Last Thing First caused one of his customers to say, “Wow, you just
reduced a painful “day in the life’ down to ‘just a few minutes in my life.’ Thanks!”
Sunday, June 1, 2014
Stunningly Awful Demo Communication – Unencrispening the Demo
Stunningly Awful Demo Communication – Unencrispening the Demo
The higher
the customer’s job title, typically, the stronger is their desire for vendors
to be crisp, focused and precise in their communications. “Get to the point!” is what many senior managers
are thinking, even if they don’t say it out loud. Instead, their actions often speak louder
than words, as they quietly get up and walk out of the demo after just a few
minutes…
Here are a
few areas where we can likely improve our verbal delivery in demos:
Mixed Metaphors
“This will
help you knock it out of the park and out-flank your competition…!” says the
vendor. “Huh?” thinks the customer – who
misses the next several sentences from the vendor as he chews on the verbal
gristle he was just served… If you are
going to use a metaphor, stay with it!
Don’t swap horses in the middle of the meal! (How’s that for a bad one?) Here are a few more, just for illustrative fun:
"I don’t think
we should wait until the other shoe drops. History has already shown what is
likely to happen. The ball has been down this court before and I can see
already the light at the end of the tunnel."
(Detroit
News, quoted in The New Yorker, November 26, 2012)
"I knew enough
to realize that the alligators were in the swamp and that it was time to circle
the wagons."
(attributed
to Rush Limbaugh)
"The committee
was tired of stoking public outrage with fortnightly gobbets of scandal. It
decided to publish everything it had left, warts and all. Now everyone is
tarred with the same ugly brush, and the myth that forever simmers in the
public consciousness--that the House shelters 435 parasitic, fat-cat
deadbeats--has received another shot of adrenalin."
(Washington
Post, 1992)
“I’ve decided to
put down roots and send up a trial balloon – I’m throwing my hat in the ring…!”
(anonymous,
for now)
Blech and gack.
Inappropriate Analogies
“We eat our
own dog food…!”
Ick,
really? Why would you do that? Instead,
contemplate communicating the same idea with a gentler version, “We drink our
own champagne.” Much more palatable!
Your vs. You’re
This is just
sloppy writing and proofing – but how many times do you see someone use “your”
when they should have written “you’re”?
Just saw an example recently:
“Your really going to like this upcoming release!” Sigh.
Don’t you
wish your word processer had a “reality checker” in addition to its
spell-checker and grammar checker?
Colloquialisms
A few years
back I was hosting a visit to our facilities by a group of Japanese customers,
whose English was fairly good (but not complete). At one point in the discussion our head of
development responded to a question regarding timing for delivery of a specific
capability – he was then asked, “How did you come up with that timing?”
He replied,
“Oh, I just pulled those numbers out of my butt…” I watched our customers’ faces as they
contorted, trying to make sense of his answer…
Fortunately, one of our guests was able to understand the idea and
provided his colleagues with a more accurate (and less literal) translation –
and smiles and nodding heads replaced the perplexed (and slightly frightened)
expressions.
Many
U.S.-based sales, presales and marketing people communicate as if the rest of
the world has fully adopted our version of English. They are, of course, in error. They have missed the pitch, dropped the ball,
fumbled the handoff, and simply not make the extra point. (How’s that for a combo with mixed
metaphors?)
Solution? When presenting to international audiences,
consciously choose vocabulary and word phrases that are simple, clear and as
internationally universal as possible.
Two Countries Separated By a
Common Language
This famous
quote by Winston Churchill highlights additional differences in English spoken
in different locations. A number of
years ago, we had a Marketing Communications (MarCom) group that was not
particularly well-beloved by the field sales and presales organization. The result was this rather embarrassing
story:
The MarCom
group typically provided “give-aways” for the various trade-shows that we
attended. In one case, they produced a
particular piece of apparel complete with our logo brightly imprinted for a trade-show
in London. Now, in the U.S. this
particular item is called a “Fanny Pack”.
In the UK, “Fanny Pack” has, well, a different meaning (you are welcome
to look it up yourself…!).
Our MarCom
group generated signage for our booth at the show, emblazoned liberally with
“Get Your Fanny Packs Here!” The signage
was installed at the booth and when the show opened it certainly attracted more
attention than our MarCom folks had anticipated…! An (embarrassingly high) number of UK
customers came to the booth and asked, rather loudly in many cases and with
great mirth with others, “Can I please have a fanny pack?”
Sigh.
Regional Differences
You, Y’all
and All Y’all: Which is singular and
which is plural?
Add these to
the list above… But wait, there’s more…!
Slinging Slang: That Dog Don’t Hunt and Other Homilies
In San
Diego, “Gnarly, Dude…!” is an expression of appreciation (and/or the presence
of large, thin-lipped, glassy, tubular waves – or exactly the opposite: slow, blown-out mushburgers).
In New
Hampshire, you may be told, “But it won’t do you no good, you can’t get there
from here…” (pronounced “heah”), meaning your directions are faulty.
In the Carolinas,
“That dog don’t hunt” indicates that your suggestion likely won’t work.
In Texas,
“It’s fixin’ to rain” is a weather forecast and “fixin’ to…” indicates that
something is likely to happen.
In Hawaii,
“Da kine!” is what you want to hear, in conjunction with an accompanying “shaka.”
And here’s a
beauty that combines several items from the topics above:
“I conclude that the
city’s proposal to skim the frosting, pocket the cake, and avoid paying the
fair, reasonable, and affordable value of the meal is a hound that will not
hunt."
(a
labor arbitrator, quoted by the Boston Globe, May 8, 2010)
Solution? Again, choose verbiage that is as neutral as
possible – particularly when working with international groups or customers
from diverse U.S. locations.
International Equivalences
“It’s
awesome!” in the U.S. is the same as “Ja, well, it is adequate” in Germany and
the UK’s “That’s brilliant!” (but it is likely that the UK offering was really
meant to be sarcastic…).
Listen
closely!
Cloudy With a Chance of Feature
Obscuration
Vendor says, “For this next new
feature let me explain our thinking and rationale for development…” followed by
“and here’s the underlying architecture, schema and data organization…,” which
leads to “the seventeen options for configuration and set-up,” “the three
different ways of accomplishing the same task” and the “hundreds of pre-built
templates and reports we’ve generated…”
The customer, reeling under this
onslaught of verbal rubbish and useless details, wonders “Where is this
going…?” followed minutes later by “When will this be over?”
Solution? Start with what good things the new
capability will enable – the relevant deliverables – and then offer explore it
in as much depth as the customer is
interested in seeing…!
Note that
the affliction above often develops into a more violent and virulent form,
known as…
Expert’s Disease
Many of us
with technical backgrounds feel obligated to explain how things work – before providing the simple answer desired by the
customer. For example, your customer asks,
“What time is it?”
You respond,
“Well, in order to tell you the time, let me first explain how a watch
works. Now in this watch, the time is metered by a small quartz tuning fork that
vibrates at a constant frequency – assuming, of course, that it is in a sealed
environment, because the density of the surrounding medium will impact the actual vibration frequency. Now the older manual watches used a coiled
spring and an escapement mechanism, which operated on the principle of an
impulse action and a locking action, actuated generally with either a pendulum (in
large, standing clocks) or a rotating balance wheel and um… sorry, what
was your question again…?”
A
solution? Answer the immediate question
right away – and then test (ask) if your customer desires further elucidation.
Kinda, Like, Sorta, Ya Know?
As noted at
the beginning of this article, the higher the job title, typically, the
stronger is that person’s desire for vendors to be crisp, focused and precise
with their communications. Imagine the
reaction of a 55 year-old Senior VP to a vendor saying, “And like here, kinda,
are the types of reports that we, like, sorta do, ya know…?”
Instead, be
precise: “These are three examples of
reports you can produce with our tool.”
Much better!
The Content-Free
Buzzword-Compliant Vocabulary List
In a demo,
the vendor states, “Our powerful software is flexible, intuitive, easy-to-use
and integrates seamlessly with your other tools. Robust and scalable, your organization can
enjoy the benefits of our best-of-breed world-class offering – the most
comprehensive solution available.”
What have
you learned so far? Nothing, other than
this person is clearly a talking marketing brochure (and that you may be able
to declare victory in “Buzzword Bingo…”)!
Vendor credibility drops precipitously and the audience furtively starts
to check email and the sports scores on their smart phones…
Robust, Powerful, Flexible, Integrated, Seamless, Extensible, Scalable, Interoperable, Easy-to-use, Intuitive, User-friendly, Comprehensive, Best-of-breed, World-class – any
to add to the list?
[Pet
peeve: “Most comprehensive”? Impossible!
Something is either comprehensive or it’s not!]
A
solution? Convert these meaningless
buzzwords to concrete, fact-based statements that can be supported by evidence
– where the evidence is the capabilities and processes you demonstrate.
Faux Fictional Names
“In our demo
we’ll be using the following characters for our storyline:
Mary the Manager Andrew the Admin Ulysses the User
Oscar the Occasional User Ernie the Expert User Theodore the Third Party
Sean the Senior Manager Victoria
the VP Alex
from Accounting …”
This tactic
has two drawbacks:
First, one
of our objectives in a demo is to suspend
disbelief – and anything that is obviously fake hurts our cause. As a
result, I don’t recommend fake names such as those above.
Second,
asking the audience to remember the relationship between “Mary” and her job
title has the additional negative impact of consuming the (far too) limited
number of memory slots we humans have available.
Solution? Use the wonderful pronoun (and its
derivatives) “You”:
“So, here you would see the report you need to
manage this process…”
“Your team would then receive this
alert…”
“And here’s
where you and your expert users could configure the system…”
Your
objective is to build a vision in your customers’ minds that they are using the software.
Fabulous Phony Fictional Names
I’ve seen
databases populated with the names of Hollywood stars, movie characters,
comic-book creatures and sports figures.
Don’t. Just don’t – it’s even
worse than above and screams “fake”!
Encrispen!
Our demos
need to be clear, concise and compelling.
To achieve this, we need to focus carefully on both what we show and how
we present it.
Copyright ©
2014 The Second Derivative – All Rights Reserved.
Monday, May 26, 2014
Demos – Showing Too Much: The Curse of the New Capability
Have you ever found yourself saying, “No, sorry, we don’t
have the capability yet…” in demo after demo after demo? That can be painful, particularly when you
know it is something considered important by many of your prospects and
customers.
Interestingly, however, a Great Demo! Workshop participant recently
pointed out that once that capability is finally
implemented, there is a very strong tendency to include it in every subsequent demo, whether it is of
interest to the prospect or not!
The result, of course, can make demos too long and appear
too complicated. The moral? Treat every demo with every customers as a
new situation – and focus on the Specific Capabilities needed by that prospect
(whether or not they include that new capability).
Sunday, May 18, 2014
Logging In As “Admin” – Failure to Suspend Disbelief…
What are we telling our customers when we log in as “Admin”? Given that one of our objectives in a demo is
to “suspend disbelief”, an “Admin” login is telling the customer that the
session won’t be real – it won’t reflect what typical users would see – and anything
that is obviously fake hurts our cause.
Instead of “Admin”, I’d suggest that you choose a more user-oriented,
realistic login (like your own name), whenever possible.
Sunday, May 11, 2014
Difficulties in Demonstrating Toolkit and Toolbox Software
Many organizations don’t describe their offerings as complete
applications, but rather as toolkits or toolboxes – and very often struggle to
find effective ways to demonstrate them and communicate value. Toolkit offerings enable enormous
flexibility, but may demand an ability to visualize what end deliverables might
resonate with specific customers.
Consider the following toolkit list of components:
·
- The intelligent NXT
features 32-bit microprocessor, a large matrix display, 4 input and 3 output
ports, and Bluetooth and USB communication link
·
- Three interactive servo
motors
·
- Four sensors: Ultrasonic
Sensor, 2 Touch Sensors and the all-new Color Sensor
·
- Color Sensor has triple
functionality: distinguishes colors and light settings, and functions as a lamp
·
- Easy-to-use software (PC
and Mac) with icon-based drag-and-drop programming and 16 fun building and
programming challenges
·
- All the elements (612
pieces) you need
·
- Personalize with the
Sound and Icon editors
·
- Share your project files
with your friends with the Pack-N-Go project packager
·
- Batteries not included
What could you build with this?
What solutions does this enable – what problems does it address? Pretty tough!
We can take a lesson from a toy company: Lego.
These folks have taken the concept of “a pile of bricks” – a toolkit– to
a wonderful array of tangible, easy-to-envision deliverables. For example, the toolkit listed above is the components
listing for Lego’s Mindstorms robots: “The NXT generation of buildable,
programmable robots is here!”
And how does
Lego help their customers visualize the end result? They use Illustrations of the (very cool)
robots that the kit can build. Check
them out here: http://shop.lego.com/ByCategory/Product.aspx?p=8547&cn=389&d=292.
These same
ideas can be applied to Vision Generation demos for toolkit and toolbox
software: generate and present Illustrations
of high-probability end-results that your tools can build – and present them as
examples for further exploration and discussion.
Sunday, April 27, 2014
"I Just Wanted To Close My Door..."
You know you are doing an excellent job in Discovery when
your contact says, in response to a question from you, “Just a moment, let me
go close my door…” Clearly, he or she is
about to reveal information that is sensitive – and you have earned sufficient
trust for that information to be shared with you. Delightful!
Monday, April 21, 2014
Remote Demos - Remind Your Customer to Turn Off Email / IM Alerts
I remind vendor teams to turn off their email and IM previews/notifications,
both to avoid embarrassing situations and to look that much more professional –
a Great Demo! Workshop participant recently noted that vendors should suggest
the same to their customers.
In other words, help your
customers avoid distractions and the risk of anything confidential or personal
bleeding through into a web meeting…!
(Don’t you love the horror stories, however…?)
Monday, April 14, 2014
Another Reason to Use a Discovery Document
Doing Discovery while working from a Discovery Document (a
list of questions and/or topics you want to cover) enables you to relax and
focus on listening to (and documenting) your customer’s answers to your
questions – and frees you from trying to remember what questions to ask!
Wednesday, April 9, 2014
[Warning: Shameless Self-Promotion Alert] Great Demo! Public Workshop May 21-22
Our next
Great Demo! Public Workshop is scheduled for May 21-22 in San Jose, California
– Registration and additional information can be found at http://www.eventbrite.com/e/great-demo-workshop-on-may-21-22-2014-registration-8886783609?aff=cohan.
This is a 1.5-Day Workshop, with the first day focusing largely on core Great Demo! concepts and the morning of the second day addressing more advanced topics and techniques. This is an excellent opportunity for individuals, small groups or for teams that have new hires.
Register using the link above or contact me for more information (PCohan@SecondDerivative.com).
This is a 1.5-Day Workshop, with the first day focusing largely on core Great Demo! concepts and the morning of the second day addressing more advanced topics and techniques. This is an excellent opportunity for individuals, small groups or for teams that have new hires.
Register using the link above or contact me for more information (PCohan@SecondDerivative.com).
Monday, March 31, 2014
If Everyone Says Their RFP Win Rates Are Really Bad Then...
It suddenly struck me, if everyone says that their RFP win
rates are really bad, then … who’s winning all those RFPs?
Hmmmm… In addition to
losing to competitors, is it possible that a large percent of RFPs end up as
“No Decision”? I wonder what percent of
RFPs do end up as a “No Decision” result?
Either way, a few observations:
1.
What an incredible waste of resources generally
expended on RFP responses that go no where (which we already knew)!
2. Why aren’t more vendors choosing to NOT
participate or at least “pull back” from RFPs where they know they are “Column Fodder” – and/or the RFPs are written with
ludicrous non-real-world “use cases” that can’t be rationally addressed by ANY
vendor?
3. "Hope” must be a very powerful thing! (In spite of enormous onslaughts of logic and
measurement).
[Corollary – The old joke:
“Doctor, it hurts when I do this…!”
“Then stop doing that…”]
Thursday, March 27, 2014
Remote Demos - Who Else Is In The Room?
For Remote Demos (as well as face-to-face situations) I
strongly recommend that you go around the virtual room and ask three questions,
at the start of any demo meeting:
1.
What is your name?
2.
What is your job title?
3.
What would you like to accomplish in our session
today?
In addition, for Remote Demos, a nice touch is to also ask
of each named participant on the WebEx or GoToMeeting (or other online tool) participants’ list, “Anyone
else in the room with you?” This helps
to reduce the possibility that participants are undiscovered or otherwise
hiding in the virtual corners of the virtual room…!
Thursday, March 20, 2014
Let’s Talk About Value – Uncovering the Delta
To paraphrase Mark Twain’s comment about the weather, everyone talks about value, but very few people actually do something about it. Clearly value is important: Insufficient perception of value is one of the three main reasons that sales opportunities end up as a “No Decision”.
Value vs. Value
“If you use our product, you’ll save time and money…!” offers the salesperson. “Blah blah blah blah blah blah blah…” thinks the customer.
“When we spoke last week, I believe you said you are hoping to recover $250,000 annually as a result of addressing your problem”, says the salesperson… “That’s right”, replies the customer, “that’s the kind of change I need to meet my objectives.”
Which approach is more compelling?
In the first case, the salesperson sounds like he is reciting from a marketing brochure and it clearly doesn’t connect with the customer (sorry, marketing folks…!). In the second example, the salesperson had done sufficient Discovery to uncover the customer’s perception of the value – and the salesperson was simply reviewing that information to make sure it was accurate and had not changed since their last communication.
We can quickly understand three key ideas about value and value communication:
1. Specific numbers are much more compelling than word phrases
2. Customers’ numbers are much more compelling that vendor or industry numbers
3. The lack of sufficient value, as perceived by the customer, is likely to result in a “No Decision”
This last item is semi-obvious, but needs to be called out clearly: There are typically three reasons why a sales opportunity becomes a “No Decision”:
1. The problem is not perceived by the customer as sufficiently important (not seen as a Critical Business Issue)
2. No critical date or compelling event
3. Insufficient perception of value
Any one or more of these items that is lacking or incomplete increases the probability that the sales opportunity will be a “No Decision” result.
Let’s explore “Insufficient perception of value” a bit further...
The Delta
Value can be easily defined as: The difference between the way things are today vs. the way they could be or need to be with a solution in place, expressed in terms of a tangible number.” In Great Demo! methodology, this difference is called the Delta – the tangible expression of the value of making the change, expressed in terms of specific units of time, people or money.
[While value can clearly include both tangible and intangible elements, the tangible elements of value are typically more important in a sales process. Very simply, the customer cannot take intangible aspects of value to the bank, nor (typically) convince a CFO to invest $125K in software without a reasonable ROI analysis.]
Easy Deltas
Many Deltas are easy to uncover and communicate. Consider the following brief portion of a conversation with a head of sales:
You ask, “So tell me, please, where are you with respect to your quota this year?”
He replies, “I’m currently at 72% of quota – $7.2 million out of $10 million – and we’ve got about 45 more days in the quarter… I gotta find a way to get that $2.8 million gap closed!”
You smile, quietly, to yourself – the Delta is $2.8 million – a very compelling number!
Here are a few examples of easy-to-uncover Deltas:
- The difference between the project deadline and the current estimated completion date (the Delta is the number of days that the project will run over)
- The current number of leads converted vs. what was listed in the marketing VP’s quarterly goals (the Delta is the number of leads needed to meet that goal)
- Current bookings vs. quarterly quota for a regional sales director (the Delta is the revenue $$$ needed to meet quota)
The two types of questions to ask in these cases are:
1. Where are you today?
2. Where do you need to be?
Easy Deltas!
Operational Deltas
Many operations-oriented Deltas can be uncovered during Discovery, conversationally. For example, the customer says, “It takes us forever to complete this process today…!”
You respond, “Sorry to hear this – tell me, how many people are involved in the process today?”
“20 folks” is the reply.
“And how often does this process take place?”
“Every week”, says the customer.
“So that’s about 50 times a year”, you comment. “And on average, how much time does each person on the team spend each time this process is done?”
“Hmmmm – I’d say about one and a half days, on average”.
Doing the math:
20 people x 50 times per year x 1.5 days each time = 1500 person days
You offer, “So, it looks like this is currently consuming 1500 days each year of your team’s time. What would you like it to be, or what does it need to be, to feel that you have solved the problem?”
Customer replies, “Good question – if I could just reduce this to a half day per person, I’d be a hero to my team and I know I’d meet my objectives…”
Ah ha! Doing the math again:
Current Situation: 20 people x 50 times per year x 1.5 days each time = 1500 person days
Desired Future 20 people x 50 times per year x 0.5 days each time = 500 person days
Subtracting 500 from 1500 you get (everyone say it together) 1000 person days – that’s the Delta. That’s the difference between the way things are today and the desired future state with a solution in place – and the numbers came from the customer’s lips!
Two notes on this:
1. When you comment that “It is currently consuming 1500 days each year…” many customers will say, “Wow, I had no idea the problem was that big!” What a great way to help move a customer’s perception of problem from simply a Business Issue to realize that it is, in fact, a Critical Business Issue!
2. Customer says, “if I could reduce this to a half day per person…” you may know that your solution could complete the task in 10 minutes – but whose numbers are they? Give yourself the ability to set expectations reasonably and the opportunity to truly delight the customer when they realize (later on) that 10 minutes is all that is needed.
And a moral, coming in the next section…
When to Explore the Delta?
When many sales teams hear a customer admit “pain” in a Discovery conversation, the sales people think, “Ah ha – we have uncovered the problem, so now we can present a solution…!” Truly great sales teams hold back at this point and, instead of offering a solution, ask a few more questions. When you hear any of the following phrases from your customer, consider each as an opportunity to explore the Deltas:
“It takes us forever to get this done today…!”
[How many people, how often, how long? What would you like it to be?]
“We have too many people focused on this…”
[How many people, how often, how long? What would you like it to be?]
“We have considerable project overruns…”
[How many projects, how much overrun? What does it need to be?]
“I can’t get this done with the current staff.”
[How many staff today, how many extra are needed?]
“We do far too many unsuccessful demos…”
[How many people, how many demos, how long…]
The moral?
Any time you hear the customer admit “pain” it represents an opportunity to explore and uncover one or more Deltas for that pain. Don’t let those opportunities escape!
Translating Value to Value
There are three interchangeable expressions of value: Time, People and Money. These are simply three ways of expressing the consumption, redeployment or liberation of resources associated with solving a problem. Generally speaking, people at different levels of an organization perceive value through different filters, aligned with these three parameters:
- High Level (e.g., C-level, SVP, VP): these people are typically most interested in gaining or saving Money. (Which is why a CFO needs to see an ROI analysis before she will agree to move forward with the purchase of $125K of software – intangibles are rarely applicable.)
- Middle Level (Sr. Directors, Directors and Middle Managers): while arguable, these folks are typically concerned with People resources. For example, most middle managers at budget time will say, “I need more people…!”
- Low Level (e.g., staff and individual contributors): “I just want to go home on time…!” Here the team’s concern is Time – a few hours saved so that they can focus on other, unaddressed tasks, for example.
So, when discussing value, we need to articulate it in alignment with the person we are speaking with.
For example, we uncovered the following information in Discovery: Solving the problem will save 20 people 2 hours per person, per week – and the fully burdened cost of each employee is $150K. If we translate for each of the above players, we would communicate:
- High Level: $$ saved or gained annually [20 people x ¼ Day x 50 weeks per year x 150K / ~250 working days per year] = $150K annual savings
- Middle Level: # of People redeployed [20 people x ¼ Day x 50 weeks per year / ~250 working days per year] = 1 FTE that can be redeployed to other, more productive tasks
- Low Level: Time saved = ¼ Day each time the workflow is executed
Who’s Numbers?
Let’s go back to our starting point in this article:
“If you use our product, you’ll save $250,000 a year…” says the vendor to the customer – and the customer looks skeptical, but doesn’t say anything. Ever see this happen in a demo meeting? Very simply, vendors’ numbers are the least believable, in the mind of the customer.
So who’s numbers are most believable? The customer’s numbers, of course. That’s why it is so important to stay in “you” mode when reviewing Discovery information with a customer at the beginning of a demo:
“I believe you said you are looking to save $250,000 a year – is that still correct?” Much stronger!
What if you were unable to get specific numbers from your customer – who’s numbers are next best? Other, similar customers – organizations that are perceived as peers to your target customer. Their numbers are next best and can be very compelling, particularly for Vision Generation demos or during Discovery conversations:
“Other customers that we’ve worked with, who are very similar to what you’ve outlined to us so far, reported that they were able to save $100,000, $200,000 and sometimes as much $300,000 each year…”
Who’s numbers are next on the list, lower down? Industry and analyst numbers – Gartner, for example. The value of these numbers is pretty low, however, since they represent broad swaths of customer types, sizes, and geographies. Not particularly compelling for an individual customer.
And who is at the bottom of the list? (Let’s all say it together) The vendor’s numbers. These are, without question, the least believable by customers:
“We calculate you’ll save $250,000 each year…” The result? Disbelief and skeptical looks.
[Corollary: Customers that present their own Situation Slides that include their own numbers are the most compelling of all!]
Note also that vendor-generated “ROI Calculators” and “Value Calculators” suffer a similar fate. Even though the customer may plug in his own numbers, the calculations have been done by the vendor, which makes the results suspect!
Value Realization
Have you ever made a major software purchase (that required senior management or board-level approval)? What happened the moment you issued that purchase order – and when was that pressure finally released?
That pressure is finally lifted when the person who made the purchase enjoys a value realization event – some kind of small victory where value is recognized – which can be broadcast through the organization to validate that the purchase was indeed worthwhile (and worth value). Note that this is not the point in time where the full ROI of the solution is enjoyed – it is simply one small success.
Consider the following:
- Typical sales people pursue the process through getting the order.
- Good sales teams follow it through the implementation and the “Go Live” date.
- Truly great sales teams track the process all the way through the point in time where the buyer is able to “declare victory” – the point in time where value is realized.
Building this “Transition Vision” with the customer of how the customer will move from their current painful situation through “Go Live” all the way to a Value Realization event is part of doing Discovery – and the vendor that does this well enjoys a distinct competitive advantage over vendors that do not!
That suggests a few additional Discovery questions, such as:
“How will you measure success?”
“How will you measure an initial success?” [This is better phrasing for a “small victory”]
“What key milestone or change are you looking for after deployment?”
(By the way, the point in time where initial value is realized for the customer is also the point in time when the customer becomes a reference – and the astute reader recognizes that vendors should go back to their customers at the point of value realization and collect this information…!)
Back To Twain
So everyone talks about value, but very few people actually do something about it. You and your organization can join the few who uncover tangible expressions of value – right from your customers’ lips – and reduce your “No Decision” numbers…!
Monday, March 17, 2014
ZoomIt – Annotations When Using Lync (and other tools) for Remote Demos
While I generally recommend WebEx and GoToMeeting for Remote
Demos, largely due to their imbedded annotations capabilities, there is now a
viable option for Lync and other packages that lack annotation capabilities
(the ability to draw over the live application that is being
demonstrated): ZoomIt provides some of
these tools, plus the ability to zoom to focus on a specific area of the
screen.
I’ve seen it in action and the annotation tools are
reasonably good, although not as rich as in WebEx or GoToMeeting; zooming can
also be helpful, but be careful not to execute a zoom too fast (or you will
have people reaching from the Dramamine!).
You can find ZoomIt here:
http://technet.microsoft.com/en-us/sysinternals/bb897434.aspx
and it is free to use.
Thursday, March 6, 2014
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]
- About 70% of their teams 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]
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 are (typically) interested or willing to learn.
A couple of ideas to close the gap:
1. Gather your best sales and presales people together (the Group 1 folks) for ½ a day and have them generate Discovery documents and the key process steps that they follow. 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!).
2. Hire a 3rd party to facilitate and teach the above (hint hint).
Sunday, March 2, 2014
Sunday Funnies – Sadly Amusing Video of a Conference Call…
Wednesday, February 26, 2014
Presales Anxiety – Not Knowing All of the Answers…
Many presales people share concerns about being sufficiently
deep with respect to product knowledge (and industry knowledge, and customer
knowledge, and competitor knowledge, and 3rd party knowledge, and systems
knowledge, and VM’s and laptops and tablets and smart-phones and on and on…). A reasonable concern!
Here’s a rescue:
You are not
expected to know the answers to every question in the universe (the answer to the
question about life, the universe and everything is, of course, 42…).
Your objective is to know the answers to just enough questions to be perceived as
competent and credible. Your
responsibility – and the expectation on the part of the customer – is to be the
conduit of answers (of questions that you don’t know how to answer) back to your
customers, later on. Post meeting, your job
is to access the appropriate resources to get those answers and then deliver the
answers back to your customers.
The use of “Parking Lots” in managing questions is an
excellent approach in managing and tracking questions (and answers). Many Great Demo! practitioners use a Word
document to capture questions – and then use strike-through text to show
questions that have been adequately addressed in a session, leaving the
unanswered questions in normal text. This
provides a written record of what was
addressed in a demo meeting or Discover session and what remains open. Very elegant!
Monday, February 17, 2014
Land and Expand Great Demo! Tactics
Here are a number of Great Demo! tactics that folks have
reported have been working particularly well for teams doing “Land and Expand”:
-
Transition Vision and tracking through Value
Realization:
Customers will only expand their licenses once their
original license has been successful, in their eyes. This is certainly not the date the order is placed
(although many sales teams are only concerned with this)! Interestingly, deployment into production use
is also not the key event on this timeline, although very important. Rather, it is the date when the customer is
able to declare a victory (can be a small victory) with some kind of Value
Realization event.
Successful Land and Expand practitioners work with
their customers in Discovery to determine what and when define a Value
Realization event – and then track progress all the way through that date. It is at that point in time that, if
successful, the customer becomes willing and able to help expand the licensing
more broadly.
-
Asking, “Who else might find this useful?” in
Discovery and related pre-expansion questions:
A number of Land and Expand teams have reported that they
include expand-oriented questions in their initial Discovery conversations with
customers. Examples include:
“Who else might find this useful?”
“Which other groups have similar challenges?”
“Who else is impacted by your current problem?”
-
Applying the Menu Approach:
Finally, a large number of Land and Expand practitioners
are singing the praises of the Menu Approach – it is proving a terrific way to
do vision expansion both at the Land and Expand stages:
o Using
the Menu Approach in Discovery to give the customer ideas of where else the
tool(s) can be applied
o In
Lunch-and-Learn sessions
o In
Webinars (and before webinars, in the invitation emails)
o At
customer-specific “trade-shows” (very similar to lunch and learn, but less
structured)
o At
EBC presentations (Executive Briefing Center) – a very good tactic for working
with executives, who may simply want a high-level understanding of what is
possible
In addition, combining the Menu with accompanying Illustrations
for each Menu item is proving very effective at accomplishing crisp, engaging
Vision Generation.
Any other ideas to suggest?
Monday, February 10, 2014
Implementing Methodology Training – How to Move the 40%
In most organizations, participants of any methodology or
skills training tend to cluster into three groups:
-
Group A:
Those who “Get It” – they understand the new concepts and are eager,
comfortable and confident to put the new ideas into practice right away.
-
Group B:
Those who understand the new ideas – but aren’t yet entirely comfortable
to apply things right away. They want to
see success with their peers before they try on their own.
-
Group F:
Those who say something like, “I’ve been selling/doing demos for 20
years and you can’t tell me how to
sell/demo…!”
For many methodology training outcomes, Group A represents about
30% of the total, Group B 40%, and Group F the remaining 30%. What can be done to improve adoption?
Group A – simply needs to feel good about what they are
doing. They need positive feedback on
the changes they’ve made and obstacles removed that might impede their
progress.
Group F – well, voluntary or involuntary attrition will take
care of them…!
Group B – here’s the biggest opportunity! They need to see success stories from their
peers as one mechanism, so that they are more comfortable to try out the new
ideas. They also need to gently (but
firmly!) be pushed to adopt the new habits.
Periodic manager coaching helps with this – but what if there were a way
to enable coaching and guidance to take place with every important interaction?
I’m very pleased to note that FactorLab offers a really
elegant solution called GROW (www.FactorLab.com
– “Making Success a Habit” – what a great line!). After each interaction (or demo, in the case
of Great Demo!), team members simply tap answers to a few quick coaching
questions in an App. While subtle, these
actions help to reinforce the key ideas of a methodology and build desired
habits.
For example, in the case of Great Demo!, the GROW App asks
if the Situation Slide was complete (really key, correct?), did the demo start
with the Illustration, and a few other important ideas.
Participants can use the App to coach themselves and/or ask
for help from their managers – what a delight!
Check it out at www.FactorLab.com.
[Note: in the case of
Great Demo! Workshops, customers report that Group A is often larger than
expected – and Group F can be very small!].
Subscribe to:
Posts (Atom)