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.
Bring the idea into a day.
A calendar entry could describe the next action in everyday language. Someone returning after a busy afternoon should not need to reconstruct its technical meaning.
Another angle on the story.
A useful default saves a decision, but a visible explanation helps you revisit it. Look for the moment when convenience becomes a choice you should understand.
- Try a task as a first-time visitor.
- Look for a clear next step after an error.
- Notice whether important actions can be undone.
Follow a related question
Separate shared assets from request-specific content.
Static pages, dynamic possibilitiesDistinguish prompts from finished answers.
A template with room to thinkKeep learning
Related background to continue exploring this subject.
W3C: web standards W3C: accessibility, usability, and inclusion
