The purpose of this manual is to guide instructional designers on how to create effective training manuals. The benefit of learning this information is to create professional - looking educational tools that will serve your clients well. It is important to implement the information within this manual in order move your clients to optimal levels of.

Prices listed are manufacturer suggested retail prices and may vary by retail location. Acer iconia b3 a30 user manual.

Purpose and Principles of this Policy Manual (6.2) PURPOSE It is the purpose of this manual to establish and maintain a uniform system for managing personnel matters; to comply with applicable employment laws; and to provide for the standards, terms and conditions of employment with Tennessee State University. The User Manual contains all essential information for the user to make full use of the information system. This manual includes a description of the system functions and capabilities, contingencies and alternate modes of operation, and step-by-step procedures for system access and use. User Manual (v1.0) Page 1 of 2 This document is 508 Compliant Insert additional appropriate disclaimer(s) Document Purpose This Practices Guide is a brief document that provides an overview describing the best practices, activities, attributes, and related templates, tools, information, and key terminology of industry-leading. The main purpose of your business operations manual, however, is not only to describe how each aspect of your company procedures and operations must be executed. It must set the mainframe of rules and regulations that will ensure consistency among all franchise units and it will help your franchise to reach its full growth potential and success.

In previous blog posts, we’ve written a lot about the courses available in Deque University, but did you know Deque U is also the home of our product documentation? These include comprehensive reference materials about our products, including user guides, quick reference guides, and automated rule information and remediation advice. In fact, this user documentation often serves as the basis of much of the product training we do in order to ensure that everyone who uses our products is using them efficiently. In this post, we’re going to cover the importance of sections like the product resources side of Deque University. This part of Deque hasn’t been highlighted as much as our course offering, but it’s no less relevant. That’s because the right product training is a huge part of cultivating self-sufficiency in web accessibility.

And this is one of the main reasons we created Deque University in the first place – to empower organizations with the right tools and training in order to create a more accessible web. But high quality user documentation is important for all organizations, no matter what their purpose. You’ll find out why in this post.

Documentation as Maturity Indicator

Here’s a little known fact: one often-overlooked indicator of a software company’s maturity is the quality of their product documentation. Software product companies are typically founded by technical people who understandably place importance on engineering roles like UX design and web development. When so much importance is placed on these departments, sometimes user documentation gets left by the wayside. A great example of this is Google, which somewhat famously evolved from being a flat organization ruled by engineers to one that realized through their survey data the importance of other specialist roles such as having technical communicators focusing on developing user assistance materials for their products. Similarly, the quality of the user documentation and other resources can be good indicators of the maturity of a company.On software product proposal review teams, functional business managers may care about features and price, while technical and IT managers might be more focused on security and maintenance.

But what about r user support? When researching and comparing software vendors, organizations that make this an important part of their review process benefit from demanding user documentation samples and demos during the Request for Information (RFI) phase of the proposal consideration process. When documentation is an afterthought, business award decisions can become big, costly regrets.

Documentation vs. Training: What’s the Difference?

As I explained in the first paragraph, Deque’s product training wouldn’t exist without its user documentation. In fact, the user documentation is the primary source from which all course materials are created. Some of the
common ways in which Deque’s training materials may differ from the product user guides are:

Table 1: Documentation vs. Training
Documentation	Training
Informing by providing access to knowledge information. The work is usually a part of product development or operations. Covers all functionality for all end user roles.	Helping people learn and develop skills. The work is usually a part of HR or professional services. Covers a subset of functionality for specific end user roles.

Table 2: Context
Documentation	Training
The context is “I’m working” – give me what I need so I can do my job. This is also known as performance support.	The context is “learning and building skills” – give me concepts, demonstrations, examples, scenarios, practice, and assessments.

Table 3: Content
Documentation	Training
Sequenced according to UI and procedures, includes everything, has more detail, does not have redundancy, no practice material.	Sequenced for learning, does not include everything, has redundancy and repetition, practice and interaction is expected.

Table 4: Goals
Documentation	Training
Focused on “providing answers at a moment of need”	Focused on getting learning to “transfer” and to “stick”

Table 5: Sharing
Documentation	Training
Documentation can be “re-purposed” as support materials during and after training, including reference materials, help systems, knowledge base articles.	Training materials such as recorded demonstrations and tutorial videos can be published within online help to become part of a “documentation set”.

Table 6: Jargon
Documentation	Training
User	Learner, student, participant
Look-up, explain, inform, trouble-shoot	Learning and job transfer
User Guides	Course materials (student guide, labs, workbooks, handouts, slides, quizzes)
Help systems	Performance support
Quick reference cards	Job aids
Usability testing	Evaluation
Architect information	Design learning experience
Process: Plan, design, develop, produce, evaluate (PDDPE)	Process: Analyze, design, develop, implement, evaluate (ADDIE)

Documentation vs. Help: What Do You Consider “Helpful”?

Have you ever clicked on a Help link or button in the user interface of a software application and been disappointed with what appears next?

Help as Contact Us Page: Some software vendors think “help” is page in the application that displays contact information for the Help Desk. You have to either call a number (during their business hours), send an email, or fill out an online form…and either way, have to wait for whatever the typical response time is. This is not helpful “at the time of need,” and offers no ability to self-educate.
Help as FAQ Page: Others think “help” should be a single page of FAQs – sometimes categorized, sometimes not. Sometimes searchable, sometimes not. Sometimes brainstormed before ever actually being frequently-asked. Sometimes maintained, sometimes not. Sometimes they’re not even alphabetized! For some software vendors, their approach to helping users is all about troubleshooting.
Comprehensive Online Help: Deque’s approach to user assistance and learning materials includes searchable, online user guides in Deque University that are linked to from the software products themselves. Learning more is always one handy click away, offered at the place of need. They include process, task and reference materials covering every facet of how to use the products.

The User Interface Argument

Can a software application’s user interface be so well-designed, intuitive, and easy to use that it doesn’t require user documentation? The short answer is No, of course not. No matter how great a user interface is, it’s been argued that no software product can be considered “usable” without accompanying user documentation. High-quality user documentation for a software product helps ensure customer satisfaction, and an improved customer support experience is what ultimately leads to retention, recommendation, and referral. So although at Deque we place a high amount of importance on design, we also invest considerably in product documentation.

Knowledge Is Power

Software companies who last in niche markets offer much more than just FAQs as their product documentation. They’ll be quick to supply you with samples of their printable materials (user manuals, quick reference guides, etc.), and they’ll be quick to offer demonstrations of their online materials (searchable help systems, knowledge bases, self-paced e-learning courses, etc.). We’re always happy to share these important aspects of our products with you. You expect quality product documentation from the large, well-known enterprise software companies. They can spoil you and cause disappointment when comparing with smaller companies. On the other hand, it can be pleasantly surprising when smaller companies focus on continuously improving the quality of their user documentation. Even the smallest improvements in documentation quality have been found to have a powerful impact on overall user acceptance and software product satisfaction. When the learning is built into the product, the depth of knowledge is available to all users, all the time. The ability to ramp up your collective expertise as an organization is partly based on the ability to self-educate. Today’s younger generation of tech workers are used to having the capability of internet search from personal mobile devices 24/7, which has contributed to their current knowledge and skillsets due to online documentation and even MOOCs. They are used to being able to self-educate quickly to get their work done. This means that they’ll end up being more effective in completing their tasks, and that’s due to the type of resources – like high quality user documentation – that empower individuals towards self-sufficiency.

Always Here To Guide You: The Deque University Product User Guides Page

As I’ve discussed, the products themselves offer handy links and help buttons that will get you to the relevant guide pages in Deque U from strategic areas of the user interface. But there are many reasons you might want to go straight to a guide without the hassle of signing into the product itself first. For example, maybe there are certain tasks you perform less frequently in a WorldSpace product and want to review the “how-to” first, or maybe you’d like to share a topic in a guide with a new colleague – in either case, it would be nice to have a single starting point. Enter the Deque University Product Guides option on the main menu. This will take you to the “index” page of all of Deque’s product user documentation from a single page.

Regardless of the Deque product you’re using, your Deque University subscription goes far beyond the various traditional training options and courses you’d expect. There are detailed, comprehensive user guides and other related user-focused materials you can access whenever you want. Coupled with the self-led courses on web accessibility, Deque University is a really useful tool for empowering self-sufficiency when it comes to web accessibility. More than that, the resources we offer in Deque U illustrate why user documentation is such an important part of creating an informative web that works for everyone.

It’s just one more step on the journey to truly make the web all about the users – and that’s something we feel very passionately about here at Deque.

Operating Procedures Manual

General Information

The purpose of this manual is to provide all employees of Michigan Technological University with a reference manual containing policies and procedures established by the Board of Trustees, deans, department chairs, or directors. In the interest of brevity, an attempt has been made to include only that information which will be used under normal operating circumstances within the University. For special situations, it is recommended that the appropriate department be contacted.

The material in this manual ranges from partial Board of Trustees policies, to Administrative policies and procedures, to policies and procedures necessitated by state or federal laws and regulations. Consequently, for some policies and procedures, it is difficult, if not impossible, to implement modifications or obtain approval for exceptions. On the other hand, many of the policies and procedures, particularly Administrative policies and procedures, are subject to internally initiated change. Additionally, exceptions to Administrative policies and procedures are allowable when the justification is documented and is processed for approval through the normal channels of your organizational unit, including approval from the department responsible for the policy or procedure, to the appropriate vice president with notification to the provost and vice president for academic affairs.

The Michigan Technological University Operating Procedures Manual is available on the World Wide Web at: www.admin.mtu.edu/admin/procman/index.htm. Copies of the printed version are maintained at: the office of the policy and procedures coordinator, Room 314 of the Lakeshore Center; the Provost's Office, Room 503 of the Administration Building; and two (2) copies at the J.R. Van Pelt Library Archives and the Library Reserves(first floor).

Responsibility

The policies and procedures in this manual are issued by the appropriate vice president. These policies and procedures apply uniformly to all departments and employees of Michigan Technological University. Any exceptions will be noted in the manual.

What Is A User Guide

These procedures are designed to be of use to employees of Michigan Technological University. Therefore, all persons are asked to make suggestions for improvement of these procedures to the department that is directly responsibility for rendering the service. Departments should make a concerted effort to see that these policies/procedures reflect the most current practice of their department. It is important that no procedure be changed without incorporating the change in this manual.

Purpose Of User Manual

Maintenance

As sections and chapters from the Operating Procedures Manual are updated, they will be moved to the University Policies and Procedures Manual. If you can not find the procedure and/or policy you are looking for here, please go to the University Policies and Procedures web site. At this time, the Board of Trustees Policy Manual will be separately maintained and is available from the Board of Trustees office home page or by clicking here.

If you are an University employee who is writing or revising a policy or procedure, please consult policy 2.1001 of this Manual: Establishing and Creating University Policy and Procedures. The policy outlines the policy and procedure formatting and organization, and the process for approval of policies and procedures. There is a link in that policy to the templates you are encouraged to use.

Requests for advice and service for the Operating Procedures Manual and the University Policies and Procedures Manual should be directed to Lori Weir at llweir@mtu.edu, of the office the vice president for administration of Michigan Technological University.

Changes to the the Web version of the Manual will be explained on the What's New page.

History
Adopted:	06/30/2000
12/21/2001	Changed office of v.p. for Finance and Administration to v.p. for Administration and changed documents resource room 405 of administration building to documents resource room of the Library.
08/22/2003	Changed office of v.p. for administration to chief financial officer
05/08/2012	To reflect current University practice, the email address for questions is now hbwebmaster.
06/05/2015	To reflect current titles and practice, 'Board of Control' is now 'Board of Trustees' and the email address for questions is now policy.

What Is The Purpose Of A User Manual Software

Table of Contents :: Board Policy :: University Policies & Procedures :: Search :: Academic/Administrative Resources :: Michigan Tech Home