How would you run go/no-go reviews for a risky multi-team launch?

Instruction: Design a scalable operating model. Be explicit about governance, tradeoffs, escalation paths, and how the system stays useful over time.

Context: Tests whether the candidate can design a scalable PM operating system that remains useful under complexity, politics, and growth.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would structure go/no-go reviews around explicit launch criteria defined before the release is emotionally committed. Every team should know the readiness checks, open risks, fallback plan, owner, and what threshold turns a concern into a stop signal. If those rules...

Related Questions