Formative usability testing is a variation on usability testing that can be used as a fast design tool. As we practice it at our company, it features unorthodox usability testing methods, such as: changing the prototype between each test session, ignoring many details and most quantitative data, and not writing a test report. This presentation will show interaction designers how to use formative usability testing to get to optimal UI designs as quickly as possible. Attendees should be completely familiar with “standard” usability testing practices.
Author(s): John Schrag
Published in: Proceedings of the Usability Professionals’ Association Conference 2006
Published date: 6/15/2006
As more organizations adopt agile development practices, UX practitioners want to ensure that the resulting products are still designed with users in mind. This tutorial teaches basic, proven methods to integrate user-centered design practices into agile teams.
This tutorial is for experienced UX practitioners and managers who work on agile teams, or who will be transitioning to agile. Prior experience with agile methods is unnecessary, and the course does not focus on a particular agile methodology.
The morning session teaches new skills for planning design on agile teams, and the afternoon session focuses on agile adaptations to usability testing and research methods. Research methods covered in this tutorial focus on eliciting observed user behavior (such as contextual inquiry, and formative usability testing).
GOALS FOR THE SESSION:
Participants in this tutorial will learn:
• advantages of a healthy agile UX practice over waterfall UX
• skills and attitudes to hone to do user-centred design on an agile team
• common errors when transitioning from waterfall to agile
• skill and activities that UX brings to the ‘Product Owner’ role on an agile team
• activities and best practices during Sprint Zero to increase a team’s success
• parallel-track/staggered sprint timing of agile UX activities
• how to hold a “big picture” of design without committing the agile deadly sin of Big Design Up Front
• how to break both UX work and design implementation into sprint-sized chunks
• tactics for incorporating user research into agile projects
• some suggestions for improving non-co-located agile teamwork
This tutorial is intended for practitioners who have come to interaction design from a research, psychology, information architecture, or other non-design background. It focuses on what happens after the requirements are done and before you build your first prototype. Design fields such as graphic arts, architecture, and industrial design have long-standing practices for innovative design, and these apply well to interaction design.
Author(s): Ian Hooper; John Schrag
Published in: UPA 2008 Conference
Published date: 6/17/2008
A user experience goal is a choice made by your product team about what kind of experience you want your users to have with your product or service. You use these choices to measure and direct the design of your product.Goals let us know when our tasks are complete, so that we can move on to something else. They stop us from obsessing over the wrong details and help us direct our energies to what is important. Goals tell us what to measure, and what can be ignored.
Author(s): John Schrag
Published in: User Experience Vol.7, Issue 1
Published date: 2/1/2008