Personas, scenarios, user stories

4,331 views

Published on

IxDworks.com tutorial materials.

Published in: Education

Personas, scenarios, user stories

  1. 1. Personas, scenarios and user stories IxDworks.com Understanding Users
  2. 2. User-Centered Design
  3. 3. Useful Usable Desirable Doing things easily and with pleasure.
  4. 4. Doing things easily and with pleasure. Behaviour
  5. 5. Doing things easily and with pleasure. Behaviour Optimising design based on how users 
 can, want or need to use a solution.
  6. 6. http://v2.centralstory.com/about/squiggle/ We are here Heading here
  7. 7. Restaurant
  8. 8. Marine
  9. 9. Sport
  10. 10. Goals & UX
  11. 11. “User experience is a stream of passing momentary feelings” – M. Hassenzahl
  12. 12. Be-goals, experience Hedonic; feeling/being e.g. ‣ Relax ‣ Look cool ‣ Remain focused ‣ Be independent ‣ Be loved “A constant stream of self-talk” – Forlizzi & Battarbee
  13. 13. Experience goals Hedonic; feeling/being e.g. Look cool Become admired Remain focused Get rich Be loved Do-goals, actions Pragmatic; doing e.g. ‣ Post a Tweet ‣ Look up a place ‣ Set up a website ‣ Play a game ‣ Close Facebook account
  14. 14. A user experience occurs when a person interacts with a product.
  15. 15. Do-goals, actions TasksBe-goals, experiences Share a photo 1.Take photo 2.Add info 3. Upload 4. Preview Self-expression
  16. 16. • Foundation for the design • Ground for discussion • A “reality check” • Empathy • Easier to relate 
 (than to e.g. flow chart) Why goals?
  17. 17. Towards User Personas & Storytelling
  18. 18. We can’t ask users to be with us all the time, thus we make user models.
  19. 19. Persona • Describes (your app’s) imaginative users archetypes. • Is based on the real research and observation. • Shows user goals and their behavior patterns • Helps to crack “what” and “why” questions • Primary, secondary, supplemental, non-persona
  20. 20. Fake persona • Stereotype or a caricature • Can’t be backed up • Factoids • Fun, but often useless
  21. 21. Persona • Used as an aid to help express, discuss and validate design questions and decisions, e.g. • Would the persona (“Bob”) use this? • Is this logical? • Does this make sense to this persona? • Is it fun / exiting / motivating... ? • Bob would not like this, because....
  22. 22. Sources Primary Secondary Personal know-how Stakeholders Online discussions Domain experts Informed guesses Feedback Surveys Contextual inquiry; Talking to people directly, Observing their behaviour *Bonus
  23. 23. •Talk to people who a different from you and what you know already •Look for reoccurring issues and trends, language (lingo), surprises... •Acknowledge your biases and be open-minded
  24. 24. Persona documentation • Helps to communicate persona to other stakeholders • A document might include e.g. • background info: age, gender, occupation • mapping, such as technical skills • a short description of an activity, that is related to the current context or problem settings and frustrations • goals
  25. 25. A business card.
  26. 26. Example template, yours can look different! Background Bio Name, (age), (role), occupation, education Photo(s) Description E.g. use environment or context, where the problem occurs and current solutions and frustrations. Goals • What are the user’s end goals? • 2-4 end goals and 0-1 life goals is enough 
 for this workshop Mapping E.g. computer skills, necessity vs fun, quality vs price.
  27. 27. Example template, yours can look different! Petter Tamm 44, botanic garden worker, father of two children Goals • Wants to manage bulk orderings more efficiently • Is looking for quality reviews about new products Reads reviews to find best... quality price As a lead gardener, Petter is responsible in ordering nutritions and specific soil for the plants for the city’s botanic garden. Currently he has to do 
 bi-weekly orders over the phone from his office, calling manufacturers one by one.
  28. 28. Before moving on… define “what” of your project What need/goal/expectation does it serve?
  29. 29. Scenarios
  30. 30. Scenarios • Stories that help understand interactions • A cheap way to illustrate design solution 
 from user’s (persona’s) point of view • Tell user’s goals, motivations and actions “What should this product do?” “How would user behave in this context?” “What if...?”
  31. 31. Scenarios • without your solution present-based • Focus is set on current practices that illustrate ‘state of the art’ and the problem context • with your solution future-based • Focus on how problems could be addressed (without diving into details and jargon). Scopeofwork
  32. 32. It’s Friday afternoon. Petter opens his desktop computer at the botanic center’s office. He wants to be quickly done with the extra flower soil orders. ! Petter decides to order the same combination of products as four weeks ago, but in smaller quantity. He does not order nutritions this time. ! Petter is not interested in staying at the office long.As soon as the order is done, he leaves work to pick his daughter from school. Context-based scenario
  33. 33. It’s Friday afternoon. Petter opens his desktop computer at the botanic center’s office. He wants to be quickly done with the extra flower soil orders. ! Petter decides to order the same combination of products as four weeks ago, but in smaller quantity. He does not order nutritions this time. ! Petter is not interested in staying at the office long.As soon as the order is done, he leaves work to pick his daughter from school. Story background, settings Goal “extra orders, quick” Motivation: efficiency High level actions 
 (e.g. re-ordering x with changes, not ordering y.)
  34. 34. • In what settings will the product be used? • Is the persona frequently interrupted? • With what other products will it be used? • What primary activities does the persona need to perform to meet her goals?
 • What is the expected end result of using the product?
  35. 35. Use Cases/ User Stories
  36. 36. Use Cases A step-by-step, often detailed description of product’s behaviour, which helps the user (and other actors) to achieve a result. Components: Use Case,Actors, Steps Success Condition: what is considered a successful end to the use case Failure Condition: what is considered a failed end to the use case
  37. 37. Steps / Basic course of events 1. Check what has been ordered before. 2. Renew a previous order. 3. Modify the order to suit current situation. 4. Place the order. Alternative course of events In step 1. check favorite orders. Use Cases Simple example Use Case – Ordering extra soil. 
 Actor – Petter / botanic garden worker
  38. 38. User Stories A simple, easily readable description of a specific user need. As a (persona/role) I want to do (what), so I can benefit (how). As a botanic garden worker I want to order extra soil. Original model popularized by Mike Cohn, Screenshot: ScrumDesk
  39. 39. Condition details User Stories Epic / Saga user stories Theme user stories User stories with clear conditions of satisfactions Theme user stories Theme user stories
  40. 40. Epic / Saga user story Example of a conditions of satisfactions As a gardener I want to quickly order extra soil. ... to see previous offers. – Condition: similar to the new offer ... to modify the order. ... to submit a new order. etc. As a gardener I want to order soil. Themed user stories
  41. 41. Today’s “To Do”
  42. 42. Task 1. Discuss and describe 1 primary persona 2.Write 1 scenario based on persona’s goal • How would persona use your (future) solution? 3.Write few fundamental user stories OR an use case based on the scenario • Define the most basic and crucial interactions
  43. 43. Resources • Cooper,Alan, Reimann, R & Cronin, D. (2007) About Face 3:The essentials of interaction design.Wiley; ISBN: 0470084111 • Hinton,Andrew. Personas and the Role of Documentation. (2008) http://boxesandarrows.com/personas-and- the-role-of-design-documentation/ • Accessibility in User-Centered Design http://www.uiaccess.com/accessucd/personas.html • Hassenzahl, M. (2008). User Experience (UX):Towards and experiential perspective on product quality. http:// www.researchgate.net/publication/ 238472807_User_experience_(UX)_Towards_an_experiential_perspective_on_product_quality/file/ 60b7d51bf4873231da.pdf • What research methods could I use to create personas? http://ux.stackexchange.com/questions/21891/what- research-methods-can-i-use-to-create-personas • Personas http://wiki.fluidproject.org/display/fluid/Persona+Categories • Mike Cohn. http://www.mountaingoatsoftware.com/articles?tag=user%20stories • Stellman & Green. Building better software. http://www.stellman-greene.com/2009/05/03/requirements-101- user-stories-vs-use-cases/ • User Story map http://winnipegagilist.blogspot.com/2012/03/how-to-create-user-story-map.html
  44. 44. Images • Boat https://www.flickr.com/photos/time-to-look/14551961151/sizes/l • Restaurant https://www.flickr.com/photos/en321/9908577253/sizes/l • Girls with ice-creams https://www.flickr.com/photos/pbaitor/4998329309/sizes/l • Woman in hospital bed https://www.flickr.com/photos/uhduh/12242998/sizes/l • Girl with a phone https://www.flickr.com/photos/brandoncwarren/2952179726/sizes/l • Men on a bench https://www.flickr.com/photos/scottrsmith/6194527237/sizes/l • Woman at ATM https://www.flickr.com/photos/betsssssy/435300495/sizes/l • User Case Map http://www.batimes.com/articles/user-stories-and-use-cases-dont-use-both.html

×