What: What do they want or need to do? What are their tasks? What are their motivations?
When: Temporally, how does one task follow the other? When is a task begun? When does it end?
Where: Where is your solution to be used? A UI for a refinery floor that the operator uses while wearing gloves will be different than one that's used primarily from a cell phone.
Why: Why does the user do what they do; what are their "goals" and motivations?
How: How do the users currently carry out their tasks? A lot can be learned about their expectations by fully understanding how they currently work.
Neat. Like a pre-flight checklist for design.
ReplyDeleteThanks, uxarchitecture. I just checked out your blog. I'll definitely be following.
ReplyDeleteScott