Big-tent UX (UX Camp West 2016)
•
202 j'aime•48,628 vues
We’re all camping at UX Camp West, so I thought I’d use the metaphor of a tent to share with you my view on the field of User Experience. I will describe the 7 poles of the tent's structure (research, design, evaluation, implementation, business, strategy, and management) and show you some random objects that I found in its corners. It is my goal that afterwards, we can all appreciate the beauty of the big tent, and realise how we contribute to a happy stay.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Big-tent UX (UX Camp West 2016)
Similaire à Big-tent UX (UX Camp West 2016) (20)
Plus de Peter Boersma
Plus de Peter Boersma (20)
Dernier
Dernier (20)
Big-tent UX (UX Camp West 2016)
- 1. Big-tent UX @pboersma UX Camp West 2016
- 2. Peter Boersma * Dutch but married to Hamburger Deern * information ergonomist = computer science + cognitive ergonomics * interaction designer * UX strategist * design process freak * UX Cocktail Hours in Amsterdam since 2001
- 3. T-model for UX (2004)
- 4. every field shallow skills deep skills business skills skills of other fields skills of other fields
- 5. UX = many related fields
- 6. UX = many related fields user experience skills
- 7. every UX practitioner is unique user experience practitioner X
- 8. every UX practitioner is unique user experience practitioner Y
- 9. every UX practitioner is unique user experience practitioner Z
- 10. every UX practitioner is unique unicorn
- 11. 7 main pillars
- 12. Business
- 13. Strategy
- 15. Research
- 16. Design
- 17. Evaluation
- 18. Implementation
- 19. 7 main pillars
- 20. Big-tent UX
- 21. Business
- 23. X
- 26. Business
- 27. Strategy
- 38. Strategy
- 42. area area area area area progress progress progress progress progress progress progress progress progress progress moment momentmoment moment
- 44. Scope Management
- 45. easy hard merely contributes essential quick win repair quality winner! pick just a few of these for your release!
- 46. Time & Budget Management
- 48. example estimate assuming we design 10 wireframes (5 complex + 5 medium) plus 15 components we estimate we need 300 hours but we don’t know the documentation needs of the developer (5x16 + 5x8) + (15x12)
- 50. Kim Goodwin on Org. Culture
- 59. Research
- 61. ask what is the idea? will it help you reach your goals? will customers accept it? why now? how fast can you move? and find out value of answers
- 64. ask: what is the idea?
- 65. ask: why now?
- 66. and find out the value of answers
- 68. ask who are you? what do you use now? how do you feel about it? when is it a good/bad day? what should it be like? and find out value of answers
- 71. Design Research
- 74. Research
- 75. Design
- 84. “Concept diagram” for bank site Life Play Buy based on real motivations of real people with modules to discover and personalise with information about products & processes Learn aimed at selling relevant products in a transparent fashion
- 91. Design
- 92. Evaluation
- 93. Evaluation With a few people * focus group * usability test * releasing an MVP With many people * public beta With all users * analytics * A/B tests * SEO
- 100. A
- 101. B
- 102. C
- 104. 28% better
- 105. Evaluation
- 106. Implementation
- 114. WTF is “the full allotment”!? Thank you for submitting your application to the American Kennel Club. Unfortunately, we are unable to complete the processing of your application. The dog name you selected cannot be used because American Kennel Club has already registered the full allotment of this breed with your requested name. So that we may continue processing your application, please print a VALID name choice in the space below.
- 115. American Kennel Club guidelines
- 117. Agile and UX Agile is useful for in-house developers of increments to existing systems.
- 118. Promising applications of Agile
- 119. Promising applications of Agile
- 120. Promising applications of Agile
- 121. The 5-day sprint (2010)
- 122. Implementation
- 123. 7 main pillars
- 124. from pillars to tent
- 125. Process
- 126. why document your process? 1. to agree on what ‘things’ are called 2. to link design activities with other processes 3. to increase efficiency through standardization 4. to speed up integration of team members 5. to explain to your client where they are involved 6. to measure your work, so you can improve it
- 127. Start with sketching your process
- 128. SITEMAP wireframes require- ments usability test Screen FLOW proto- type design principles Persona
- 129. 1 2 3 4 Persona SITEMAP wireframes require- ments usability test Screen FLOW proto- type design principles
- 130. 1 2 3 4user research concept design detailed design prototype & evaluate Persona SITEMAP wireframes require- ments usability test Screen FLOW proto- type design principles
- 148. 10 steps 1. identify your current deliverables 2.create diagram with deliverables & phases 3.describe activities, specifying input & output 4.present process to rest of company 5.improve diagram & descriptions ...
- 149. 10 steps ... 6.create templates & instructions for deliverables 7.update diagram & descriptions 8.promote your process, internally & externally 9.measure & evaluate working with the process 10. continue to improve the process
- 150. a plan for process improvement I will <do something> together with <another role> and we will change <a part of the process> to improve <a success metric> before <a deadline>.
- 151. Process
- 152. Big-tent UX Business Strategy Resource Management Design EvaluationImplementation Research
- 153. Big-tent UX Business Strategy Resource Management Design EvaluationImplementation Research Process
- 154. UX = many related fields user experience skills
- 155. every UX practitioner is unique user experience practitioner X
- 156. Big-tent UX @pboersma UX Camp West 2016