Defending Design Decisions and Building a Plan B

Learners will apply negotiation strategies to defend research-based design decisions and collaboratively construct alternative solutions when technical constraints arise. This capability allows you to maintain user experience integrity while satisfying developer and stakeholder needs during post-handoff collaboration. Learning Objective: By the end of this lesson, learners will be able to apply negotiation techniques to defend research-based design decisions and collaborate on alternative solutions when partners propose changes impacting user experience. Transcript Grounding Defense in Research The moment a downstream partner proposes a change that negatively impacts the user experience, your defense must be rooted in the research you conducted. This research serves as the basis of defense, providing the concrete evidence that the proposed solution is necessary. You are not just defending a preference; you are validating a user need. The objective is to use negotiation skills to convince partners that the proposed user experience is feasible and necessary. This context often arises when stakeholders claim a solution "can't" be done, forcing you to bridge the gap between technical constraints and user requirements. You must be prepared to defend decisions or collaborate on alternatives. [pause:1s] Grounding your position in data transforms the conversation from subjective opinion to objective fact. This foundation allows you to engage in meaningful dialogue rather than defensive posturing. When you connect your defense to the research, you create a shared reality for the team. This shared understanding is the starting point for building a viable Plan B. Key Points: Design decisions must be grounded in the research conducted by the UX designer to serve as the basis of defense The objective is to use negotiation skills to convince partners that the proposed user experience is feasible and necessary This context occurs when downstream partners propose changes that negatively impact the user experience or when stakeholders claim a solution 'can't' be done The Plan B Collaboration Protocol When a stakeholder or partner states that a specific design element or feature cannot be done, that moment triggers the Plan B protocol. The UX designer must be prepared to immediately propose an alternative solution. This is not a time for defending the original vision in isolation. Instead, the goal is to apply the Plan B protocol to propose alternative solutions when stakeholders claim a feature cannot be done. You use negotiation skills to work with partners to create a satisfactory Plan B that meets as many of everyone’s needs as possible. This collaborative approach ensures the user experience remains intact or is adapted in a way that satisfies both technical constraints and user needs. The objective is to find a path forward that respects the technical reality while preserving the core user value. Key Points: Trigger: A stakeholder or partner states that a specific design element or feature 'can't' be done Action: The UX designer must be prepared to immediately propose an alternative solution (Plan B) Collaborative Approach: Use negotiation skills to work with partners to create a satisfactory Plan B that meets as many of everyone’s needs as possible Goal: Ensure the user experience remains intact or is adapted in a way that satisfies both technical constraints and user needs Post-Handoff Advocacy Responsibilities The work doesn't stop when you hand over the files. Many designers assume their role is finished once knowledge transfer is complete, but that’s a common mistake. Your post-handoff responsibility is ongoing, and it demands you stay en