A long manual can contain the answer while still leaving someone stuck. The difficulty may be knowing which term to search for, which setting is involved, or what changed just before the problem appeared.
A useful explanation starts near the task. It names the situation, gives enough context to understand the choice, and offers a concrete next step. Deeper documentation can remain available without interrupting every ordinary action.
When explaining a tool to someone else, begin with the moment they are in. Show one relevant example before expanding the vocabulary. A well-placed sentence often makes a larger collection of documentation easier to use.
An example to consider.
A reader choosing an image size may need a short explanation of the tradeoff beside the control. A distant manual is less helpful at that moment.
Put it in perspective.
Follow the information through one complete task. What is created, where does it go, and what will someone need to understand it later?
- Begin with the reader’s current task.
- Show one relevant example.
- Offer a clear path to more detail.
Follow a related question
Describe a scene at two scales.
Changing the scale of a questionRecord the support behind the pilot.
From a pilot to an ordinary dayKeep learning
Related background to continue exploring this subject.
W3C: web standards W3C: accessibility, usability, and inclusion
