The other day I wrote about lessons for delivering a better software demo. This article ended up being one of the most popular ones in recent times. I have therefore decided to add a few more tips as a solid demo can really make a difference. Likewise a bad software demo can really hurt you and your project. Remember – the first impression is usually the most important one. You therefore have to make sure that you do a great job.
1. Keep it clean
A few weeks ago, I watched a demo. It wasn’t that bad. However, the guy ran it of his own desktop. And what a messy desktop it was. Icons cluttered a photo of him floating in a swimming pool. Oh well. Various apps were open and the person delivering the demo often had a hard time finding the right window. Also, his email program was open. The little Outlook bubbles kept popping up and we could read some of the email subjects (Viagra for sale!). Too bad! This could have been a good demo but the overall impression was anything but positive. You wouldn’t want to sell a dirty car, would you? Before you head out to deliver your next demo make sure to do the following:
Does this look good enough for a customer?
Close all apps that you don’t need
Kill all incoming emails, instant messages or Skype calls
Clean up your desktop
Choose a professional desktop background (the group photo from your bachelor party is probably not the right choice…)
Even easier: run the demo from a clean virtual machine
2. Keep it relevant
Demos need to be short and sweet. Don’t waste time explaining useless stuff. Imagine the car sales person talking about the spare wheel. Not all that exciting, is it? Spending time on irrelevant features can seriously harm you and your message. People might leave thinking your solution is not capable. You won’t believe it – but it’s true. I recently witnessed a person spending 2 minutes showing the audience how to change a password. It was irrelevant and painful to watch (message received: we have basic security). You have to make sure that what you show resonates with your audience and that it has impact. When you prepare for your demo, ask yourself the following questions:
What is the business pain of my audience?
Which features solve that pain?
Does that feature look great on screen?
Is it easy to understand?
Is this something interesting?
3. Fast forward
Have I mentioned that demos ought to be short and sweet? There are times, though, when it’s hard to stick to that idea. There are processes that may have to run, we might have to complete various ‘boring steps’ etc.. Don’t torture your audience with running through the entire process. It is so easy to loose people’s attention today. A good demo is like a river: It keeps flowing. Consider one of the following alternatives:
Record the entire demo or parts of it. Recording the entire script allows you to edit out irrelevant steps. You can also enhance a live demo with some video to show those steps in a quick manner (kind of like a timelapse effect).
Prepare the irrelevant and lengthy steps before the actual demo. This is possible in many case.
Only show the relevant fragments. We don’t always have to show it all. A simple before and after often speaks louder than hundreds of demo minutes
Team up with a colleague. Show some slides during the ‘boring’ parts while your colleague advances the demo
Better software demos
Delivering better software demos does not have to be difficult. Follow some of these ideas to improve. It’s worth it. The greatest dashboard will have a hard time getting accepted if the demos really suck.
As an analytics professional, you often have to show your work to select audiences. This could be a demonstration of a new corporate dashboard at the monthly townhall meeting. It might also be a training class for the operations team or a 1:1 session with the CEO. Regardless of the occasion, you have to make sure that your technical presentation gets the audience excited about your analytics solution. Unfortunately, too many technical presentations go bad. It’s really easy to loose the attention of your audience, if you don’t prepare carefully. The other day I watched a superb technical demo by the famous entrepreneur and photographer Gary Fong. It exhibits a lot of characteristics that you and I should incorporate in our next technical presentation.
The Gary Fong Factor
Take a look at the short video. Gary Fong demonstrates one of his new photo products. Even if you don’t know anything about photography, you will immediately get the idea of his product. Just watch 1-2 minutes.
What’s so special about Gary’s demo. It exhibits a lot of qualities you and I need to incorporate in every technical presentation:
Be enthusiastic: Gary is extremely enthusiastic about his products and it shows. Enthusiasm is contagious. Most photographers want to buy his products after watching one of his demos. However, too many technical presentations are just plain boring. Put yourself in the shoes of your audience: why should you use that analytics solution if your technical leader isn’t excited about it? Show your passion!
Avoid technical language: Notice how simple this short demo is. There are no buzzwords, there is hardly any jargon. Even non-photographers understand his product. Jargon and buzzwords are an excellent way to confuse people. It probably scares the CFO to hear about the configuration of the ODBC connection. Neither does he care about the latest in-memory technology. Make it easy for people to follow you!
Explain the problem: When you deliver a technical presentation, it is critical to explain your audience why they need to change. People don’t like to change. Don’t just jump in and show your shiny technology. Set the background and explain what the problem is that you are trying to combat. Gary does that marvelously. He clearly shows that the current state (i.e. without his products) is problematic. Try to do the same in your next technical presentation.
Show the benefits: Gary doesn’t stop right there. He goes further and stops at certain points to show the benefits of the new approach. He compares the old with the new. He leaves no doubt that the change is worth the effort. This helps the audience make up their mind. Too many demos leave it to the audience to identify the benefits. That’s a risky strategy.
Be quick: Demos are often long and boring. Gary Fong, on the other hand, is quick. He jumps right in and he uses engaging language. There are no slow or boring parts. This is actually one of his longer demos. Most of his video demos run less than 2-3 minutes. This pays off tremendously – you won’t loose your audience.
Practice your technical presentation
Delivering an awesome technical presentation can be extremely rewarding – not only for yourself but also for your audience. Technical excellence of a solution does not automatically translate into enthusiasm by the end users. You have to help them with accepting the new solution. Spend some time to learn and practice these lessons.
Demos are a critical part of every business analytics implementation. There are frequent occasions during any project where we have to show present tools & processes: At the beginning, we might show the new software to our users to educate them. Later on we might want to review a prototype and we need to solicit productive feedback based on the demo. Training sessions require us to teach the new process and tool while also obtaining buy-in from the business. Overall, I would argue that being able to deliver a great demo is a critical skill for every business analytics professional.