Tools & Consulting for the webMethods® platform

Tools & Consulting for the webMethods® platform

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

Update connection details for JDBC adapter on webMethods Integration Server

Connections to a an external database are mostly environment specific. So they must be adjusted whenever a new instance of Integration Server gets deployed. In some situations that can be done manually, in others automation is mandatory. The tool described here can do this for you and is ideal for use in a container scenario.

Performance tuning for webMethods Integration Server

Having spent a lot of time with performance tuning on webMethods Integration Server, I wanted to share some thoughts here. They will equip you with a starting point and the flexibility to go wherever your project takes you.

Understand the problem. Truly.

If you want to solve a problem, you must first understand it. What may sound silly, is actually more nuanced than people often realize. Here is a bit more detail on this and why an outside view is often helpful.

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.

CI/CD and change logs

If you release software multiple times a day, what does that mean for change logs? Here is my approach to convey relevant information to various target groups like end-users or sysadmins.