By Dashiel Neimark Published: April 11, 2016 “Is the team in a panic and scrambling for a magic UX pill? Or does a consistent intake of UX nutrients support the team’s process?” No, this headline isn’t a joke about the increasing popularity of the term Lean UX. Rather, I am talking about the choices that organizations make in deciding how to adopt User Experience as a practice and improve the experience they are attempting to create. Do they apply User Experience through intermittent, quick fixes to rectify gaps in an experience? Or do they foster UX practices from beginning to end, throughout a development cycle? Is the team in a panic and scrambling for a magic UX pill? Or does a consistent intake of UX nutrients support the team’s process? The UX Diet The UX diet is all about preventative measures. One easy way to identify a team that has a steady UX diet is to see at what point they inject UX into their overall development process. If they involve user researchers and experience designers during a project’s discovery phase, that’s a positive sign. Involving User Experience in the generation of requirements rather than just the amendment of those requirements typically results in reducing the need for such amendments. In contrast, if a team hires a UX professional for a last-call, polish-it-off sort of engagement, the UX diet is likely absent. The driving force behind the UX diet is ensuring more precise, consistent validation of the direction a team is taking. It requires a long-term outlook.
from UXmatters http://ift.tt/1YoVDuM
via IFTTT
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.