Skip to content
Share
Explore
Waha UX/UI Information Scaffolding
Usability Guidelines
Waha should generally follow these guidelines. Credit to https://www.nngroup.com/
When should these be used?
Guideline
Description
1
Keep users informed
Waha should always let users know what is happening and provide feedback within a reasonable amount of time.
2
Use familiar language
Waha should use words and concepts that are familiar to users, rather than technical (ie DMM / legacy church) terms. It should also follow real-world conventions in the way it presents information.
3
Give users control
Users should be able to easily undo or redo actions, and have a clear way to exit unwanted states.
4
Be consistent
Users shouldn't have to wonder if different words, situations, or actions mean the same thing. Waha should follow standard conventions.
5
Prevent errors
Waha should be designed to avoid errors whenever possible, or at least confirm with users before they make mistakes.
6
Make information easy to find
Waha should make it easy for users to access the information they need, and shouldn't require them to remember information from one part of the interface to another.
7
Be efficient
Waha should allow experienced users to work more quickly, but also be easy for inexperienced users to use. It should allow users to customize frequent actions.
8
Keep the design simple
The interface of Waha should only contain necessary information and not be cluttered with unnecessary details.
9
Help users fix errors
Error messages should be clear, explain the problem, and suggest a solution.
10
Provide help
If necessary, Waha should provide clear and helpful documentation that is easy to search and focused on the tasks users need to complete.
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.