Scope cuts under a deadline, launch readiness, working with engineering, and handling a slipped date.
3 questions in Product Management.
Find out what the date is being used for, then commit to something you can actually control — a timeboxed discovery end, a date for the date, or a narrow first slice — and never issue a single-point estimate for scope that is still undefined.
Find out what the six weeks is made of before negotiating anything, then choose between cutting scope, splitting the release, launching to a limited cohort and moving the date — and tell everyone who depends on the date the same day you know.
Re-plan around the dependency before you escalate: price the delay, find the smallest thing the other team could give you, and design a version that ships without them. Escalate only with a costed choice between two named options, and never as a complaint about the other team's judgement.