Posted: 31 Aug 2016 04:30 AM PDT
The User Guide (aka User Manual) provides the information and instructions needed to set up and use a product. A User Guide includes written and visual information (such as diagrams or screen shots) to assist the user in completing tasks associated with the product (or service), organized along functional or workflow lines.
The User Guide explains how to do something with the product, and often includes the why, and what happens if the task is not done correctly. A well-constructed User Guide provides information geared to the typical user of the product, and provides both procedures and a context for completing the procedures in concise and jargon-free language.
This user guide template is designed to support either a workflow-based or functional approach to the tasks associated with the product. Most technical communicators use this format to document software or hardware. With some tweaking, you can easily use this template to document a whole range of electronic, manufacturing or other hard goods, as well as complex processes or service flows.
Traditional user guides, particularly for software applications, often document every function and option available organized by how the functions were accessed in the user interface. A growing number of technical communicators (technical writers, user assistance specialists, content developers, etc.) subscribe to a user-centered approach to design and documentation, and have begun to move away from exhaustive documentation of every function available. This form of user assistance uses business workflows to organize the information and instructions, so chapters and sections may be organized around performing a set of tasks related to a business role or activity, using the product being documented. In both cases, you should draw on development documentation such as use cases, user stories (Agile) or personas, to determine what features to cover and in what order.
This user guide template includes a set of styles that can support eventual conversion to other formats. It follows the traditional sequential path of a document, rather than the componentized, topic-based style of content creation required for digital media. However, because it's structured to support either functions or workflows, it can serve as a good starting point for technical communicators who are not yet using CCMS or structured authoring tools.
Using the Template:
Do you have other user guide templates that work well for the products you are documenting? Are you in an Agile development environment and have tools for creating user assistance that aligns with Sprints? Feel free to contact us and submit your templates. We'll provide credit to you for assisting the TechWhirl community and contributing to Template Tuesdays.
|You are subscribed to email updates from Tech Writer Today Magazine by TechWhirl. |
To stop receiving these emails, you may unsubscribe now.
|Email delivery powered by Google|
|Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States|