A dose of user research: techniques to get the team involved in the UX design process (UX in the City: Oxford, 2016)
4 likes1,575 views
The document discusses the importance of collaboration between designers and developers in a project, emphasizing that isolation is not an option. It highlights best practices for communication, feedback, and user research, stressing the need for early and ongoing user engagement throughout the project lifecycle. Additionally, it encourages continuous improvement and adapting to changes in technology, urging teams to regularly meet and discuss progress.
A dose of user research: techniques to get the team involved in the UX design process (UX in the City: Oxford, 2016)
- 2. @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
- 10. @MARIANAMOTA
- 11. @MARIANAMOTA
- 12. @MARIANAMOTA
- 14. oxfordcc.co.uk
- 16. @MARIANAMOTA
- 17. @MARIANAMOTA
- 20. @MARIANAMOTA
- 24. ETHNOGRAPHIC RESEARCH Oxford Computer Consultants running user interviews for National Grid@MARIANAMOTA
- 25. Mariana UX Designer Mark Project Manager Reynold Account Manager Tim Developer ETHNOGRAPHIC RESEARCH Oxford Computer Consultants running user interviews for National Grid@MARIANAMOTA
- 26. Paul Support and training Mariana UX Designer Ant User USER INTERVIEW Oxford Computer Consultants running usability testing at Bath & North East Somerset Council@MARIANAMOTA
- 27. USER RESEARCH STREAMED BACK TO THE OFFICE @MARIANAMOTA
- 28. @MARIANAMOTA
- 30. @MARIANAMOTA
- 31. User flow QUESTION - MISSING - IDEA @MARIANAMOTA
- 32. QUESTION - MISSING - IDEA @MARIANAMOTA
- 33. User flow Wireframes QUESTION - MISSING - IDEA @MARIANAMOTA
- 36. User groups User flow Sketches Sprint goal Sprint tasks MetricsProject goal @MARIANAMOTA
- 44. Verbal communication: Facilitator & Leader
- 45. Facilitator language • Warm and neutral • Active listening • Passive and inclusive tone “How about…” “Maybe we can…” “What if…” @MARIANAMOTA
- 46. 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
- 47. 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
- 48. 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
- 49. Avoid: “I don’t like it.” “Can’t do it” (without explaining why) @MARIANAMOTA
- 50. Go back to the brief. Gerry Leonidas in an interview for Talking Design
- 51. Designers need to know the ‘why’s.
- 52. How many designers does it take to change a light bulb?
- 53. Answer: Does it have to be a light bulb? How many designers does it take to change a light bulb?
- 54. “Give it 5 minutes.” https://signalvnoise.com/posts/3124-give-it-five-minutes
- 55. “If someone loses, you did it wrong” When negotiating… http://www.artofmanliness.com/2011/05/11/how-to-haggle- like-your-old-man/
- 58. Jira
- 59. Trello
- 60. Trello
- 61. Sqwiggle
- 62. But let’s not settle.
- 63. But let’s not settle. We work with technology.
- 64. But let’s not settle. We work with technology. It’s always changing.
- 65. But let’s not settle. We work with technology. It’s always changing. This process will change.
- 66. So, Let’s keep meeting up, discussing, improving.
- 67. So, Let’s keep meeting up, discussing, improving. Regularly.