Integrating guidance throughout the design can assist users in understanding what to do and how to do it.
- Keep the language simple and avoid technical jargon.
- Make help easy to find.
- Use a variety of methods to cater to different learning styles.
Here are four different levels of help than can - and should - be incorporated:
Tooltips
Tooltips are small messages that appear when a user hovers over or clicks on an element. They are a great way to provide contextual information without cluttering the interface. Tooltips should be clear and concise, and it is best to use them sparingly to avoid overwhelming the user.
Onboarding
Onboarding is the process of guiding users through a product or service when they first start using it. This can be done through a series of screens or tutorials that explain what the product is and how to use it. Onboarding is an excellent way to educate users and reduce the learning curve.
Contextual Help
Contextual help is information that is presented to users based on their current context. For example, if a user is filling out a form incorrectly, an alert message could appear explaining what they need to do to fix it. Contextual help is a powerful tool to prevent errors and frustration.
Help Center / The Docs
A help center is a centralized location where users can find answers to their questions. It should be easily accessible and searchable, with clear categories and subcategories. A good help center should also include visual aids such as screenshots or videos to make it easier for users to understand. There is a tendency in DeFi to have highly technical docs in a Gitbook or something, but this isn’t really a help center. This can even be intimidating for users to search through. Depending on project size, you either want a hybrid help/docs, or you want to try and create a dedicated Help section. Or at the very least, an FAQ.