An interactive design of user handbook with social help

Demand analysis

Company A more complex software needs product upgrades, the new version of the relatively old version has more improvements, but also added a lot of new features. In order for users to easily enter the use state, a new user manual needs to be redesigned.

So, in the interactive design process, how to design the user manual?

For a novice, it is necessary to understand the basic functions.

The user sees creating a concrete instance, rather than simply understanding the basic functionality. In the process of using software, users need to quickly enter a more proficient state, they do not want to waste too much time in the introductory phase.

In the process of using the user, there is a need to use some of the features to store them in a signed fashion, and not to rule out that everyone has been in a state of proficiency, and that sometimes the help they have summed up is more useful than the help of research and implementation personnel, and more useful if they can be shared by others.

So the new Help manual, in the content will help divide into three types: feature Help, Application Help, my help.

function help, for the most basic module help, is some language rigorous functional description, used to introduce the function of the product module, Product Manager can complete the "functional help" writing.

Application help needs to be combined with specific application scenarios to write examples, by the first line of product implementation personnel led the completion. In the process of writing, use the graphics and text tutorials, if necessary, flash animation can be used to describe the process.

My help allows the user to write down the application of the process and recommend some excellent documents for you to use.

Type switching

Three kinds of classifications for users of different application levels to learn to use. If you can't switch smoothly, you might as well mix these three types of help together. But because of the complexity of the software, especially when the user is done, there is no need to read "feature help" over and over again, or even to view "my help" at most.

In the product, these three types of help, using the same directory hierarchy, switch to each other according to the directory entry switch. They jump to anchor each other. For example, when browsing the "function help" of module A, click the "Apply Help" button, then go to the application help of a module.

Help Interface Interactive Design draft

When the user clicks the Help button, it enters the appropriate type of help by memory. If you click the B module's Help button, you enter the appropriate help type for B (the user last visited the "functional module" of a module in the software, the "functional Help" to B), and if the user first uses Help, you can go to "feature help."

My help.

"Feature help" and "Application Help" have no particular focus on design, and need to emphasize "my help."

When the user enters my help, there is help information, a share list, and a new three modules.

My Help list

When you create a new custom help, the sharing and allow comments are selected by default, and users can also cancel them. If a document is a "shared" type, it can be reproduced. At the same time, you have the right to edit a variety of custom documents.

New/Edit Page

Share list, displays the help information that is shared in all custom Help, and displays the number of shares that have been shared, sorted by the number of shared times and the priority of the dates.

Help information, display custom Help and reprinted documents. The sharing document will be updated according to the author's update, but the reprint is no longer updated, and the user can modify the reproduced document.

Summarize

(1) Maintain consistency

In the jump process, you must maintain consistency, users can be in the process of using a module to continuously step. Because three kinds of help documents are classified according to the same directory, the consistency of the jump can be realized smoothly.

(2) Respect the user's habit

If the user stays in "functional help" and "Application Help", he has been unskilled in using it. It is possible to enter a more proficient state when the user uses most of my help. As a result, users are likely to have more help in one of the three help categories at different stages. Let the system remember which type of help was last entered, and this time it also went into such help.

(3) The advantages of socialization

Sharing and commenting can improve the sense of achievement and enthusiasm of the participants. Sharing features makes it possible to share the achievements of others, and viewers can also make reasonable comments for them, which is conducive to the improvement of their application level. Maybe one day, users just need to see the help they write, without having to look at functional help, and become an efficient way to learn to get started.