UXscot17 - Change through education
Download as PPTX, PDF1 like808 views
Neil Allison emphasizes the importance of building a UX culture through education at the University of Edinburgh, advocating that everyone contributes to user experience. He compares usability to cooking, where basic skills are necessary for effective results, with a master needed for excellence. The presentation outlines the progression towards recognized and managed organizational maturity in UX practices over specified years.
UXscot17 - Change through education
- 1. Change through education Building a UX culture while empowering colleagues Neil Allison UX Manager, University of Edinburgh @usabilityed #uxscot
- 2. • Imagine for a moment you’re a classroom teacher. How do you know how you’re doing?
- 4. A few metrics for a teacher… • % who did their homework • % who brought everything they needed to class • Average noise level • % of required content covered • Did the class enjoy themselves? • How many kids did I need to sanction? • Topic test scores • End of year exam scores
- 7. Perception of UX professionals “…like tree huggers but for users…” Lisa Reichelt www.disambiguity.com/guerrilla-empathy
- 8. Everybody is responsible for the user experience. We need to get to a place where UX empathy, curiosity, communication is just part of a basic skills set. Imagine if we were talking about writing. How crazy would it be to expect one person on the team to do all the work when stuff needed writing down?
- 11. "Usability is like cooking: everybody needs the results, anybody can do it reasonably well with a bit of training, and yet it takes a master to produce a gourmet outcome.” Jakob Nielsen
- 13. How to run a collaborative review session: http://bit.ly/uoe-agile-usability
- 14. Why usability problems go unfixed http://bit.ly/krug-jarrett-unfixed Have you had your recommended dose of research? http://bit.ly/research-dose
- 15. Collaborative sketching at scale http://bit.ly/ux-sketching-scale
- 19. Initial position: Absent to Informal By end of 2016/17: Recognised By end of 2018/19: Managed Target organisational maturity
- 21. Thank you Change through education Neil Allison UX Manager, University of Edinburgh @usabilityed #uxscot
- 22. Image credits • 1 & 21: Graduates: https://static.pexels.com/photos/267885/pexels-photo-267885.jpeg • 2: Classroom www.flickr.com (michael 1952) • 3: Child in class http://cdn.skim.gs/image/upload/v1456337727/msi/student-goofing-off-in-class-600_ys6eh4.jpg • 4: Measure www.flickr.com (william warby) • 5: University of Edinburgh crest: www.ed.ac.uk • 6: Tanker: https://upload.wikimedia.org/wikipedia/commons/thumb/5/5d/Oil_tanker_Sanko_Brave_%28IMO_9257010%29_just_past_the_Golden_Gate_Bridge.jpg/1280px- Oil_tanker_Sanko_Brave_%28IMO_9257010%29_just_past_the_Golden_Gate_Bridge.jpg • 7: Treehugger https://www.flickr.com/photos/marinadelcastell/14778027283 • 8: “Everyone is responsible…” Lis Hubert quote on wall http://t.co/nILAB5oIE7 • 9: Blog posts: Neil Allison • 10: Typing pool: https://c1.staticflickr.com/6/5654/20958039231_c92ea47b20_b.jpg • 11: Beans on toast www.flickr.com (Robyn Lee) • 12: Rocket Surgery book image: Steve Krug, www.sensible.com https://image.slidesharecdn.com/sxsw11-stevekrug-110728132913-phpapp02/95/steve-krug-explains-it-all-for-you-sxsw-2011-58-728.jpg?cb=1311860797 • 12-16: UX training, Neil Allison • 17: Jeff Gothelf and Lean UX book www.jeffgothelf.com • 18: Crystal ball: https://c1.staticflickr.com/1/621/21523294814_ddd84475e2_b.jpg • 19: UX Maturity model: Abi Reynolds, www.uservision.co.uk • 20: Child on bike https://i.ytimg.com/vi/p6SNCvIN4EI/maxresdefault.jpg
Editor's Notes
- #18: Or to put it another way (my words), it's about making sure that what you're doing is likely to be a good idea before you put too much effort into it. How many web pages, or features, or service elements are you responsible for that are not well used, or not fit for purpose, or just basically redundant? How much does it cost you to maintain? How much does it interfere with your end users' experience? How did they come to be there, or be like that, in the first place? How much time, cost and effort went into getting it there? Is it because nobody stopped to ask why? Or because the boss said just do it? Or because what seemed like a good idea at first turned out to be not such a good idea, but by that point you were too far down a particular road?