Designing For the Person Who Is Already Tired

“User-first” is a phrase that sounds good in presentations, but it only really means something when you picture a specific person. The user I have in mind is not excited, not hyper-productive, and definitely not patient. They are already tired before they open the app. They want to do one thing, then leave.

When I evaluate a product, I imagine what happens if this tired user logs in at 11:30 PM after a long day. Do they immediately know where to click? Are the important actions visible without hunting through menus? Do the words on the screen sound like a person talking, or like a policy document written by a committee? These details are not glamorous, but they decide whether the tool feels welcoming or hostile.

A user-first tool does not try to impress the user. It tries to protect their attention. It doesn’t force them to make unnecessary decisions (“Choose your layout!” “Pick your theme!”) when all they want is to finish a task. Simple defaults, clear wording, and a path that makes sense on the first try—that is what respect looks like in interface form.

Tip:
Do a “tired user test” on any important flow. Give yourself 30 seconds and try to complete the main action with as few clicks as possible. If you get confused even once, assume real users will, too—and fix that friction first.