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

WxConfig NG news

This is the first in a series of posts to inform people about what is happening with WxConfig NG.

Transforming the business with CI/CD

On the business level there are huge benefits to be gained from applying CI/CD. This article looks at a few of them and helps you to move your business to the next level, when it comes to software delivery. This is not limited to webMethods Integration Server, but of course it can make a huge positive impact especially on an integration platform. And it is a great vehicle to boost your career.

Deployment options for webMethods Integration

There are several ways to deploy code to webMethods Integration. Let’s look at how things work under the hood, some common pitfalls, and how you can easily automate things. This knowledge will allow you to deliver more value to projects.

Coding vs. career?

Let me share some thoughts on why quite a few people think that coding, which is only the last step in software development, is only for beginners.