A system can be capable without being comfortable to use. A setting may be precise but unexplained; an error may be accurate but give no useful next step.
Human-scale design begins with the situation. What does someone already know? What are they trying to finish? What happens if they make a mistake or lose their connection?
Clear language, visible state, and recoverable actions are technical choices as well as design choices. They help a system remain understandable when the day is less than ideal.
- Try a task as a first-time visitor.
- Look for a clear next step after an error.
- Notice whether important actions can be undone.
Bring the idea into a day.
Imagine a settings page organized around what a reader wants to change. Familiar questions can make a complex collection of options easier to approach.
Another angle on the story.
A feature becomes easier to understand when you can describe the ordinary action it supports. Start with the task, then work inward toward the mechanism.
Follow a related question
Look for the stated measurement limits.
Uncertainty belongs with the resultNotice what is complete or waiting.
A review that stays lightweightKeep learning
Related background to continue exploring this subject.
W3C: web standards W3C: accessibility, usability, and inclusion

