For example, most traditional demos start by presenting how a user can set up a particular workflow or task framework, from scratch. “First we turn on this setting, then we build this form, which you can change and customize further; if you want to do this then click that; if you want this other thing then change this parameter here…”, etc. This process often consumes 20, 30 or 40 minutes of a traditional demo, as the demonstrator walks through the many options and choices involved with setting-up the workflow.
By the time the presenter has completed this process, the audience is already exhausted – waaaay too much stuff to remember, waaaay too confusing, and many audience members will have already “checked-out”.
Even worse, traditional demonstrators often never show how the user would actually use the workflow just created – it is assumed, by the vendor, that the user will somehow figure this out on their own (they won’t, typically).
“Daily Use” mode, on the other hand, is where most people spend most of their time. “I just want to see the current report”. In a demo, show how easy it is to run or access that current report (that’s the “Do It!” pathway in Great Demo! methodology). If the customer is interested in modifying the report (or learning how to create it from scratch), let them ask..!
Think about your own work day: How much time do you spend in “Daily Use” mode vs. “Set-up” mode?
[Along similar lines, how many “Day in the Life” demos focus on “Set-up” mode? Seems like a bit of an oxymoron…!]