13. February 27, 2013
First, know your users.
⢠What are they trying to accomplish?
!
â˘Â What are their metrics of success?
Productivity, creativity, accomplishment,
better communication, fun?
!
â˘Â Oh, and... who are they?
14. February 27, 2013
A common problem app developers face is
unknowingly designing for:
â˘Â Their features and capabilities
â˘Â Themselves
â˘Â Everyone
â˘Â Their mom
15. February 27, 2013
To avoid falling in this trap, create a persona!
!
Personas are ďŹctional, archetypal users that
represent the needs of larger groups of users
16. February 27, 2013
To avoid falling in this trap, create a persona!
!
They act as âstand-insâ for real users and help guide
decisions about functionality and design
17. February 27, 2013
!
Personas have speciďŹc attributes as people and
needs as users. They should be ârealâ enough to
talk about and design for
!
18. February 27, 2013
Personas are useful for:
!
Giving the team a shared point of reference for
design (much better than everyoneâs mom)
19. February 27, 2013
Personas are useful for:
!
Tying the usage and design of the product to real
human needs, not just features
20. February 27, 2013
Personas are useful for:
!
Focusing the scope of design on particular kinds of
users, rather than âall usersâ