Loading…
Loading…
Resources like guides and FAQs that help users understand and use a product.
stellae.design
Help and documentation (Nielsen's 10th heuristic) acknowledges that help content is still necessary even for usable systems. Help should be easy to search, focused on tasks, list concrete steps, and not be too large. Modern interpretation extends to embedded help: tooltips, onboarding flows, contextual guidance, and empty state instructions. Help should be the last resort, not the primary interface.
Help and documentation is the tenth and final of Jakob Nielsen's usability heuristics, recognizing that even the most intuitive interfaces occasionally require users to seek guidance for complex, infrequent, or domain-specific tasks. Effective help reduces support costs, accelerates onboarding, and empowers users to solve problems independently rather than abandoning the product or filing a ticket. The quality of help content is often the deciding factor in whether a frustrated user recovers or churns, making it a direct contributor to retention and satisfaction.
Stripe provides inline code examples alongside every API endpoint, with a live request builder that lets developers test calls without leaving the documentation page. The help content is organized by task — accepting a payment, creating a subscription, handling refunds — matching how developers think about their goals. Copy-paste-ready code samples in multiple languages eliminate the translation step between reading documentation and writing implementation code.
When users type a forward slash in Notion, a searchable menu of all available block types appears with icons, names, and brief descriptions for each option. Users discover features in context while actively working rather than needing to consult a separate manual. The pattern turns the help system into a discovery mechanism embedded directly in the user's workflow.
An enterprise application hides its help documentation behind a settings menu, then a support submenu, then a knowledge base link that opens a separate portal requiring a second login. Users who encounter a problem must interrupt their task, navigate a labyrinth, authenticate again, and then search a poorly indexed FAQ. By the time they find an answer — if one exists — the cognitive cost has already eroded their trust in the product.
• The most common mistake is writing help documentation from the perspective of the product team rather than the user, organizing content by feature modules instead of user tasks and using internal jargon that the audience does not recognize. Another error is creating documentation once at launch and never updating it, so users encounter screenshots and instructions that no longer match the current interface. Teams also underinvest in search within help systems, forcing users to browse hierarchical categories when they already know what they need and just want to type a question.
Was this article helpful?