This is a funny video of Chris Pirillo talking about how difficult it is to teach people software.
In software training sessions I've given recently, I've learned that demos can be incredibly boring unless you do them in a certain way. People don't learn much by simply watching you click through everything and explain tabs and buttons. People learn by doing, so you have to get them doing something.
Here's my recipe, recommended by a friend, for delivering more engaging software demos. (This assumes you're in a computer lab).
People like to be challenged with exercises -- that's the key. Even if you haven't shown them how to do the task, that's okay. Let them try to figure it out.
Also, make sure you invite your interaction designer to come and watch people stumble around the application.
What tips and techniques do you use to keep people engaged while giving software demos?
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. In this blog, I write about topics related to technical communication — Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, academics, and more. I'm interested in , API documentation, visual communication, information architecture and findability, and more. If you're a technical writer of any kind (progressional, transitioning, student), be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.