I have been in enough launch rooms to know this: a Medical Affairs launch can look busy and still be unready.
The strategy is drafted. A vendor has been selected. Field hiring is underway. The publication plan is in motion. Safety processes are being written.
Then launch gets closer.
A new data point needs to change the field conversation. An unsolicited medical question may also be a potential safety event. A vendor needs a decision no one has assigned. A field insight challenges an assumption built into the launch plan.
And suddenly, everyone is asking: Who owns this?
Launch rarely breaks inside a function. It breaks where work crosses from one function, or one vendor, into another.
Every workstream may have a plan. The more important question is whether critical information can reach the right owner, trigger a decision, and come back as useful action.
When this happens | A named owner is needed for | If no one owns it |
|---|---|---|
A field insight challenges a launch assumption | Insight triage and decision-making | Insights are captured but not acted on |
An unsolicited question may be a safety event | Medical Information/PV escalation | The handoff is missed or untested |
New data become available | Scientific implications and updates | Each team updates on its own timeline |
A research idea enters through the field | IIS governance and authority | No decision reaches the investigator |
A payer needs pre-approval information | Delivery ownership and content boundaries | No clear compliant response |
Here are a few patterns I see repeatedly.
1. Owned on paper, untested in practice
Medical Information has a plan. Safety has a process. Field Medical has training. Scientific Communications has a publication plan.
The weakness appears when a question, insight, or new piece of data has to move across those systems.
Who receives it first? Who decides whether it changes a launch assumption? What needs to be updated? How does the field learn what changed? Has that flow ever been tested end to end?
A process can work in isolation and still fail at the handoff.
2. Every vendor delivers. No one integrates.
Emerging biotech teams rely heavily on external partners and for a good reason.
The risk comes when each vendor follows its own scope, timeline, and SOPs, while no sponsor-side owner is accountable for how the pieces connect.
A vendor can deliver exactly what it was contracted to do, and the organization can still be unprepared.
Outsourcing moves the work. It does not move the accountability.
3. The care pathway is part of launch readiness
An HCP can understand the data, have confidence in a product, and still be unable to get it to the patient.
The friction may be diagnostic, formulary-related, referral-based, or tied to site of care. Treatment may begin in the hospital while no practical path exists for outpatient continuation.
These are the gray zones between Medical, Access, Commercial, Patient Services, and clinical operations. They are ownership gaps too—just ones that do not show up on any org chart.
By the time this friction becomes visible, it is often treated as an execution problem rather than a care-delivery design problem.
That changes how Field Medical should be prepared for launch.
So the first question isn't when to train the field. It's this:
What does the organization still need to understand about the conditions required for this therapy to reach patients?
How does diagnosis happen today? Where do referrals stall? What determines site of care? Which patients are unlikely to make it from treatment initiation to ongoing therapy? What uncertainty do HCPs still have about the data, the workflow, or the patient pathway?
For an established therapy, some of those answers may be known. For a first-in-class product or a new treatment setting, they may not be.
Field alignment and training matter, but they cannot, on their own, solve for barriers the organization has not identified, or help the organization answer questions it has not yet learned to ask.
A CRM is not an insight system. A slide deck is not a field strategy. And a territory map is not a launch plan.
The launch-readiness test
Nothing is ever perfectly ready for launch.
Something will change. Something will fall through.
The real test is whether the team has enough clarity, ownership, and flexibility to respond without creating confusion, delay, or risk.
The Medical Affairs Launch Readiness Build Map is a seven-page resource for emerging biotech teams preparing to connect the systems, workflows, and ownership required before launch. Download the Build Map.
If your organization is preparing for launch and needs help identifying what must be connected, tested, or explicitly owned, let’s talk about your launch.
P.S. If you're on a launch team but don't own readiness, forward this to the person who does.