Share a concise impact statement describing what stays high quality if the delivery date remains, and what risks emerge. Propose a reduced slice that meets essential needs, with a follow‑up release scheduled. This reframes delay as stewardship, inviting partnership rather than a win‑lose standoff. Last quarter, Priya used this approach and preserved launch credibility.
Bring relevant data: throughput metrics, defect trends, customer commitments, or staffing calendars. Describe two or three credible risk paths and their mitigation costs. By grounding the conversation in shared facts, you transform pressure into a mutual problem to solve, rather than a unilateral demand to absorb.
Invite them to sketch alternatives with you on a whiteboard or doc. Name uncertainties, choose checkpoints, and define success signals. When people help design the path, they commit to it emotionally, making reminders feel like teamwork rather than policing, and keeping future negotiations warmer.