UX process should be a series of activities that can be mixed-and-matched to build the right process for a given project and team. The same UX activities won't work the same every time, learn to be flexible!
for UX design. • Rigid approaches to UX processes do not account for differences in teams, clients and projects. • UX is about recognizing the essential humanity of software. • Our processes should reflect the humanity of our teams and account for those differences. • A one-size-fits all approach will not work all the time. PREMISE
needs. • Answer the highest-risk questions for your product as efficiently as possible. • Decide where to draw the line. How much research is enough? THE CHALLENGE
• All UX activities are not created equal • different learning • about different constituencies • for different phases of development and • for different types of projects. UX ACTIVITIES
and methods for learning how to accomplish them. User Interviews • Research Phase • Collects initial user guidance. • Can be on your own or with your team for buy-in. UX ACTIVITIES
trees. Personas • Research Phase • Helps team gain perspective about customers. • Great for empathy, but can seem abstract on the surface. UX ACTIVITIES
visual representation of your product. Prototype Testing • Testing and Validation Phase • A relatively low-cost interactive representation of your product.
to document. • There is no absolute right amount of documentation; it depends on the situation. DOCUMENTATION • Keep your focus on what you’re making, not writing about what you’re making. • Break down tasks into detailed chunks when it feels right.
in terms of “Agile,” “Waterfall,” or “Lean.” • These labels are useful, but UX doesn’t fit neatly into any of these methodologies, and it shouldn’t. THE POINT