A field rep visits a treating specialist on a Tuesday. A field reimbursement manager (FRM) calls the same office on Thursday to work through a prior authorization. A medical science liaison (MSL) follows up the next week on a clinical question the physician raised months earlier. None of the three know the other two were in the building.
In a rare disease launch, where the treating specialists for a given indication can number in the hundreds nationally, that kind of disconnection carries real cost. It is often the difference between a specialist who trusts the company and one who quietly tunes it out.
Rare disease field teams do not have the redundancy that large primary care organizations lean on. A primary care team can absorb an inconsistent message here and there across a market of thousands of prescribers. A rare disease team calling on a market measured in the hundreds cannot. Every touchpoint carries weight, and medical, commercial, market access, and patient services are often called on the same small set of accounts.
Coordination should be the operating model in this environment. Too often, training is what works against it.
How training reinforces silos without meaning to
Most launch training is still built in the way commercial organizations are structured: by function, for function. MSLs get a medical curriculum. Reps get a selling model. FRMs get access and reimbursement content. Each track is well built. Each track stops at the edge of its own role.
This pattern shows up in a few consistent ways.
- Launch readiness gets measured by completion rates within each function rather than by how well those functions work together
- Role specific content explains what a person does but rarely what happens next, or who picks up the thread once their part of the interaction ends
- Medical, commercial, and access teams each get their own narrative about the launch, built and reviewed in isolation
Pre-commercial teams launching their first product are especially prone to this. Field teams are often hired independently by function, onboarded separately, and deployed without ever sitting through a shared framework for how they are supposed to work together in the field. A field team of 30 people, every one of them new to the company and often new to rare disease, ends up individually well trained and collectively disorganized. Reps know their selling model. FRMs know their payer pathways. MSLs know their clinical talking points. None of them know how their piece connects to the other two people who might walk into the same account this month.
Building shared context without collapsing roles
Every function should keep its own depth. The FRM stays the payer expert. The MSL stays the scientific expert. What changes is the layer above that depth: a working understanding of the patient journey from start to finish, where each function’s contribution sits within it, where the handoffs happen, and what a good handoff looks like when the pressure is on.
Metrix’s cross-functional collaboration framework for rare disease launch teams gives that shared context four concrete mechanisms rather than a general aspiration to work together.
- Shared account planning, so every function calling on a hospital works from the same map of who the stakeholders are and what stage the account is at
- Call sequencing protocols, so a rep, an FRM, and an MSL are not showing up at the same office within days of each other with no coordination
- Regular cross-team intelligence sharing, so a payer objection an FRM hears on Monday reaches the rep before their Wednesday visit
- Escalation pathways for complex cases, so nobody is guessing who owns a problem that spans two or three functions at once
These are the mechanics that turn “we should work together” into a repeatable field behavior.
What this looks like in training design
Training that builds real cross-functional capability shares a few characteristics that most launch curricula skip.
It respects each person’s functional depth while making the interdependencies explicit. Reps, FRMs, MSLs, KAMs, and device trainers keep their own tracks. What each track now includes is where the role ends, who picks it up next, and what that person needs to do the handoff well.
It is built around real scenarios rather than abstractions. A scenario built around a prior authorization denial should walk through the FRM’s diagnosis, the rep’s account context, and the point where an MSL needs to weigh in on a clinical question the payer raised. Teams practice the handoff itself, not just the individual task.
It is timed to where friction actually happens. A field team launching a rare disease product hits its hardest cross-functional moments in the first 90 days. When everyone is new, the patient journey is still being worked out in real time, and there is no established playbook to fall back on. Training that only happens before launch misses the window where the coordination problem is most acute.
It gets reinforced by managers, not delivered once and left alone. Field managers need to know how to observe cross-functional behavior on a ride-along, not just whether a rep hit call volume targets. Coaching has to extend into how well someone is working the seams with the rest of the team.
Why this matters more in rare disease than anywhere else
A small field team. A narrow HCP base. Drug-device complexity on many of these products. The reimbursement complexity FRMs manage under buy-and-bill pressure. Every structural feature of a rare disease launch points back to the same fact: everyone is operating inside the same small set of accounts, so the training has to build coordination in from day one rather than adding it after the field team is already in the field.
Organizations that get this right see clear results. Messaging holds together across every touchpoint a specialist has with the company. Field issues are escalated and closed faster because everyone understands the pathway. Reps, FRMs, and MSLs walk into shared accounts with confidence instead of working around each other. And the improvisation that lean, budget-conscious teams default to when nobody has built a shared framework starts to disappear.
The question L&D leaders should be asking
Most launch readiness reviews still ask whether every function completed its training on time. A more useful question asks whether that training helped those functions work as one team once they hit the field. Rare disease launches build cross-functional excellence into the operating model itself. Training can either carry forward the silos the org chart creates, or it can become the mechanism that closes them before they cost the company a relationship with one of the few hundred specialists who matter.
