Who’s it for?
It’s not for everybody, so don’t worry about everybody. Worry about your person. Are they an expert or a beginner? You’ll have to make assumptions about terminology, visuals, and workflow. Build them around who it’s for.
Why are they here?
They’re using your UI to do something. What is that, and why? Simplify around the why. Make the why front and center and dead-easy to understand and recognize. The default workflow should naturally support the why.
What do they care about?
Attend to what they care about, not what you care about. They care about feeling smart, heard, and accomplished. Your UI should make them feel all of those.
What do they struggle with?
Tolerate mistakes. Simplify terminology and workflow. Guide via defaults. Use visuals consistently with terminology. Less clicks. Less talking. Less time.
Use the above questions to design your UI. Whether its an app, service, or you.
