I've been on teams with minimal interaction between dev and UX, where the UX team would throw a design over the wall. These were not great experiences and led to frustration on both sides.
I've also been on teams where we work very closely with UX and they are a part of all our agile ceremonies, etc. They were a core team member of the team.
The latter experience was on a mobile team. We would review the proposed designs as a team, make comments on potential navigation issues, or non-standard UI elements for our platform. There was some give or take here on both sides.
Once we were in general agreement the dev teams would start their implementation work.
Then we had a bi-weekly meeting for both platforms where a rotating engineer would meet with the team's UX team member (UX-Palooza) for 30 minutes. They would come prepared with a list of small UI issues they saw that they wanted adjusted. Minor alignment issues, font issues, etc. Things that were too small to bother writing up tickets for. The developers would try to fix everything live while sitting with the UX team member and if anything seemed like it would take more than a couple minutes we would create a story.
I feel like this model worked really well. The one "drawback" is that the UX team member identified more with the product development team than their UX peers who didn't operate like this. I feel like it may have caused some friction between the UX team member and their broader UX organization.
Yum! Brands | Plano, TX & Chicago, IL | Onsite | Full Time
Our Company:
We are building one of the largest restaurant e-commerce platforms in the world. It will eventually help power the digital properties of Pizza Hut, KFC and Taco Bell across 50,000 restaurants in 145 countries.
The e-commerce platform is a microservice architecture built on Kubernetes and deployed to AWS. These roles would help lead, develop and test these services as we continue to expand our deployment.
I've also been on teams where we work very closely with UX and they are a part of all our agile ceremonies, etc. They were a core team member of the team.
The latter experience was on a mobile team. We would review the proposed designs as a team, make comments on potential navigation issues, or non-standard UI elements for our platform. There was some give or take here on both sides. Once we were in general agreement the dev teams would start their implementation work.
Then we had a bi-weekly meeting for both platforms where a rotating engineer would meet with the team's UX team member (UX-Palooza) for 30 minutes. They would come prepared with a list of small UI issues they saw that they wanted adjusted. Minor alignment issues, font issues, etc. Things that were too small to bother writing up tickets for. The developers would try to fix everything live while sitting with the UX team member and if anything seemed like it would take more than a couple minutes we would create a story.
I feel like this model worked really well. The one "drawback" is that the UX team member identified more with the product development team than their UX peers who didn't operate like this. I feel like it may have caused some friction between the UX team member and their broader UX organization.