Call: 0123456789 | Email:

Five tips for the great software demo

Whether you close your sales, collect end-user feedback, make progress with your customer, or simply explain how your product works, you will need to show the software product sooner or later.

Over the years, I've been able to present hundreds of demos for audiences of different sizes. I also had the opportunity to participate in demos organized by others. Here are the five most important ideas I've learned about demos over the last decade.

Listen to Audience Expectations

Have You Ever Wished to Watch a Movie? Often, the cinemas do not because the picture was bad, but rather because it was worse than expected. Does not meet your expectations.

Likewise, when people point to demo-thinking that they will see a finished product, they expect to be practically error-free, aesthetically and user-friendly. You would not be impressed, for example, with a web-based application that contains errors or JavaScript errors if you are impressed as if you were living within a week. However, if you know that you are presenting a disposable prototype, then the same audience will be much lighter. And they are happy to provide many necessary feedback in their work.

Managing audiences' expectations is critical to a successful demo. If you want to keep quiet from your presentation, make sure you have pre-set the right expectations. Be honest with them. Do not try to over-dimension your demo. Just sell it and try to give it more. A Bad Apple stunned the entire team

A demo is lost only by one person. If someone starts to negatively criticize each widget in the application or keeps interrupting you because you hear your own voice, the demo will be a disaster. Your job is to make sure these bad apples do not show up in the show.

Unless you have a closed door presentation, it is very difficult to check who will be participating. Silencing people on the invitation list does not guarantee that the demo will not hear the oral word and will simply be displayed.

Here are some ways to fool the bad apple into the demo: [19659002]

  • Create a scheduling collision with bad apples. Make sure you're busy or even better from the office when the show is done.
  • There are two different demos to be booked. Invite people whose feedback really appreciates the first demo and bad apples for the second. Often, each group appears in the demo for which they were invited. If it's time for the second demo, go ahead and give the best shot, or if you do not have time, simply delete it.

I'm aware that these two tips sound like a detail of Scott Adams Dilbert and The Way Of The Weasel, but if you do not feel comfortable telling your partners, superiors or clients not to show up demo, these two options are pretty much what you're left with.

Do A Practice Run

Last week I attended a show hosted by the local launch manager. Having met her at an exhibition, she was convinced that she had developed a technology that solves the needs of one of my clients. That's why I agreed to give him 30 minutes to showcase his skills.

I did not need 30 minutes to figure out I did not want to do business with her. I only needed 30 seconds.

This guy was unable to log in to his web application either! The first 10 minutes of a demo to search for a password

Always run a system on your system that you will use during the actual demo. You may know the application like your palm, but if someone else has access to your demo system, who knows what form it is. You may have removed features, updated components, or – as this CEO,

If you do not mind being crazy, always practice a practice on the demo system before you show your audience.

Listen to the details

] Over the years, hundreds of demos demonstrated to me that people pay more attention to how the app looks like what it does. Software can be a solution for secular hunger, but if a member of the audience detects a bug in your GUI, you'll find out!

Readers are especially overwhelmed by legible content – and that's a fact. Accept that you thoroughly scan the text and graphics on the interface. If you do not have time to review and finalize the text, use Lorem Ipsum.

Lorem Ipsum has more or less normal letters in letters, so as if it were readable English, it does not bother reading. Now, I'm developing new prototypes with Lorem Ipsum, and I add real text when and only when it's time to write content that I know will not be a subject in the next demo. I strongly advise you to do the same.

Show (obvious) errors

The software contains errors. It's that simple. Anyone who disagrees with this statement has not worked hard in the software industry. While sometimes we strive for defective products, the reality of complex systems always contains errors – even if they are generally available.

Performing a pre-demo exercise will allow you to identify and resolve showstoppers, and Lorem Ipsum will deal with those odd-grainy details that otherwise distract your audience. But what about the other mistakes associated with Murphy's law?

In the event that an obvious error appears during the demo, please show it.

Probably the audience has already noticed the mistake. Any attempt to conceal it gives you the impression that you are not honest. Consequently, you will begin to wonder what you are trying to copy.

Show the bug, explain how it has a solution, feel free to say that the fix will take place at a specific time and move on. This honest attitude reassures your audience that (a) does not try to wipe it under the carpet and (b) resolve the problem when installing the system.

I do not support you going hunting during the bugs demo. If you can play them in any way, please do so. But if an error occurs during the presentation, do not assume it does not exist. The only person you're kidding is the man himself. [19645002] Summary

Here it is. Five Tips for a Great Software Demos.

  • Managing Audience Expectations
  • Make sure bad apples do not ruin the knot
  • Practice
  • Listen to the details and use the Lorem Ipsum
  • Describe the obvious mistakes
  • Do these five tips for all that I learned from the hundreds of demos I left behind? Not at all! The hardest part of this article was probably written down to 5 tips. I simply dropped 5 more tips, such as: (a) checking the situation and (b) always have a plan B but the goal was not to point to any tips that might help. Only the top five!

    Have any Question or Comment?

    Leave a Reply

    Your email address will not be published. Required fields are marked *