Slashing Risks with User Experience Engineering (Part 3)

Dmitri is a User Experience (UX) and Interaction Designer in Toronto.

  Agile   Applications Delivery   Information Technology   Quality   Requirements Management   Risk Management   Testing/Test Management  

This is the third installment in my series on using the latest UX methods for focusing on the right problems and slashing requirements-based risks. In the first article, we looked at the seven key UX activities involved in collecting accurate insights, modelling and validating our designs. Part 2 focused exclusively on the key differences of modern user research methods from traditional requirements-gathering activities.

As I mentioned in the previous article, we never want to ask business users what they want or have them design apps for themselves. We could only get accurate information by asking them what they don't want and what problems are they struggling with. Once we learn about their situation and conduct planning, we will have our professional designer build a prototype and then validate it by watching users go about their daily tasks using our prototype--and see what works.

Before we jump into the content of this article, let me remind you that the sole purpose of this series is for you to get the practical tools that will immediately benefit you and your teams in your current project. So if you have a question or comment, if anything is missing or unclear or you'd like to see more information on anything else related to requirements or risk management, please scroll down and leave me a comment now while it is still fresh in your mind (or send me a …

Please log in or sign up below to read the rest of the article.