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.
<<To eliminate some weight of the manual and work effort, we're looking into creating a true "user manual" or task-oriented manual (with little reference), and then put the reference material in our online Help (such as description of windows, options, and so on).>>
I agree with Jane. You should reverse yourself about 180 degrees on the reference material online and task-oriented material offline. Users are interested in performing the tasks for their job, put that information where they can get it easily and painlessly.
If you want to see good examples of task-oriented help, look to Microsoft (oh boy, I can't belive I said this) ;-) Most often referred to as "How To" help, task-oriented help can provide a user with the information needed to do their job, whether it be writing a letter or performing a mail merge.
A dead giveaway to task-oriented help is that it's title begins with an action verb, e.g., perform, determine, create, change, move, etc. Now granted, although it begins with an action verb, what follows may not be true task-oriented help <grin>
Task oriented help is time consuming to produce if you do not know much about your users. You need to find out what they use the software for and then identify the steps they take to do the tasks. Often, building 80% of the tasks into help on a new system is a good start. Master users of the software often appreciate help for the 20% of tasks that are infrequently performed or very complex. This task-oriented help is much easier to put together once the software has been in use and those complex tasks identified.
The ideas from Tony Markatos are great. Follow his instruction and you will be able to deliver useful task-oriented help.