Wondershare EdrawMind
EdrawMindProduct acceptance
MindMap Gallery Product acceptance
- 6
Product acceptance
Regarding the mind map for product acceptance, Nielsen's ten usability principles: state perceptibility, close to user cognition, controllable operation, consistency, error prevention, recognition is better than recall, flexibility and efficiency, easy scanning, error tolerance, humanized help .
Edited at 2023-05-23 20:30:31- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
Product acceptance
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
- Recommended to you
- Outline
No relevant template
Product acceptance
<h1>Nielsen’s ten usability principles</h1>
<h3> Status aware</h3>
Are the menu tab records obvious?
Menu Tab allows users to know where they are currently
Is the title bar clear?
The title bar is the signature of a page. If a page does not even have a title bar, or the title bar does not match the content, the user experience will be extremely poor.
Is there a progress reminder for data loading?
It’s not that the user is unwilling to wait, it’s just that the waiting time is too long. The user doesn’t know how long it will take, so he simply closes the application. If a progress prompt is added to let him know how long it will take for the page to load and jump, he will will be more patient
<h3>Close to user awareness</h3>
Are all icons or terms understood by the user?
Are there any icons that are easily ambiguous?
In addition to icons, can all text be read by users? Is there any technical language that is closer to technology than to users?
<h3>Controllable operation</h3>
Does it support undo or redo?
<h3>Consistency</h3>
Functions with the same meaning must have the same name or icon.
Do the positions of both the back and forward buttons remain the same? Is there any situation where some pages have it and some pages don’t?
<h3>Error proofing</h3>
Is there a second confirmation for important operations that are prone to errors? For example, canceling an order, deleting records, etc.
Is there any text prompt before making irreversible operations such as deletion?
<h3>Recognition is better than memory</h3>
Will the filled-in content be displayed to the user for confirmation during final confirmation?
Have the selected products and quantities been reconfirmed with the user before final ordering?
<h3>Flexible and efficient</h3>
Is the loading speed fast enough?
Are the functions too complex to understand?
Is the direction of all clickable places clear? Are there any click events that make users hesitate?
Most importantly, do your intermediate users understand how to use it?
<h3>Easy to scan</h3>
Are important features/content highlighted?
Is the layout clearly divided?
Are unimportant functions hidden or moved or toned down?
<h3>Fault tolerance</h3>
If an error occurs, is there a user-friendly prompt telling the user where to go instead of just 404?
Will there be any abnormal operation that causes the application to crash?
<h3>Humanized help</h3>
Can simple functions be understood without documentation?
Is there any novice guidance for unfamiliar functions?
Is there a help center for difficult features?
Is there help documentation for complex questions?
Is the customer service number posted?