# Designer collab

# Definitions

Developers - Individual contributors creating any level of technical infrastructure that makes up the application and/or system. Designers - In this text, designers are most similar to Product Owners representing the Business Unit's requests and needs, as well as communicating them to the team for the developers to implement.

# Design Requirements Guidelines

1. Clear and Concise Language: Use simple, unambiguous language to describe the design requirements.
2. Specific Acceptance Criteria: Requirements must be as specific as possible, achievable and relevant.
3. Testable Requirements: Ensure design requirements are testable, allowing developers to verify that the implementation meets the design intent.
4. Visual Aids and Prototypes: Provide visual aids like wireframes, mockups, or prototypes to help developers understand the design vision and requirements.
5. Prioritize Requirements: Prioritize design requirements based on business goals, user needs, and developer feedback about the cost. This helps developers focus on the most critical features and functionalities.

# Roles and Responsibilities

1. Designers Focus on "What": Designers focus on defining the problem, identifying the requirements, and detailing the desired user experience. They should not specify "how" the solution will be implemented.
2. Developers Own the "How": Developers are responsible for choosing the technical solution, architecture, and implementation details. Designers should not dictate specific technical solutions or architectures.

# Collaboration Best Practices

1. Regular Communication: Establish regular communication channels between designers and analysts to ensure that requirements are clearly understood and any questions or concerns are addressed. Developers may be included in the discussion after the initial problem is fleshed out.
2. Active Listening: Encourage active listening between designers, analysts and developers to ensure that requirements are understood between all parties and implemented correctly.
3. Collaborative Problem-Solving: Foster a collaborative environment where designers and developers work together to solve problems. However, designers should focus on the "what" and developers should focus on the "how".
4. Respect Boundaries: Respect the boundaries between design and development. Designers should not dictate technical solutions, and developers should not disregard design requirements.

# Expectations

1. Technical Feasibility: Developers will evaluate requirements and provide feedback on the technical and cost impact of the overall system(s)
2. Design Systems and Style Guides: Developers will establish and maintain a design system and style guide to ensure consistency across the application.

By following these guidelines, designers and developers can work together more effectively, ensuring that design requirements are implemented correctly and that the final product meets both design and technical requirements.