One secret of good demos

Here is a short article on what I consider an often overlooked reason for how well software demos go and why you need to prepare hard.

Nobody would argue that preparing a demo for a software product is not important. But one aspect for doing so is often overlooked.

If you struggle with the content side of a demo, you cannot focus on the audience.

That is the sometimes not so obvious reason, why you need to prepare vigorously. Many people only think about how fluent things look like. And of course that is important. But it serves a different purpose, so let’s look a bit deeper.

When giving a demo you want to convey a few things. It is mainly about fit to the customer’s problem, and you being competent, trustworthy, and pleasant to deal with. If you have made your homework and your offering does indeed fit the customer’s problem, the first part is solved already. (Plus the demo must be flawless to bring that across.) The challenge, though, is that often you are not the only vendor who can do that. So it comes to the “personal” side.

I argue that being able to “read” the audience during the presentation is critical. If you don’t need most of your mental energy to execute the demo, you can concentrate on people’s reactions, their body language, and what signals they may send. Being able to react instantly, sends a powerful message about customer centricity.

In particular I remember one meeting with an existing customer. Their CIO mentioned something about performance problems and the use-case seemed similar to something we had solved before. So I simply threw in that we might have something to help. To my surprise this CIO asked my literally, whether I had time to come over the next day. Had I been completely absorbed with the demo, things would likely have developed differently.

Of course your colleagues should also look at the audience and see what they can pick up. But that is no replacement for you doing this. Firstly, they may not be as technical as you and not see what you see (and vice versa of course). Secondly, your proficiency with the product will always be translated into how complicated it is. If all you can do during your demo is “tame” the product, it looks as if said product is difficult to handle. How could it not be, if even the product specialist (=you) has a hard time with it?

There are certainly more points to consider, but this is the one I wanted to send out today. Looking forward to your comments!

If you want me to write about other aspects of this topic, please leave a comment or send an email to info@jahntech.com. The same applies if you want to talk how we at JahnTech can help you with your project.

Share:

Facebook
Twitter
Pinterest
LinkedIn

Leave a Reply

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

On Key

Related Posts

Running MSR outside Service Designer

If you want to run the the webMethods Microservices Runtime that comes with Service Designer separately, you can do that. But the start script for Linux and macOS contains an error. It is easy to fix and here are the details.

Tips for job seekers

The IT job market is not a cozy place right now. To help people find their new job, I put together this list of recommendations. While originally targeted for webMethods, much of it is also applicable for other roles.

webMethods and AS/400

The IBM AS/400 midrange system is a fascinating piece of technology. But it does quite a few things differently than PC-based servers. So be prepared to run into a few challenges when working with it for the first time. Here is my story from a really interesting project.

How to give a presentation

Giving a presentation is vital not only in business but many situations in life. In essence it is about conveying some content in an effective way. Here are a few basic points that will help you.

Unique IDs in programming

A core aspect of almost all IT systems is the ability to identify a single transaction, customer, etc. So you need an ID that is guaranteed to only exist once. With distributed systems and large amounts of data, that is easier said than done.