Describe a time when you had to collaborate with developers and product managers to resolve a conflicting design decision. How did you ensure the team reached consensus while keeping user needs at the forefront?

STAR + step‑by‑step strategy (120‑150 words): 1) Set context & stakeholders. 2) Use CIRCLES to gather user & business data. 3) Facilitate a design sprint workshop to surface trade‑offs. 4) Iterate prototypes, collect quick feedback. 5) Document decisions & next steps. 6) Validate with metrics.

I was tasked with resolving a disagreement between developers, who preferred a flat navigation, and product managers, who wanted a hierarchical menu. First, I mapped the stakeholders and clarified each side’s constraints. Using the CIRCLES framework, I collected user journey data, pain points, and business goals. I then organized a 2‑hour design sprint workshop where we sketched three navigation prototypes. We ran rapid usability tests with 12 users, measuring task completion and satisfaction. The data showed a 20% higher completion rate for the hierarchical prototype. I documented the decision, shared the test results, and set up a 12‑week KPI to monitor support tickets. The outcome was a 15% reduction in navigation‑related tickets and improved stakeholder alignment.