Join Chris Nodder for an in-depth discussion in this video Earning respect, part of Making User Experience Happen as a Team.
- Development teams respect actions rather than words.…If you want to be taken seriously, you need to…demonstrate ownership and commitment…rather than just peripheral involvement.…That can be hard when you're sharing your workload…between multiple teams.…But for the period of time when you're focused…on a specific team, you need to be truly present.…Don't just raise usability and design bugs,…own them, and see them through to resolution.…Don't just flag things as an issue,…but help provide a solution, too.…
That might mean sitting with the developer…while they make changes to the code,…or it might mean getting in there…and creating the updated CSS file.…It really doesn't mean just emailing an image…of how the interface should look.…That's highly open to interpretation…and it's extra work, rather than less work,…for the development team.…If you show that you're willing to take on the work…to back up your proposed changes,…you're more likely to be able to get designs seen…as an acceptance criteria.…The first step is really simple.…
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