In Trimble’s pursuit of connectivity and scalability, Modus aims to harmonize the way users access help. Through various acquisitions and multiple teams working across many products it is important to strive for consistency of user assistance in help menus. This article serves to provide a comprehensive framework that will unify Trimble products, establishing a standardized taxonomy and hierarchical structure for organizing help assets.
The rationale of the help hierarchy is built upon the user help journey. Following is the user help journey extrapolated from various user interviews:
Modeling the help hierarchy to the current user behavior allows users to have access to the resources they find most useful.
At the top level there are six core categories required for the help menu:
- Getting Started
- Guides (written)
- Tutorials (video or wizard)
- Help Site
- Guides (usually short, text-based help)
- Support articles (longer text, to replace the so-called “Knowledge Base”)
- Suggestion box
- Demos (shorter video formats)
- Tutorials (longer video formats)
- Trimble learing
- Advanced instructions
- Customer portal
- Submit a support ticket
Most products have help assets which fall into one of these categories. Let’s learn more about the core categories and the subcategories that fit within them.
The Getting Started section is where written guides or video based tutorials are listed and found for users. The goal of the guides and tutorials are to show a new user how to get started with the product.
If the product does not have guides or tutorials geared towards helping a user get started, omit this category altogether.
The Help section is where a user will find a link to the associated help site for the product. This section can also include more links to short, text-based guides and a link to the product’s “Knowledge Base” (renamed as “Support Articles”). The guides found in this section are separate from the guides found in “Getting Started” as these guides are targeted to workflows within a product.
If the product does not have guides or a knowledge base use the “Help” category as a hyperlink to the product’s Help site. Meaning, this menu option would not have a second level navigation component.
The Community section is where a user will find links to the product’s community forum, suggestion box links and any blog content links associated with the product.
If the product only has one form of community content to link to, use the “Community” category as a hyperlink to that content and name the category the same as the content type. For example, if a product only has a suggestion box, instead of a “Community” category title that links to the suggestion box it will be titled “Suggestion Box”.
The Learning section is where a user will find links to the product’s learning assets. The order of the assets goes from the shortest time to consume to the longest.
Demos are short videos or articles that demonstrate features or show a user how to perform tasks.
Tutorials are longer videos or articles which may detail an entire workflow.
The Support section is where a user will find links to the product’s support portal. This is where users can submit tickets to get help or talk to a representative of the product.
The About section is a link to show information about their product, such as their version number.
Help assets have three core properties that can be used to identify their category:
Understanding these properties will help in identifying the category to which a particular help asset belongs.
The format of the help content ranges from highly visual to text-based content. For example, video content versus a written article.
The length of the help content ranges from a few minutes to a few days. For example, a task-based guide for a task versus a multiple day training for a module or workflow.
The scope of the help content ranges from task-based to a 30,000 foot view. For example, a task-based guide versus a demo video on how a new feature functions.
To simplify the taxonomy of help content, Modus employs four core categories:
Each of these categories encompasses the three properties mentioned earlier.
Here is how you can use these categories and their properties to identify the appropriate name for a help asset:
- Pick a help asset
- Consider its format, length, and scope, and assign a score using a sliding scale
- Compare the scores to the visual graphics provided below. This will help determine the main category under which the help asset falls.
For example, let’s consider a help asset labelled “How-To”:
- The format tends to be text-based.
- The length tends to be short.
- The scope tends to focus on tasks.
Based on these properties, the asset would be categorized as “Guide”.
Use the following visual graphics to help categorize help assets:
For products that have implemented the Modus Navbars use the help menu pattern guide to include the dropdown in the question mark icon as shown below:
Refer to examples of a fully implemented dropdown help menu system in the Navbars component styles section. The examples represent all six core categories. There are variations using icons, and supporting text for each category and ones that omit both. Icons and supporting text are recommended, however if the product cannot support this it can be omitted.
|User Assistance and help menu pattern guidance added.
|C. Christison, D. Bedick, A. Chammoth Sivaraman, M. Cowley, C. Cuellar, S. Kaukonen, F. Kuipers, A. Galstyan, T. Hautalahti, M. Linja-aho, R. Pekkinen, C. Starbird, T. Stryker, K. Vander Ploeg, J. Wegerer