TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:demos From:Damien Braniff <Damien_Braniff -at- PAC -dot- CO -dot- UK> Date:Tue, 1 Jun 1999 13:19:57 +0100
We use Demoshield to produce the CD front end and the demos of our software
(just been on the course) and it looks as if we can provide everything needed
(if only it wasn't needed yesterday!). The question I have is one of WHAT to
demo. One suggestion has been to provide a walk through of all the most common
features but I'm not convinced. We do a quick user guide that covers all the
common features - key administration, generating reports (we design/manufacture
access control equipment and software) etc. While useful, I feel what we should
be doing first is demos of the not-so-common features that are used once in a
while such as PhotoID (printing personnel photos onto access cards direct from
access database etc) and leave the quick user guide to cover the common features
until they can be done.
