Strategy question

You have a back-to-school deadline for a new youth feature, but legal wants stricter consent flows and safety wants more review. How would you decide what ships now versus later, who should make the call, and what launch criteria must be met?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Judgment on scoping decisions under deadline pressure without compromising legitimate safety and legal requirements.

Separate the deadline pressure from the safety requirement explicitly: a back-to-school launch date is a business goal, not a reason to relax legal consent requirements for minors.
Propose narrowing the feature's initial scope, launching a version that satisfies the stricter consent flow safety and legal want, even if it means fewer features than originally planned, rather than delaying the whole launch or skipping review.
Assign decision rights: legal and safety hold hard veto power on consent and review requirements, the PM decides which features to defer to hit the date within that constraint.
Define launch criteria in writing: the narrowed feature must pass the required consent and safety review, with a published list of deferred features for a fast-follow release.
Communicate proactively to stakeholders expecting the full feature that a phased launch protects the back-to-school date while meeting non-negotiable safety and legal requirements.

Refuses to treat a business deadline as a reason to compromise legal consent requirements, holding that line explicitly rather than treating it as a negotiable tradeoff.
Proposes scope reduction, not schedule slippage or safety compromise, as the actual lever to hit the deadline, resolving the apparent conflict cleanly.
Assigns clear decision rights, legal and safety as hard gatekeepers on consent, avoiding an ambiguous negotiation under time pressure.
Plans a fast-follow release for deferred features, showing this is a sequencing decision, not an abandonment of the original vision.

Proposing to launch the full feature on schedule with a plan to fix consent flows after the fact, which treats a legal requirement as optional.
Failing to specify who has final say, leaving the tradeoff as an ongoing negotiation rather than a resolved decision.

What would you cut from scope first to preserve the launch date?
How would you handle a business stakeholder who pushes back hard on the scope reduction?