I worked as an extra on several films and television shows where we were referred to affectionately as “background.” The purpose of background is …
The Surprising Impact of Your Background on Sales Read More »
What’s the Value of Better Demos? A Never Stop Learning! Article What’s in this article for you? 🗸 Your own estimates…! 🗸 The value …
What’s the Value of Better Demos? (A Never Stop Learning! Article) Read More »
We’ll be exploring: Stop Apologizing, Include Problems, Don’t Call It a Demo, Personalize, Customize!
This 30 min. podcast features:
– The experience and epiphany that led to the Great Demo! methodology (a rather provocative story!);
– Some key ideas for a “Perfect Demo Environment”;
– And a discussion of why many demos fail (and how to avoid), plus a few Great Demo! fundamentals, including an good example of “Do the Last Thing First”.
You’ve been asked to put together the content for an automated or recorded demo – where do you start? What should be included?
I’ve blogged about the need for demo data to reflect real-life problems and situations, including the ability to find and surface problems, identify opportunities, and explore exceptions. I can add one more to the list: the ability to identify certain gaps – when things that should be happening aren’t happening…
I was working with a vendor on an example demo and we identified a dashboard to serve as an Illustration (a “Wow!” screen for that use case) – but while the dashboard had all the right data elements, the data itself was uncompelling. There were no problems, gaps, or exceptions exhibited. Everything looked “OK”.
In Great Demo! Workshops we help teams identify the “wow” screens and deliverables in their software (“Illustrations”). One terrific approach is to leverage the well-known “before-and-after” approach…
“Sorry, I don’t have an example like that in our demo system…”
“No, we can’t show that workflow – this is a demo database…”
EN 
ES 