Lean UX presentation (UXSG meetup #9)


Published on

Sharing of Lean UX case studies

Published in: Design, Technology

Lean UX presentation (UXSG meetup #9)

  1. 1. LeanUX It’s  not  lazy  UX,   It’s  about  minimizing  waste   Raven  Chai   Founding  Principal  Consultant
  2. 2. 2 RAVEN CHAI Founding Principal Consultant • Over 15 years experience as a technologist, designer and user experience practitioner • Completed over 120 UX projects since 2006 • Evaluated and assessed more than 1,000 startups across Asia • Formed a local UX Community - UXSG User Experience Professional Association - Asia Region, Leadership Team Founder & Principal Consultant Founder of UXSG Community Partnership / Mentorship Certi8ied  Practising  Management  Consultant  under  SPRING  Singapore
  3. 3. UX Consulting - What We Do Design  Research  and  Service  Design  Methodology
  4. 4. Some stuff I’m involved in... Public  Sector Private  Sector
  5. 5. Agenda 1.      Introduction   2.      Overview   3.      Design  Stories   4.      Key  Learnings   5.      Resources
  6. 6. h6p://konigi.com/files/konigi/images/what-­‐is-­‐ux.png
  7. 7. What  does  the  word  “Lean  UX”  mean  to  you?
  8. 8. “Lean  UX”  implies  that  less  UX  is  being  done.   ! That  couldn’t  be  further  from  the  truth,  nor   is  it  something  we  should  encourage. Source:  Ar*cle  from  Whitney  Hess,  Feb  27,  2011  -­‐  Why  I  detest  the  term  “Lean  UX”
  9. 9. hFp://notjustalive.files.wordpress.com/2010/12/lazy-­‐cat5.jpg It’s  NOT  lazy  UX   You  still  gonna  work  hard!!! Source:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011,  Lean  UX:  GeUng  Out  Of  The  Deliverables  Business
  10. 10. hFp://www.vuidesign.net/wp-­‐content/images/documenta*on.jpg It  is  NOT  Anti-­‐deliverable   It  is  a  refocusing  of  UX  efforts  away  from  the  documentation   and  moves  towards  validating  product  hypotheses Source:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011,  Lean  UX:  GeUng  Out  Of  The  Deliverables  Business
  11. 11. It  is  NOT  design-­‐by-­‐committee   Who  needs  vision  when  you  have  meetings? hFp://www.joerib.com/wp-­‐content/uploads/design-­‐by-­‐commiFee.jpg
  12. 12. The  only  thing  being  removed  is  waste   Minimizes  the  time  spent  heading  down  the  wrong  path hFp://notjustalive.files.wordpress.com/2010/12/lazy-­‐cat5.jpgSource:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011,  Lean  UX:  GeUng  Out  Of  The  Deliverables  Business
  13. 13. Prototype  communicates  everything   The  fastest  way  between  you  and  your  customers hFp://xunyangixd.files.wordpress.com/2011/04/just-­‐the-­‐ux-­‐process-­‐large.jpgSource:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011,  Lean  UX:  GeUng  Out  Of  The  Deliverables  Business
  14. 14. You  don’t  need  “The  Spec”  to  keep  control   You  are  in  the  problem-­‐solving  business,  and  you  don’t  solve   problems  with  design  documentation. hFp://www.arcelormiFal.com/distribu*onsolu*ons/repo/angelique/Corporate_picture_Document_Control_MR_RF.JPG Source:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011,     Lean  UX:  GeUng  Out  Of  The  Deliverables  Business
  15. 15. If  you  spend  3  months  perfecting  a  design  only  to  8ind  out  it  fails  to   meet  customer  and/or  business  needs,  you’ve  just   ! wasted  3  months  of  your  life,   not  to  mention  your  team’s Source:  www.jeffgothelf.com/blog
  16. 16. Lean  UX Metrics-­‐Driven  Design/Research SHIPPING  IS  ONLY   THE  BEGINNING
  17. 17. The  Value  of  the  Minimum  Viable  Product   The  bare  feature  set  needed  to  prove  out  a  hypothesis Source:  Ar*cle  from  Jeff  Gothelf,  Mar  07,  2011:  Lean  UX:  GeUng  Out  Of  The  Deliverables  Business hFp://i-­‐cdn.apartmenFherapy.com/uimages/re-­‐nest/plane12609.jpg
  18. 18. Started  with  a  boring  3  minute  video  in  2008  for  their   minimum  viable  product,  beta  waiHng  list  jump  from   5,000  to  75,000  in  one  day  (Mar  2008) Started  in  1984  with  a  single  Boeing  747  flying  a  single  route   (Gatwick  to  Newark  and  back).  As  they  got  the  Virgin  magic   working  and  debugged,  they  added  more  planes  and  more  routes. Examples  of  Minimum  Viable  Product  (MVP) It  started  out  as  a  simple  WordPress  blog,  the   point.com  with  a  widget  that  used  AppleScript  to   send  PDFs  coupons  via  Mail.app
  19. 19. Same  principle  is  applicable  for  the  larger,  growing  Mirms  too! You  probably  won’t  fancy  the  1st  version  of  Facebook,   but  it  started  to  address  user  needs  first From  iPhone  2G  to  4S  model  since  January  9,  2007 2004 2007 20092012 Despite  Basecamp’s  popularity,  the  team  keeps   improving  the  UX  and  usability  of  the  portal 29  Jun  2007 11  Jul  2008 8  Jun  2009 24  Jun  2010 7  October  2011
  20. 20. Agenda 1.      Introduction   2.      Overview   3.      Design  Stories   4.      Key  Learnings   5.      Resources
  21. 21. Story  1   Application  in  SDLC  methodology
  22. 22. Case Study - SMRTConnect Mobile App Some  facts:   • Commuters  wants  it   • More  than  80%  visitors  are  repeat  users   • But  received  plenty  of  complaints  and  negative  feedback   • Drastic  drop  in  usage  due  to  poor  performance  and  usability   • Yearn  for  better  improvement
  23. 23. User Research - Customer Data Identify the problems first
  24. 24. User Research - StoryBoarding Focus on people, not user interface
  25. 25. User Research - Paper Prototyping Cheaper - Better - Faster way to get your story right
  26. 26. Interaction Design - Understand Design Guidelines Read to fast track the design process
  27. 27. Interaction Design - Develop a Low-Fidelity Prototype Focus on interaction behaviour that are intuitive to the users
  28. 28. Interaction Design - Usability Findings 23 users  provide  invaluable   feedback  on  the  prototype Validate the design based on facts, not opinions
  29. 29. Interaction Design - Increase the Prototype Fidelity Define Design Specifications
  30. 30. Rapid Prototyping Process Start  small  with  a  only  few  key  areas,  grows  in  breath  and   depth  over  multiple  iterations Launched  iPhone  v1.1  on  19  Sep  2012
  31. 31. Design > Build > Launch Quantitative   data Qualitative   data Identify  key  pain   points Create  storyboard,   focusing  on  people  behaviour   and  social  norms Paper  prototyping   to  validate  interaction   Elow Create  low-­‐Eidelity   prototype  for  guerrilla   user  testing Adopt  design  best   practices Guerrilla  user  testing   to  validate  hypothesis Iterate  design  and   create  high-­‐Eidelity   prototype Create  design   document  for  technical   development Iterate  design  along   when  discover  new  user   scenarios Launch  v1  Eirst,  validate  usage  behaviour   and  plan  for  v2
  32. 32. Launched after 6 months of User Research, Prototyping and Coding Launched  iPhone  v1.1  on  19  Sep  2012
  33. 33. Story  2   Application  in  Startup  environment
  34. 34. Case Study - Schoozit Mobile App The  team  wants  to  develop  a  solution  to  collect  information   about  a  child’s  growth,  development  and  education. Put$together$such$informa1on$ clearly$&$1mely$into$a$ $Learning$Journey.$
  35. 35. User Research - Understanding your target users’ motivation Why and how they may use the product Teachers’  responses   13 30% 11% 37 28% 32 2% 2 34 2% 3 26% Parents’  responses 2 14% 4 29% 21%5 36% 3
  36. 36. User Research - Identify your users’ pain points Pre-­‐school  Teachers 2 3 1 Documenting  too  many  portfolios   -­‐  Lack  of  manpower   -­‐  Not  able  to  document  with  full  focus   -­‐  Multi-­‐tasking Not  able  to  document  immediately  by  writing   notes  or  using  camera   Lack  of  time Parents 4 When  children  are  frequently  absence  from   school Child’s  behavior     -­‐  Repetitive  actions  and  motivational  rewards   DifEiculty  in  organizing  photos  and  videos2 1 Initial findings gives you a starting point
  37. 37. User Research - Observation and depth Interviews gives you insights with context Validate your assumptions A  Typical  Day  in  School   Observation  on  how  lessons  were  carried  out Depth  Interviews  with  Users   Understand  their  motivations,  needs  and  pain  points
  38. 38. Experience Design - Understand where your product can be most effective Design Customer Journey Map Scenario 1: Teacher TUV decided to create a development milestone for her students so that it could act as a goal to what is needed to be achieved by a certain period of time. With the development milestones, it could be of any type of developement be it language, motor skills, etc. and parents are allowed to update the date as to when it must be achieved. Teacher TUV Parents Child!s Development Milestones Ok Language Age: Development: Date: 29 Dec 2012 Ages 6 to 12 Child!s Development Milestones Ok Language Age: Development: Date: 15 Dec 2012 Ages 6 to 12 Scenario 2: Teacher TUV has to set a !to-do"checklist for the students and parents to view so that it could act as a reminder and students are able to complete the tasks given. With the ‘to-do’ checklist, parents will be able to check up on their child’s task and make sure they have completed it. Once completed, parents are able to update the checklist. Teacher TUV John"s Parents John completed his Maths homework. Today!s Checklist Ok Maths H/W Spelling Test Revision Today!s Checklist Send Maths H/W Spelling Test Revision Notification Teacher TUV requires your acknowledgement Student!s Progress Acknowledge John Tay 06/10/2013 - Full marks for spelling Parents Once teachers have updated on the students’ progress, parents will receive a notification alert asking for their acknowledgement. Parents will read through the progress and able to acknowledge it simply by pressing on the ‘Acknowledge’ button. Scenario 3: At the end of the day, Teacher TUV updated on all of her students! progress for the spelling test she conducted earlier on and she requires all parents to acknowledge on their child!s progress. Teachers are able to tag student before posting out the remarks. Same goes for uploading a photo. They can tag student and also put a caption after taking a photo of the student’s progression. Afterwhich, parents will receive a notification alert on the tagged photo or remark. Scenario 4: Teacher TUV wants to update on one of her student!s progression by posting remarks as well as taking a photo and uploading it to the student!s profile for his parents to view. Post Photo Post Caption Tag John is starting to socialise! John Tay Teacher TUV of Class XYZ Post Remark Post Remark Tag John needs to improve on his spelling. John Tay Notification Teacher A has tagged you in a photo. Teacher A has left a remark. John!s Parents Given that Teacher XYZ teaches two classes, the search results will be restricted to only the classes that she is teaching. Search Ok May May Chua May Wong Teacher XYZ of Class XYZ and Class TUV May Chua Class XYZ May Wong Class TUV May Lim Class PQR Scenario 6: Teacher XYZ wants to search for one of her students named May Wong from Class TUV. ParentsTeacher TUV of Class XYZ Parents: I would like to enquire about tomorrow’s lesson Teacher A: Yes sure. How may I help you? Parents: How would tomorrow’s lesson benefit my child? Message Messages can be set to private where only chosen recipient(s) (Teachers/Principal) is/are able to view. Teacher XYZ of Class XYZ Teacher PQR of Class TUV Principal Scenario 5: Parents having a personal conversation via Schoozitʼs message feature with their childrenʼs teacher(s) Appendix
5.7 Appendix
5.1 Appendix
5.2 Appendix
5.3 Appendix
5.4 Appendix
5.5 Appendix
5.6 In terms of tagging photos, Teachers are allowed to tag students even from other classes that they are not teaching. Scenario 7: Teacher TUV attended the Inter-Class Competition and took photos which includes students from other classes and she wants to tag them. Inter-Class Competition Teacher TUV of Class XYZ Post Photo Post Caption Tag Competition David David Chua David Chan David Chua Class TUV Simon Tan Class PQR
  39. 39. Story  3   Application  in  Agile  UX  Approach Due to sensitivity of the case study, the slides for Story 3 will not be available for public viewing
  40. 40. Agenda 1.      Introduction   2.      Overview   3.      Design  Stories   4.      Key  Learnings   5.      Resources
  41. 41. hFp://www.kickerstudio.com/blog/images/ux.jpgSource:  Ar*cle  from  Jared  M.  Spool,  Nov  30,  2011,  Is  There  Any  Meat  on  This  Lean  UX  Thing? Lean UX is just UX. But UX isn't always Lean UX.
  42. 42. 2. Features begin as hypotheses to be tested before heavy investment 3. A feature starts as a minimum valuable feature, and then iterates 4. Proof carries more weight than opinion 5. The team talks to real customers on a regular basis, including in-person 1. You are composed of small, goal-driven, cross-functional teams How  Lean  UX  may  work  well? How  Lean  UX  may  not  work  well?         1. If your stakeholders requires formality to justify decisions 2. If you need to deal with legacy systems and require regular updates
  43. 43. Relationship - UX is not UI UI UX hFp://www.kickerstudio.com/blog/2008/12/the-­‐disciplines-­‐of-­‐user-­‐experience/
  44. 44. A  “user-­‐friendly”  UI  =  Good  UX
  45. 45. UX UI how  people  feels  while  they   do  certain  things what  people  use  to  interact   with  the  product Emotional Technical
  46. 46. Agenda 1.      Introduction   2.      Overview   3.      Design  Stories   4.      Key  Learnings   5.      Resources
  47. 47. Recommended Books
  48. 48. Online UX Web Resources Smashing  Magazine UX  Booth UIE  Blog Johnny  Holland UX  Matters Fast  Company Jeff  Gothelf’s  Blog
  49. 49. Conferences UXPA  London,  21  -­‐  24  Jul  2014 UX  Australia,  26  -­‐  29  Aug  2014 UXPA  Indonesia,  early  Nov  2014 User  Friendly  China,  13  -­‐16  Nov  2014 UXSG  Conference,  1  -­‐  3  Oct  2014
  50. 50. RAVEN CHAI Email:  raven@uxconsulting.com.sg   Twitter:  @ravenchai Publications  /  Featured  in:   http://www.slideshare.net/uxconsulting   http://www.uxconsulting.com.sg/articles