Whether you need to end the sale, collect end-user feedback, show progress to the customer, or just explain how the product works, you will need to demonstrate your software product sooner or later.
Over the years, I have had the opportunity to perform hundreds of presentations for audiences of all sizes. I also have the opportunity to participate in a demo hosted by others. The following are the top 5 tips for my presentation over the past decade.
Manage your audience expectations
Have you ever seen a movie that everyone is full of, and are completely disappointed to go out? Movie viewers are often disappointed not because the picture is bad, but because it is worse than they expected. It did not meet their expectations.
Similarly, if people show them that they are about to see a demonstration of the finished product, they want it to be essentially flawless, aesthetically pleasing and user friendly. For example, if a web-based application contains misspellings or JavaScript errors, they will not be impressive if they produce this error within a week. However, if they know in advance that you are showing a one-off prototype, then the same audience will be more tolerant. They are happy to provide much-needed feedback to help you get the job done.
Managing the expectations of your audience is critical to a successful presentation. If you want them to stay away from your presentation, make sure you set the right expectations in advance. Honestly. Don't try to exaggerate your presentation. Just sell it and try to overdeliver.
A bad apple plunders the entire group
It only takes one person to mess up the demo. If someone starts to negatively comment on every widget in your app, or if he/she likes to hear his/her own voice and keep interrupting you, then your demo will be a disaster. Make sure these bad apples don't appear in your presentation, it's your job.
Unless you are holding a closed-door presentation, it is difficult to control who will participate. Omitting someone from your invitation list does not guarantee that they will not hear your presentation through verbal communication and will only appear.
Here are some ways to trick a bad apple, instead of attending your demo:
- Create conflicts for those bad apples. Make sure they are busy or better off the office during the presentation.
- Book two separate demos. Invite those who really value the first demo and the second bad guy. Often, each group will present a demonstration of their respectful invitation. When the time for the second demo arrives, please continue shooting, or if you don't have time, just cancel.
I know very well that these two tips sound like an excerpt from the way of Scott Adams' Dilbert and sly, but unless you feel like telling your peers, the superior or the customer don't show up on your presentation, these two options are almost all you left behind. of.
Doing practice running
I attended a demo hosted by the CEO of a local startup last week. After meeting with him at a trade show, he managed to convince me that his company has developed a technology that can solve the needs of my customers. Therefore, I agreed to give him 30 minutes to show his product capabilities.
I don't need 30 minutes to realize that I don't want to do business with him. I only need 30 seconds.
This guy can't even log in to his own web-based app! He sent the demo for the first 10 minutes to find the password.
Always practice on the system you will be using during the actual demo. You may know the app like a palm, but if someone else can access your demo system, who knows what its shape is. They may have deleted the service, upgraded the component, or just like this. The CEO changed the user credentials without notifying you.
Unless you don't mind looking like a fool, be sure to practice on your demo system before showing it to your audience.
Attention to detail
Hundreds of presentations I have conducted over the years have taught me that people are more concerned with the look of the application than how it works. Your software may be the way to solve the problem of hunger in the world, but if someone in your audience notices a spelling mistake in the GUI, he/she will point it out!
Readers are especially distracted by readable content - this is the truth. Process it by carefully looking at the text in the interface and graphics. If you don't have time to view and complete the text, use Lorem Ipsum.
Lorem Ipsum has a more or less normal letter distribution, making it look readable English, but it won't distract your readers. I am now using Lorem Ipsum to develop new prototypes, and when I have time to write actual text that I don't know will not be the subject of the discussion in the next demo. I highly recommend you to do this.
Point out [obvious] error
The software contains errors. It's that simple. Anyone who disagrees with the statement apparently has not worked in the software industry for a long time. While we sometimes strive for flawless products, the reality is that complex systems always contain defects - even if they are usually available.
Practicing before your presentation will allow you to identify and resolve showstoppers and use Lorem Ipsum to handle details that may distract your audience. But what about the other flaws of Murphy's Law?
If there are obvious errors during the demonstration, please point them out!
Your audience is likely to have noticed this error. Any attempt to hide it will make them feel that you are dishonest. Therefore, they will begin to wonder what you are trying to cover up.
Point out the error and explain that you have a solution that confidently states that the fix will be implemented on a specific date and then continue. This sincere behavior will reassure your audience: [a] you have not tried to sweep the carpet; [b] defects will be resolved when the system is deployed.
I don't mean you are looking for bugs during the demo. If you can circumvent them in any way, please do so. But if there is a defect in your presentation, don't predict that it doesn't exist. The only person you are joking is yourself.
in conclusion
You have it. Five tips for a great software demo.
- Manage your audience's expectations
- Make sure bad apples don't break this heap
- Doing exercises
- Pay attention to the details and use Lorem Ipsum
- Point out obvious errors
Do these 5 skills represent all the knowledge I have learned in the hundreds of presentations I have conducted? Absolutely not! Perhaps the hardest part of writing this article is to limit it to 5 prompts. I can easily suggest five other tips, such as [a] control, and [b] always have plan B. But the goal is not to point out all the tips that can help you. Only the top five!
Orignal From: Five tips for a great software demo
No comments:
Post a Comment