Launch Control

Designing a product decision game

Design intent

Launch Control turns the ambiguity of leading a live game into a short decision simulation. Each scenario asks the player to connect a clear problem with supporting metrics, hear competing stakeholder perspectives, and make a credible product choice. Team energy represents development bandwidth, so a strong decision must protect both the game and the people operating it. The intent is to reveal how the player reasons through tradeoffs, not whether they can guess a hidden correct answer.

Design approach

The experience follows one consistent loop: understand the problem, inspect the evidence, hear the team, choose a response, and observe what changes. The interface reveals information in that order so the player can form a point of view before seeing the available decisions. Beneath that visible loop, each choice updates product metrics, changes team energy, and records state that can reshape later scenarios. The final recap connects outcomes to specific decisions and remaining capacity, turning the run into useful feedback.

What the simulation teaches

Launch Control teaches that product management is not the search for one universally correct answer; it is the practice of making a clear decision with incomplete evidence and accepting the tradeoffs. Players learn to connect qualitative feedback with operating metrics, prioritize the highest-leverage problem, and protect team capacity instead of treating every issue as an emergency. Carry-forward effects show how short-term wins can create future constraints, while the final recap makes the quality of each judgment visible. That reflects my experience with major product releases, where timelines are limited and time matters: leaders must decide what to solve now, what to defer, and how to preserve enough capacity to respond after launch.