Join Chris Nodder for an in-depth discussion in this video Getting things done, part of Making User Experience Happen as a Team.
- Let's start by making one thing very clear,…user experience work is most likely to be a drain…on a development team's resources,…if only user experience people are involved.…That sounds like a contradiction in terms,…but here's what I mean.…If you, the user experience person,…do your work in isolation,…and then pass it on to someone on the development team…to implement, you've created extra work for that person.…They have to interpret your input…and turn it into something tangible in the product.…That most likely takes more effort…than if they just created the interaction…the way they initially envisioned it in their own minds.…
Of course given your training in interaction design…and the input you've gathered from real users,…your solution is almost definitely better…than the one that would have otherwise happened.…But still yours takes more effort,…and development teams are most often rewarded…based on some measure of time or effort.…That's one reason why development teams are often reluctant…to involve user experience people on their teams.…
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