During a rotation you are asked to take an urgent task that conflicts with a deadline already promised by another team that depends on your work. How would you handle the competing priorities, communicate with stakeholders, and decide what to deliver?

If I'm handed an urgent task that conflicts with an already-promised deadline, I first pause to quantify both pieces: scope, risks, and time-to-deliver in hours. Within an hour I’d surface a clear, data-driven choice to both stakeholders — for example, “I can finish the urgent fix in 6–8 hours, or deliver the dependent team’s API contract by the agreed date in 24 hours.” I then propose pragmatic options: ship a critical subset (MVP) that preserves 80–90% of downstream functionality, reassign the urgent work to a teammate, or push the dependent deadline with a new concrete date. I update the ticket, call a 15-minute alignment sync, and escalate only if there’s no agreement. In a previous rotation with a 5-person team I used this approach and avoided a full re-plan, delivering the critical path artifact on time and resolving the urgent request within 48 hours.