Aim for a product that needs no explanation, then write help for the cases where that is impossible.
HEUR·010Heuristic · Nielsen heuristics
Entries tagged documentation, drawn from across the library. Tags cut through the section structure, which is where most of the useful connections are.
11 entries
Aim for a product that needs no explanation, then write help for the cases where that is impossible.
HEUR·010Heuristic · Nielsen heuristics
Once you know how something works you cannot accurately imagine not knowing, which is why teams misjudge their own interfaces.
BIAS·008Cognitive bias · Judgement
Users start acting immediately rather than reading, even when reading would be faster, so design has to teach through doing.
PSY·007Psychology · Learning
Documentation is the product. An undocumented system is a component library nobody can adopt correctly.
SYS·003Design system · Practice
Drafting component documentation from code, which handles the mechanical parts and not the judgement.
AI·007AI workflow · Design systems
A large share of searches returned nothing, and the fix was vocabulary rather than the search engine.
CASE·006Case study · Search
Long-established tool for complex, data-driven prototypes and detailed specifications.
TOOL·012Tool · prototyping
The standard workshop for developing and documenting components in isolation.
TOOL·037Tool · design-systems
Design system documentation aimed at the whole team, not only engineers.
TOOL·038Tool · design-systems
Flexible documents and databases, used by many teams as a lightweight research repository.
TOOL·044Tool · collaboration
Enterprise documentation, usually chosen because the organisation already runs Jira.
TOOL·045Tool · collaboration