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.
Laura MacLemale wondered <<Are there any statistics available concerning
user preference of a manual vs. online help for software documentation?...
End-users are more likely to be non-techies than techies, of various ages,
who want to find information quickly and easily from a searchable
There may be statistics, but they're not likely to be broadly useful unless
they apply to an audience that is very similar to your actuall audience.
Since you mentioned in the message header that this is beta software, you
have a great opportunity here: collect the statistics yourself by asking
those who request an opportunity to use the beta software what form of
documentation they prefer! This is easy enough to do: simply make indicating
their preferences (or responding to a really short audience analysis survey)
the price of receiving the beta software. This also gives you several months
(i.e., until the end of the beta period) to adjust your doc strategy
correspondingly. If you can establish an ongoing relationship with some of
the users, you can get ongoing feedback on your documentation too.
Anecdotal suggestion: My opinion (personal experience as a beta tester) is
that paper docs work best in the early stages of beta testing, and that
online help can be added to subsequent builds once you learn what subjects
the users want to cover in the online help.