Gallery
See what others have created
requisiteworkshop
@requisiteworkshop
Offering help
Design a help pattern for a product screen, not a separate support page. Place the entry point where users would actually look for it: in the header, in a settings menu, or beside a confusing control. The design should make help feel available on demand, not buried.
Show what happens after the user opens help. Include a short list of common questions, a search field or quick links if needed, and a clear path to contact support when self-serve answers are not enough. Keep the content short and scannable so users can decide fast whether they can solve the issue themselves.
Add one contextual help example. This could be a tooltip on a field, an inline hint near a form control, or a small explainer attached to a feature that needs clarification. The help should answer the question in place and avoid forcing the user to switch screens.
What to deliver
- Design a help entry point in the product chrome.
- Show at least two help access patterns, such as icon, drawer, or support link.
- Include a compact help menu with common tasks and contact options.
- Add one contextual help state tied to a specific screen or field.
Incorporate familiar symbols like the '?' for help features. Play with subtle animations or highlights to draw attention to the help options, making them easier to find.