Wednesday, March 3, 2010

Cognitive Dissonance in Demos

How does cognitive dissonance apply to delivering demos? Cognitive dissonance can be defined as an uncomfortable feeling caused by holding two contradictory ideas simultaneously in mind. Cognitive dissonance occurs when a person perceives a logical inconsistency with his/her thoughts.

This happens when one idea implies the opposite of another. In movies, a great example is when a man and woman initially despise each other, but then fall in love (grudgingly at first, of course!).

Does cognitive dissonance occur with software demos? Yes and no. [Sorry, couldn’t resist the example!] It certainly happens when the vendor says, “Easy to use…” but the demo shows the offering as complex and confusing, from the customer’s perspective.

Equally importantly, cognitive dissonance may occur within the vendor’s team – particularly in discussions between sales and presales players, both before and after the demo:

- “Have we done sufficient qualification and discovery?” “ Yes, but… we don’t really know what they need.”
- “Did we address the customer’s key needs?” “Yes, but… we did the same demo we always do.”
- “Did we achieve our objective for the demo?” “Yes, but… the customer didn’t ask very many questions during the demo – and they didn’t say what their next steps are.”

What do we, as the vendor, remember from a demo vs. what the customer remembers – or what we think the customer remembers?

Interestingly, our first impressions of the relative success of a demo are sometimes the harshest. As a few hours pass, or several days, our memory of the demo tends to slant more towards the positive. [The effect intensifies with the number of beers/drinks at the airport bar, not surprisingly…] This suggests that demo teams should debrief and capture, in writing, their impressions of the demo meeting as soon after the meeting as possible:

- What went well?
- What could have done better/differently?
- What expected/unexpected problems appeared?
- What did the customer say? What didn’t they say?
- What action items/follow-up did we promise? Did they promise?

Most people’s brains work to resolve cognitive dissonance, tending towards a filtered set of perceptions. Those perceptions often mask or causatively ignore the initially dissonant items – resulting in over-positive final impressions, inflated forecasts, and shock when the deals don’t close!

Thursday, February 25, 2010

Avoiding Boring

I was learning about a software company’s presales on-boarding process recently and noted a practice that reminded me of a Seth Godin blog post from a few months back…

The on-boarding process included the following steps (among many others) for a newly hired presales person:

1. Watch our current demo.
2. Read the script.
3. Learn it.
4. Prove you know it by presenting the demo in a role-play session [they called this the “Certification Review”].

The candidate presales person lost points for going off-script or incorporating any changes. Seems like a great plan to ensure that the new hire can follow the process dependably, right?

Here’s Seth’s blog post – it may make us rethink this kind of “certification”:

Upside vs. downside

How much of time, staffing and money does your organization spend on creating incredible experiences (vs. avoiding bad outcomes)?

At the hospital, it's probably 5% on the upside (the doctor who puts in the stitches, say) and 95% on the downside (all the avoidance of infection or lawsuits, records to keep, forms to sign). Most of the people you interact with in a hospital aren't there to help you get what you came for (to get better) they're there to help you avoid getting worse. At an avant garde art show, on the other hand, perhaps 95% of the effort goes into creating and presenting shocking ideas, with just 5% devoted to keeping the place warm or avoiding falls and spills as you walk in.

Which is probably as it should be.

But what about you and your organization? As you get bigger and older, are you busy insuring that a bad thing won't happen that might upset your day, or are you aggressively investing in having a remarkable thing happen that will delight or move a customer?

A new restaurant might rely on fresh vegetables and whatever they can get at the market. The bigger, more established fast-food chain starts shipping in processed canned food. One is less reliable with bigger upside, the other—more dependable with less downside.

Here's a rule that's so inevitable that it's almost a law: As an organization grows and succeeds, it sows the seeds of its own demise by getting boring. With more to lose and more people to lose it, meetings and policies become more about avoiding risk than providing joy.

The link for Seth’s post is: http://www.feedblitz.com/t2.asp?/198516/5705813/2863865/http://feedproxy.google.com/~r/typepad/sethsmainblog/~3/gQt5OA4McWw/upside-vs-downside.html.

Tuesday, February 23, 2010

Customers’ Checklist for Purchasing Software

A recent article in the January 2010 edition of Purchasing offered a checklist for customers of contract management software – and is a good general list for a range of software offerings. Items 1 and 2 are particularly interesting and map extremely well to Great Demo! concepts. Here’s the list:

1. Identify your company’s goals, needs and pain points around contract management. Where are the inefficiencies?
2. Identify what reports you would like to have.
3. Check internally across all departments and business units to see if any contract management systems or processes are already in place.
4. Determine how many people will use the contract management software and how much training they will require.
5. Research and narrow down a potential list of providers that meet your needs.
6. Confirm what pricing from providers includes – service, training, etc.
7. Check your internal IT capabilities before finalizing on a product.

Item number 2, “Identify what reports you would like to have”, speaks directly to a core Great Demo! idea – seeking to understand what end deliverables are desired from the software by the customer. Interestingly, this is one of the first times I’ve ever seen “reports” specifically called out.

In traditional demos, reports and reporting would be the last thing demonstrated – and would likely be missed by high-level members of the customer, who may have already left the demo meeting.

With Great Demo!, if reports are key, we would work to understand exactly what reports are desired and what they should look like – and then we’d present these right up front at the beginning of the demo.


The article is entitled, “On the Hunt for Contract Management Software Under $100,000”, in Purchasing from January 2010.

Monday, February 22, 2010

[Warning – Shameless Self-Promotion Alert!] Great Demo! Open Workshop

We are holding an open 1-Day Great Demo! Workshop March 17, 2010 in San Jose, California. The event is co-sponsored by SKMurphy (www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice. You can find an overview, agenda, location and pricing information here: https://www.123signup.com/event?id=jkxxz.

Friday, February 19, 2010

Product Selection Tip – Customers’ Perspective

A recent article providing product selection tips for customers evaluating software offerings included the following advice:

- Compile a list of questions from your entire team to ask vendors during their demos…

Interestingly, the article’s guidance for customers is to ask these questions in the demo meeting – there was no mention of asking these questions beforehand. We’ve done such a good job (poor job, really) of training our customers to expect that we lead with demos (rather than qualification/discovery) that this “tip” expects and anticipates that the demo meeting will be the first substantive opportunity for a discussion! (OMG!).

This immediately suggests three tactics:

1. Prior to the demo meeting, contact the customer to ask for the list of questions they may have put together. Use this list as a starting point to guide your qualification/discovery discussions.

2. Use the list of questions as a post-demo review tool: did we address all of their issues? What open topics still need to be addressed?

3. Save and make the list of questions available for the balance of your team, for future sessions with other customers in similar situations.

Tuesday, February 16, 2010

Demo Memory – Like Muscle Memory

Getting into a groove can be a Good Thing – in that we get comfortable and proficient following a specific pathway…

Getting into a rut may be a Bad Thing – in that we are too comfortable and follow the same pathway over and over again..!

Thursday, February 11, 2010

The Terrible Tabs Death March…

I sat in on a demo recently where the presenter navigated to a page with about 10 tabs displayed across the screen and then proceeded to march through each tab, one by one, in detail.

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

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

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

Monday, February 8, 2010

Best Practices for Network Connections for Face-to-Face Demos

I’ve watched a number of vendors struggle with trying to connect to their network/software applications when at customer sites. Typically, they are trying to run through both the customer’s network/firewall as well as their own.

I’ve seen specific cases (many!) where the first 20 minutes of an on-site demo meeting was consumed by the vendor technical person (e.g., SC) working with the customer’s IT staff to figure out how to connect – and fail to connect!

Often, running with virtual machines adds to the challenge. “OK, just reboot now and try it again…” – and it takes 20 minutes to reboot, only to find that you still can’t connect…

Here are current best practices for on-site demos where you need access to your own network:

- Best: Broadband (modem) connection (fastest, most modern version you can find…). This keeps things under your control, with the exception of the possibility of poor phone coverage. This most likely will be the best solution about 95% of the time. You can always ask to move conference rooms, if possible/necessary.

- Next best: Connecting through their network. This is the best choice with respect to performance, typically, but is “fraught with hazard” (who says “fraught” anymore?) Likely this gets harder and harder as IT people seek to make their networks more secure – you’ve got two network security systems to worry about (theirs and yours). It also typically requires IT help to get things set up. I’d suggest this is you are doing a long demo meeting on site (2 hours or more), where the investment in IT time is worthwhile.

- Next next best: Deliver a Remote Demo with one of your people present (e.g., you go to the site and have a separate technical person present the demo over WebEx/GoToMeeting/Live Meeting, while you serve as the “active conduit” to manage the meeting. Again, there may be some network issues, but typically much less than running “live” through their network.

Backup: PowerPoint slides and/or recordings are the final line of defense.

Other ideas?

Thursday, February 4, 2010

Live Meeting: Another Task for Your Meeting Manager

I’ve noted that the best practice for Remote Demos is to have a representative at the customer site to be your active conduit of information back to you delivering the demo remotely – to be your “eyes” on location. This person (the “Meeting Manager”) can be a representative from your company (best) or your champion/sponsor (next best) or designee (next next best).

For Remote Demos done via Microsoft Live meeting, there are often problems with screen resolution that result in the audience computer having scrolls bars present, that must often be moved to be able to see the important parts of the screen. In this case, assign your “Meeting Manager” the task to adjust the scroll bars on the customer side of the meeting, to make sure that the customer is seeing what you want them to see…!

Tuesday, February 2, 2010

Over 10,000 Great Demo! Copies Purchased

Sometime during the last few months Great Demo! passed the 10,000 copies purchased mark (wow!) – this doesn’t include copies resold on eBay and elsewhere, and copies that get passed around within teams…

Many thanks to all of you!

[Shameless self-promotion time: if you don’t already have a copy of your own, it is available on Amazon.com (US, UK, Canada, France, Germany, Japan), BarnesandNoble.com, or directly from me at The Second Derivative. I can also provide discounts on volume purchases and can ship right away.]

Sunday, January 31, 2010

Summarize After Answering a Question to Re-engage Your Audience

After answering a question, in the midst of a demo, most presenters simply turn back to their flow and pick up where they left off. This makes sense to the presenter (who knows the demo and the product), but it is very likely that the audience has lost track…

Instead, after answering a question, do a quick recap of the steps you’d just completed (before the question) to re-set and re-engage your audience. Works wonderfully!

Tuesday, January 26, 2010

We Are Programmed To Forget - And Its Impact on Our Demos

Indeed we are – and consider the impact this has on traditional software demos!

Imagine you are driving home from work or on an errand… What do you remember about the cars and signs you see, the road-side debris, people, buildings and the roads you pass? How much of that information is retained?

Very little is actually remembered about what you saw along your way. Our brains are continuously evaluating what we see and hear as we move through our day – and continuously discarding anything that is not considered important, threatening, or particularly interesting.

What don’t we remember? Everything that is typical, expected, or normal.

What do we remember? Remarkable events, problems, danger and close calls, humor (things that made us laugh), anger (things that made us mad) and other emotional experiences (things that caused a strong emotional reaction).


What’s Forgotten?

How does this impact our demos and what audiences remember? In an hour-long traditional demo, we shouldn’t expect our audiences to remember very much:

- They won’t remember long sequences of features, functions and options…

- They won’t remember complex workflows, loops and multiple “if” cases…

- They won’t remember the confusing interdependencies of configuration choices, multiple roles, and intertwined pathways…


What’s Remembered?

What will audiences recall from traditional demos? The beginning, the end, and the ugly:

- They will remember the first and last few things that are shown…

- They will remember the bugs, crashes, ignored or poorly handled questions, the amusing distractions from other audience members, and particularly stunning fumbling for features.

- And they will remember an overall impression of the demo – as being boring, confusing, and complicated.

They may also remember the absence of capabilities they were looking for – in many cases, even if these capabilities were, in fact, presented!

What can we do to improve our success rates?


Memory Management

Here are three simple (yet very effective!) tactics to help your customers retain the key ideas you want them to remember:

[Shall we all say it together? “Do the Last Thing First!”] When presented with a long list of ideas, people remember the first few items very well and the last few items moderately well – and the material in between generally gets lost. This is the “Attention-Retention” principle (also known as the Serial Positioning Effect).

Take advantage of this and start your demos with the most compelling, most interesting deliverables for each audience. If the audience remembers nothing else, they will remember the most important part of your demo – the payoff, the visual evidence of the solution to their problem.

Along similar lines, people absorb and retain information best when it is presented in discrete “chunks”, as opposed to a long linear flow. Organize and present your demos accordingly – in consumable components – and use a roadmap to help manage the delivery of your component chunks.

Summarize…! Adults learn by repetition – so when you complete a demo segment, summarize. Repeat, verbally, what you just showed them. If you are face-to-face, you should see your audience nodding their heads – this means they have heard you, they understand, and they have a higher likelihood of remembering.

How can you tell if your audience will remember the key points? You’ll see them making notes – writing things down.

We combat our “programming-to-forget” by making notes of the major ideas, issues and questions we want to remember. For software demos, if you are doing well, you’ll see your audience making notes about key capabilities and writing comments about what they find particularly interesting.

I Really Remember…

What else can we do to help audiences remember our demos? Anything that is perceived as remarkable is memorable – for example:

- A unique presentation of a solution to a problem – “Wow! – They showed us the key reports that we need to produce right up front, at the beginning of their demo. And they showed generating those reports in 3 mouse clicks, as opposed to what is taking us a week to do today…!”

- Engage the audience – “That was so cool – they had John drive a portion of their demo, and John still types in all caps…!”

- Develop concepts or materials ad hoc – “It was great when they built a new form for us, first on a whiteboard and then right in their software…!”

- Make it a two-way conversation – “We were really engaged – asking questions and even coming up with new ideas for our process…”

- Finish the demo early – “Wow – they finished early and I had time to get some real work done…!”

- Be humorous, but effective – “It was funny when the sales guy said, ‘The bad news is I have a 60 slide corporate overview presentation to show – the good news is that I’m not going to inflict it on you…!’”

- Use props – “Do you remember when their technical guy came into the room with this huge stack of documents and folders spilling all over the place? Looked like our day-to-day lives, to me…!”

- Run their examples – “That was really nice – we rarely take something of value away from a demo…”

Humans are, by nature, programmed to forget. Causatively forgetting the unimportant, the uninteresting and the unremarkable is how our brains are able to handle the enormous volume of information we encounter every day.

Make your demos memorable by Doing the Last Thing First, organizing your delivery in consumable components, and by summarizing – as basics. Make your demos truly unforgettable by doing the unexpected, the noteworthy, and the remarkable.

Thursday, January 21, 2010

Presales On-boarding Training Novel Concept

Here’s a terrific idea for training new presales staff: Teach them your discovery/qualification process before teaching how to demo your software… Why consider this approach?

- It models the principle of doing discovery/qualification before presenting your solutions.
- It teaches new hires how to put together summaries of customer-specific situations (“Situation Slides”).
- It breaks the tradition of “Here’s our standard demo script… Learn it!”

This method also helps put your software in context:
- What specific customer problems does it solve?
- What specific capabilities are needed to solve these problems?
- What customer job titles are involved, and in what specific way?

If anyone (else) is already doing this, please let me know how it has been working for you…

Wednesday, January 13, 2010

“Controlled Vocabulary”

Years ago, a colleague introduced me to the concept of “Controlled” vs. “Uncontrolled Vocabulary”. Watching a series of demos recently reminded me of the importance of this concept. Very simply, with Controlled Vocabulary, everyone in the meeting has a mutual understanding of all words and phrases used in a presentation or demo. Uncontrolled Vocabulary are words and phrases that are introduced by the vendor that are NOT understood by the customer.

Uncontrolled Vocabulary includes (but is not limited to!) words and phrases such as:
- Company-specific acronyms
- Company-specific terms
- Product feature names

Don’t use these in demos and presentations if you want to be most effective in your communications!

Friday, January 8, 2010

Warning – Shameless Self-Promotion Alert! Great Demo! Open Workshop

We are holding an open 1-Day Great Demo! Workshop March 17, 2010 in San Jose, California. The event is co-sponsored by SKMurphy (www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice. Contact me for an overview, agenda and pricing information at PCohan@SecondDerivative.com.

Wednesday, January 6, 2010

Remote Demos – Don't Forget to Disconnect!

While this is certainly obvious, I’m occasionally amused – and sometimes astonished – by vendors who forget to close their Remote Demo meetings (e.g., via WebEx, GoToMeeting, Adobe Connect, etc.) and corresponding phone connections.

Amused – when a vendor forgets to close the session(s) and the collaboration tool window remains open/active.

Astonished – when a vendor forgets and, still sharing his desktop, starts to write email messages about the results of the web meeting! As a customer, it can be very interesting to see how the sales rep describes what a “great” meeting it was and how the “business is in the bag…!” I’ve heard the same with conference calls that remain open and active after the meeting has completed.

Monday, January 4, 2010

Understanding Before Proposing Solutions

We all know that we need to gain a sufficient understanding of our customers’ needs and specific situations before proposing solutions – and before presenting most demos. Here’s an additional reason to do this:

Miller Heiman, Inc. reports in their Executive Summary of their 2009 Sales Best Practice Study that 93% of “World Class” vendors vs. 50% of “All” vendors do “Clearly understand our customers’ issues before we propose a solution”. “World Class” organizations achieved stronger results in five areas measured:

- Average account billing
- Sales force quota attainment
- Number of qualified opportunities/leads
- Customer retention
- Forecast accuracy

Not surprising…!

Wednesday, December 30, 2009

“Tentative”

Here’s another option when responding to sales’ calendar requests for demo resources: Choose “Tentative”. You can leave your response as “Tentative” pending receiving sufficient pre-demo qualification/discovery information.

Monday, December 28, 2009

Remote Demos – Consider Using Two Computers

Consider hosting your Remote Demo sessions (e.g., using WebEx, GoToMeeting, Adobe Connect, etc.) on separate computer – not the one you are using for the demo. This can help with bugs, crashes, managing the meeting, etc. It also makes it safer when using IM between vendor participants and presenters (sales person, presales, etc.)!

Friday, December 18, 2009

“A Link and a Login”

Software has always been an “intangible”, making it difficult to understand the value of what the software offers – and it only gets harder.

In the mainframe era, a new software customer would expect to receive a box containing tapes and administrator manuals, plus several boxes with user manuals, quick start guides, and even keyboard templates (to help remember the arcane keyboard commands). Additionally, one might expect several people from the vendor to arrive on-site to perform the installation, migrate data, implement customization, and then train administrators and users.

When PC software became the norm, the physical deliverable might include shrink-wrapped boxes of floppy disks, installation and quick guides, manuals, etc. for each user in the customer’s organization. As users, our shelves often held more boxes of software than books!

Today, the “deliverable” for hosted, on-demand, and SaaS offerings may simply be a link and a login. No boxes, no installation, no physical manuals; everything is online and accessed via a link and a login. Talk about intangible!

This makes it harder than ever for vendors to communicate the value of the software – and why it is so important to uncover customer perceptions of value during qualification and discovery, as expressed in measurable numbers (time, people, money), and present that value during demos.

Tuesday, December 15, 2009

‘Twas the Night Before The Big Demo

‘Twas the Night Before The Big Demo
(with apologies to Clement Clarke Moore)

‘Twas the night ‘fore the demo and all through the house
Not a creature was stirring, ‘cept my SC and his mouse;
I’d proposed a big licensing deal with great care
In hopes a big order soon would be there;

Management was restless and not in their beds
As visions of bonuses danced in their heads;
And my VP with his forecast and me with my own,
Had just started a long EOQ roam,

When out from my mobile there came a great ring-tone,
I sprang from my chair to answer my phone,
What could it be? Was it good news or no?
A last-minute order? A contract? PO?

Greetings, said my assistant, who spoke on the line,
It was someone to see me, offering help at this time!
Who could it be at this late eleventh-hour,
To make the deal sweet and avoid something sour?

Away to the door I flew in a flash,
And swept it open in my quest for fast cash,
When who to my wondering eyes should appear,
The DemoGuru! And standing so near!

He came in my office and, while dusting off snow,
Said, “I have some news that you’ll want to know.”
He drew up a chair and asked for some tea,
And said to my VP, SC and to me:

“Your deal is in trouble and I’ll tell you now,
Your demo’s confusing, complex and lacks ‘Wow!’
It’s riddled with features and functions and more,
And too many cool things, mouse clicks galore,

Don’t flog them with features and other neat stuff,
Stick with the substance, stay away from the fluff,
The more that you show is not always nice,
Customers may say, ‘Please lower the price!’

The Buzzword-Compliant Vocabulary list,
Are words, I’m afraid, that are better-off missed,
Not Flexible, nor Powerful, nor Easy-to-Use,
Not Robust, nor Seamlessly Integrated abuse,

And no corporate overview, please don’t do that,
After ten minutes they’re grabbing their hats,
Present as a team, so if things get hairy,
Sales folks aren’t lost in the back with Blackberry.

Your customer’s queued and ready to go,
They love the vision you’ve built with them so
They want Technical Proof in the demo you’ve planned,
Just the key capabilities, everything else banned.”

“But how can we do this?” I heard myself cry,
“We’re victims of momentum, we’re nervous to try,
Another approach, a new way to go,
We have to admit we’re just a bit slow!”

“Do the Last Thing First!” he said with a smile,
“Then peel back the layers, and Do It with style,
Peel it back in accord with their interest,
Stay focused and execute, and you’ll find it best,

Your customer’s Situation is a great way to intro,
Their Reasons and needs, from CBI flow,
Review these and check – is this still the case?
Are we aligned or are we off-base?

Start with the end, that big pay-off piece,
Illustrate and describe, those are the keys!
Capture their interest, compel their attention,
Make sure it aligns with their mode of consumption.

When it clicks and they’re hooked, they’ll then ask for more,
There’s absolutely no way that they’ll head for the door,
They’ll say, “Please show us, prove that it’s so,
Show us the rest, please do demo.”

Then Do It, just Do It, with no extra clicks,
To return to that Illustrative image that sticks,
Make it simple, make it fast, make it easy and clear,
Then they will realize they’ve nothing to fear,

Encourage their questions, most are not new,
Good ones and Great ones and Stupid ones too,
Treat Hostiles with courtesy, use your Not Now List so
Those mean, nasty folks can’t damage your flow,

Peel back the layers, Do It Again,
Show only what’s needed, put nothing else in,
Let them drive the demo, let them think they’re in charge,
While their Vision Solution you work to enlarge!

Summarize, summarize, tell them again,
‘Cause adults do learn by repetition,
And when you show a key take-away screen,
Leave it up, let it linger, so they’ll know what they’ve seen!

“I get it – I’ll do it!” exclaimed my SC,
“This is all so obvious, it’s way clear to me!”
And he sprang into action, his mouse flew like lightening,
(Frankly, his speed was a little bit frightening!)

And with that the DemoGuru smiled and he said,
“Your way is now clear, put that baby to bed,
Your deal’s now on track, your order secure,
You’ll make your numbers at the end of the year,
Then he strode from my office in a blink of a pun,
Turned ‘round and he said, “My job here is done,”
Ere he drove out of sight, I did hear him say,
“Great Demo! to all and to all a Great Day!”

Friday, December 11, 2009

Remote Demos – Three Audio Considerations

[Many thanks to The Webinar Blog for these ideas]

If they can’t hear you, it is all over even before you begin…! Here are a few ideas specifically regarding the audio for Remote Demos:

International Call-in Numbers: A few U.S. collaboration software providers still list “800” numbers as the sole connection possibility – make sure that non-“800” numbers are also provided, so that participants outside the U.S. can call in.

“Barge Tones”: Have you ever been participating in a webinar and noted the annoying “bonnnnng” sounds announcing the “arrival” and “departure” of participants? Even worse, an automated voice often announces, “John Doe has joined the call…” During set up, before a webinar, find out if these alerts can be turned off!

Muzak madness: Along the same lines, who hasn’t heard “muzak” playing from a participant who has put the call on “hold”? During set up, learn how to mute individual participants or the entire audience, if possible.

There are other guidelines at The Webinar Blog if you are interested in exploring them…

Wednesday, December 9, 2009

Implementation Strategies – For Great Demo! and Other Methodologies

When presenting new ideas to teams that may include sales, presales and marketing, there are some strategies that work better than others, with respect to the degree of implementation and ongoing improvement of the overall team’s level of practice.

Many organizations simply ask for a Workshop as an “event”, where methodology information is presented and practiced in role-play exercises. Without any follow-up or coaching on the part of management, these situations yield the lowest levels of implementation – not surprising.

Along similar lines, an event that simply includes presales participants – and no sales people – may result in some levels of frustration on the part of the presales team, as they have to “train” and coach their sales counterparts on the new ideas and processes. With the support of good presales management, this can still be a very successful plan.

Better, however, is to include sales (and marketing) folks in a Workshop with their presales peers, so that everyone is exposed at the same time. Role-play exercises reinforce the team-play aspects, and the team overall is clear about the specific roles for each job title.

Coaching, by management, is often key to seeing new ideas take hold. This means, implicitly, that managers need to participate in the Workshop, so that they understand what they are coaching!

Other activities that help with implementation success include:

- Weekly calls with the presales team to present success stories and discuss new challenges
- Harvesting and communicating success stories
- Capturing and sharing good example Situation Slides and corresponding Illustrations
- Holding period “Demo Days” so the team can see one another’s demos, props, tricks, etc.
- Creating Mentors who can coach and train new (and existing) team members.

One non-obvious strategy that yields very high levels of successful implementation is to invite managers to a pre-Workshop Coaching Seminar. This event exposes managers to the key ideas – and provides specific guidance and tactics on coaching staff and team members.

This is a starter list – other ideas and experiences solicited…!

Monday, December 7, 2009

Performance Challenges - (Not) Waiting For the Hourglass…

You’ve just started a process that will take several seconds to complete, in your demo, and now the audience’s attention is riveted watching the hourglass cursor do its thing, emphasizing the delay.

A recent Great Demo! Workshop participant noted that moving the mouse to the far right of your screen (or bottom-right corner) hides the cursor from view, reducing the impact of what might be perceived as less-than-optimal performance!

Thursday, December 3, 2009

Fuze – Another Entry in the Web Collaboration Marketplace

Fuze Box, Inc. (www.Fuzebox.com) has announced three offerings to enable presentation and sharing of information over the web:

- Fuze Meeting – (www.fuzemeeting.com)
- Fuze Messenger – integrates multiple IM accounts into a single app
- Fuze Movie – ability to share, view and annotate video, audio and pictures.

Unfortunately, Fuze Meeting does not support annotation over a live application. This continues to leave GoToMeeting, WebEx and Adobe Connect as the leading packages suitable for Remote Demos.