Agile Prague 2016 - UX is team work
The document summarizes Mariana Morris's presentation at Agile Prague 2016 on the importance of teamwork in UX design. Some key points discussed include: - UX design requires collaboration between designers, developers, and other roles to understand user needs. Isolating roles is not an option. - Techniques were presented for getting the whole team involved in user research through activities like ethnographic research, user interviews, and usability testing. - An effective process involves sharing work early, using tools like user flows and product canvases, and conducting stakeholder workshops and retrospectives to improve. - Providing and receiving feedback requires clear communication and focusing on research and goals rather than personal preferences.
Agile Prague 2016 - UX is team work
- 1. Agile Prague, 2016 Mariana MorrisUX is team work! Mariana Morris @MarianaMota
- 4. Are you crazy? I can’t do that! ” - developer “ @MARIANAMOTA
- 5. This looks nothing like the design I made! ” - designer “ @MARIANAMOTA
- 7. Designing or developing in isolation is not an option. @MARIANAMOTA
- 9. @MARIANAMOTA
- 10. @MARIANAMOTA
- 12. Techniques to get your team involved in user research @MARIANAMOTA
- 18. ETHNOGRAPHIC RESEARCH Oxford Computer Consultants running user interviews for National Grid@MARIANAMOTA
- 19. Mariana UX Designer Mark Project Manager Reynold Account Manager Tim Developer ETHNOGRAPHIC RESEARCH Oxford Computer Consultants running user interviews for National Grid@MARIANAMOTA
- 20. Paul Support and training Mariana UX Designer Ant User USER INTERVIEW Oxford Computer Consultants running usability testing at Bath & North East Somerset Council@MARIANAMOTA
- 21. USER RESEARCH STREAMED BACK TO THE OFFICE @MARIANAMOTA
- 22. @MARIANAMOTA
- 23. It’s not what users want. @MARIANAMOTA
- 24. It’s not what users want. It’s what users need. @MARIANAMOTA
- 25. @MARIANAMOTA https://en.wikipedia.org/wiki/Alan_Cooper#/media/File:AlanCooper.jpg Alan Cooper Pioneer in interaction design
- 27. @MARIANAMOTA
- 28. User flow QUESTION - MISSING - IDEA @MARIANAMOTA
- 30. User groups User flow Sketches Sprint goal Sprint tasks MetricsProject goal @MARIANAMOTA
- 37. Verbal communication: Facilitator & Leader
- 38. Facilitator language • Warm and neutral • Active listening • Passive and inclusive tone “How about…” “Maybe we can…” “What if…” @MARIANAMOTA
- 39. Leader language • Competence • Expert • Direct and muscular language “That’s absolutely right, and here’s why…” “I completely agree because…” “This is my plan…” @MARIANAMOTA
- 41. When asking for feedback: • State clearly: Where you are at What you expect feedback on • Ask clear questions • Explain the rationale for your decisions @MARIANAMOTA
- 42. When giving feedback: • Ask the current status of the design • Question first. Comment last. • Explain technical challenges • Don’t refer to your personal taste. Refer to the briefing and user research. @MARIANAMOTA
- 43. Avoid: “I don’t like it.” “Can’t do it” (without explaining why) @MARIANAMOTA
- 44. Go back to the brief. Gerry Leonidas in an interview for Talking Design
- 45. “Give it 5 minutes.” https://signalvnoise.com/posts/3124-give-it-five-minutes
- 46. “If someone loses, you did it wrong” When negotiating… http://www.artofmanliness.com/2011/05/11/how-to-haggle- like-your-old-man/
- 47. Let’s not settle. We work with technology. It’s always changing. This process will change.
- 48. So, Let’s keep meeting up, discussing, improving.
- 49. So, Let’s keep meeting up, discussing, improving. Regularly.