During my 22 years of working, I have done both good and bad demos. There are, of course, a number of ways that things can go wrong. However, I have noticed one clear element that is always crucial for success: you have to know your customer’s expectations.
One of the most common mistakes that I have seen is in interpreting the customer’s expectations. Here are my guidelines for avoiding problems:
What about if there are no expectations? Suppose you have asked the customer and they have said, “I/we do not have any expectations, can’t you just show us a general demo on…?” This might turn out to be fine. However, it is most likely that someone has suggested doing a demo just to make things more interesting. The problem is that just throwing in a demo without knowing about expectations can actually damage your credibility. I’ve done some very cool and flashy demos, showing my software at its best, and then someone in the audience has said, “We already have something that does this, and we are very happy with it, thank you.”
In this case, you have wasted everyone’s time. You may even have made yourself appear less credible because of your lack of understanding of their needs.
If you don’t know the customer’s expectations, it may be better NOT to do a demo at all.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning and boost your career prospects.