Join Chris Nodder for an in-depth discussion in this video The danger: Too much work, part of Making User Experience Happen as a Team.
- Say you turn out to be really good…at communicating the value of the work you do…and all of a sudden, too many teams want your involvement.…What can you do?…You have a set user experience team size,…and having them work over time is not a sustainable solution…so you have to work out which teams you'll support…and which ones you won't,…and how you're going to still keep everyone engaged…in thinking about user experience.…Let's consider the criteria you'd use to decide…whether to work with a team or not.…There are a couple of factors that might be important here.…
First, are there any high cost, high visibility projects…in relatively untested areas?…Those have a high potential risk to the company,…so they definitely benefit from a large degree…of user experience help.…So too, do maintenance projects that will change…a piece of user experience that's used by many people.…The cost of messing up in the situation is high,…so there's a good justification for…user experience involvement.…Apart from the strategic reasons,…
In this practical course, look at what it takes to help systemizers to empathize, and how you can best integrate with development teams, communicate the value of UX to business-oriented team members, and cultivate executive champions. Upon wrapping up this course, you'll have a better understanding of how to help your colleagues grasp the importance of user experience—which, in turn, can help make design decisions a bit easier.
- Integrating with development teams
- Owning the user experience
- UX as a brand
- Resources for teams you can't help
- Speaking from data, not opinion
- Influencing without authority
- Cultivating executive champions
- Justifying your budget