A regulated launch cannot advance on schedule alone, so I connected the evidence that let it proceed.
Amgen · Repatha Launch
Challenge
Every requirement in a regulated multichannel launch needs a test, an accountable owner, a documented exception where it fails, and evidence of approval. Held in separate places, that record cannot be read as a whole, and leadership is asked to approve a release without being able to see what passed, what remains open, and who accepted which risk.
Action
Making the launch's evidence readable in a single pass was the job. Requirements, test scenarios, expected results, actual results, defects, owners, and release gates were aligned across the launch workstreams so each could be traced to the others — a requirement to its test, a failure to the person resolving it, an exception to whoever accepted it. The Validation Evidence Package carried that trace. Completing the validation report, resolving exceptions, and approving release were sequential gates rather than parallel claims, which is what stopped schedule pressure from quietly standing in for evidence.
Result
Program leadership received a clear record of what had passed, what remained open, who had accepted which risk, and whether the launch could proceed — as one package rather than an assembly of separate assurances. The release decision rested on traceable evidence, and an exception that had been accepted was visible as a decision with a name against it.
