Designing with open decisions can help increase collaboration between user experience and dev teams.
Open Decision Framework can overcome many of these obstacles.

These principles probably resonate with anyone involved in the many decisions around designing a product, feature, or service. For a designer, developers are key stakeholders in making the best design decisions. If you’re a designer, it’s time to embrace the opportunity to get diverse opinions.
This feedback saved the development team time, leaving more opportunity to address bugs, build additional features, and preserve a healthy work-life balance. The user experience remained strong, and the team was even stronger. This result would not have been possible without the early feedback from a developer with whom I had a strong working relationship.

The backend and the user experience

Set up a recurring time to collaborate: Establish a recurring time for design and development to meet between once a week and once a month. The invitation should at least include UX, lead engineering, and quality engineering. Ideally, all developers on the team should be invited to attend as schedules permit.
He mentioned that with a few minor design changes, the effort to develop it would be significantly lower. We agreed that the changes would not negatively affect the user experience, and the user would still be able to achieve their goals.

Make space for collaboration

The Open Decision Framework asserts that open decision-making is transparent, inclusive, and customer-centric. It involves clearly sharing problems, requirements, and constraints with affected parties. It enables collaboration with multiple stakeholders to secure diverse opinions and comprehensive feedback. Most importantly, it manages relationships and expectations across competing needs and priorities.

  1. Embrace a learning mindset: Avoid lecturing or “telling.” Instead, aim to learn from each other. Use mutual expertise to design and build a great experience for users and customers. Ask for explanations of unfamiliar technology or concepts.
  2. Developers are key stakeholders because a user’s product or service experience is more than just the pixels on the screen or the workflow designs. It encompasses the service’s performance, the speediness of API calls, the way user data is treated, and even the design of the data for scalability. When they’re considered full stakeholders in the design, developers can contribute their expertise on the backend and architecture of services to assist the overall design of the experience.
  3. Here is what I’ve learned to be the key factors that go into a successful user experience for a CLI project.
  4. Consider formal learning: A collaborative relationship can be easier when groups speak the same language. Consider formal learning paths, such as:
  5. A user experience (UX) designer is a stakeholder for the items the dev team is responsible for. A performance deficit, or the effects of an architecture on what data is available, can hinder the user experience. An open, collaborative relationship between dev and design allows for trust and transparency in all areas.
    • Designers: A coding foundations course, such as the open source Odin Project, can be helpful for learning the fundamentals of how a service is constructed and built.
    • Developers: An understanding of UX principles can help guide questions and feedback. You can find a good overview at UX design principles or in various books and articles.

An example of open collaboration

Encourage questions: Collaboration is the ideal scenario. Encourage all attendees to ask questions and give feedback. Answers to questions and responses to feedback are opportunities to discuss design and direction, as well as a chance to learn from one another.
An open and transparent relationship between developers and design is not as common as it should be. This way of working may be new to both sides. Here are my top five tips for making collaboration a success:
Stereotypes aside, the fates of designers and developers are forever intertwined. Here’s how to get everyone on the same page.

Your next steps

Creating an experience is a series of decisions made by a collaborative team. Product, design, and development need to work together as experts in their respective fields and stakeholders in the others. I encourage you to engage development and design for more collaborative feedback and work together to create the best product with the best user experience.

What to read next

Making open decisions in five steps

In an early design review with a developer on my team, I showed a specific interaction for displaying more data about an object. I communicated the user’s need and demonstrated the interaction when the developer asked, “Does it need to be done in exactly this way?”

3 steps to create an awesome UX in a CLI application

Collaborative, inclusive decisions lead to better results. This process can help you get there.

9 ways to improve collaboration between developers and designers

Make sharing the main agenda: UX should share the current use cases and features they are working on, along with any relevant user research data. UX designers should demonstrate workflow designs, wireframes, and high-fidelity mockups to the development team. Development should share any design decisions made on their side that may affect how the user experience works.
Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.

Similar Posts