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.
My user manuals have a combination of both tasks and screens. Since I don't
ever meet my audience, I want my manuals to meet the needs of both user
types. Some people are visual and want to see the screen while others do
well with instructions. I also use tables to give a quick overview of
functionality of different elements of our software.
This works for me and the company I work for.
Peggy
----- Original Message -----
From: "Samir Sachdeva (STEAG)" <s -dot- sachdeva -at- steagindia -dot- in>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Thursday, January 18, 2007 12:28 AM
Subject: Approach for user manual
Hi All,
Thanks for all your responses. They have helped me a lot. As far as I have
understood, a task-based approach is more suitable for applications like
Microsoft Word, where the tasks the user has to do can be described in their
order of decreasing importance. On the other hand, a screen-based approach
would be more suitable for web applications, where the user goes from one
screen to the next in a logical sequence.
Any takes on this?
Samir Sachdeva
www.t-t-t-online.com
-----------------------------------------------
Steag Encotec (India) Pvt Ltd, New Delhi, India
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team
authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList