How to Bridge the Gap Between Your UX Design and Development Teams :: UXmatters

2. Invite developers and UX designers to the same sprint meetings.

Including both developers and designers in the same sprint meetings is invaluable for collaboration. Designers should be aware of developers’ schedules for tackling certain features so they can plan their design work accordingly—and vice versa. For example, if a developer hears a designer is working on designs for a certain feature, that developer might have a few thoughts about how to most easily implement it or might know of a code library to try out that would support it. This could prevent the UX designer and the entire product team having to spend time working on a second design iteration later.

Someone from a different discipline can offer fresh eyes and help teammates find a different approach when they get stuck trying to solve a problem. For example, when we held our daily Slack scrum and a remote Development-team member who participated was stuck on resolving a certain ticket, a UX designer, who was also participating in that Slack discussion, was immediately able to offer solutions to get the developer moving again.

3. Include developers in design charrettes.

A design charrette is a brief, collaborative design session during which the key members of a product team sketch possible design solutions, exploring a broad diversity of design ideas. Developers can add great value to this creative activity.

For example, one of our developers contributed a particularly unique UX design idea for a feature during a design charrette. The developer sketched out this idea because we could take advantage of a certain code library to implement it easily. The UX designers, project manager, and client would have been unlikely to think of this solution—or, if they did, might have assumed that implementing it would have required too much effort. It was a win for everyone.

4. Hold lunch-and-learn meetings.

A great way to cross-pollinate your UX Design and Development teams is through lunch-and-learn meetings. These provide chances to eat together and listen to talks on technical and design topics. Designers can learn about new technologies, features, and development best practices, all of which can spark insights they can apply to their design process. Developers get to understand more about topics such as how design tools work, what a design system is, or how usability testing helps improve the end product. Shared knowledge helps developers to work more effectively with UX designers, ensuring that they implement designs to spec and with higher quality.

Building up shared skillsets among all product-team members helps remedy a skills-gap problem that a vast majority of talent-development specialists see in their organizations. Plus, 83% of business leaders feel that their product-development investments don’t produce the greatest possible return. By bringing all team members together to solve problems, you can get the best possible results and make the most of your talent pool.

I recently gave a lunch-and-learn talk on scoping best practices. Afterward, one of our UX designers mentioned that it provided the Design team with new, useful insights into how design decisions could cause a significant scope increase for developers. While this might seem like a small realization, this is just the kind of transformative moment you should continually foster across your company by sharing knowledge.

Conclusion

The practice of having developers and UX designers work in silos must come to an end. Cross-talk between the Development and UX Design teams is not only good for the teams themselves but is also vital to delivering good outcomes for clients and the users of their products.

By implementing the four best practices I’ve presented in this article for working together and sharing ideas, you can create a culture of informed collaboration and take your mission to new heights. 

Source link