Preparing for a scientific interaction

Preparing for a scientific meeting means knowing what this clinician already understands, what was left unresolved last time, and which of your planned points are worth raising today. Most MSLs assemble that from four systems and their own memory, the night before, and almost everything downstream depends on how well it goes.

I spend a lot of my time watching how field teams actually prepare, as opposed to how preparation is described in a process document. The distance between those two things is the largest unaddressed problem in the field medical workflow, and it is the one nobody raises, because everyone has decided it is simply what the job is.

I want to describe it honestly, including the part where preparation runs out of things it can do for you. That last part matters more to me than the rest, and it is where the measurement problem this sits inside stops being a measurement problem and becomes a question about judgement.

What does an MSL need before a scientific meeting?

Six things. Honestly, in this order.

1. What you discussed last time, and where it landed. Not that a meeting took place. What came out of it, and whether anything moved.
2. What they asked that you could not answer. This is the highest-value item on the list and the one most reliably lost. They remember asking. You are the only one who might not remember being asked.
3. What they already understand, by product and by scientific topic. So that you neither re-explain something they know well nor assume familiarity they do not have. Both errors are expensive and the second is worse.
4. What has changed since you last spoke. New data, a publication, a guideline movement, a label update.
5. Which planned scientific talking points are worth raising with this person today. A short list chosen for them, not the full set from the plan.
6. Anything about their environment. How their institution actually makes decisions, what is happening with a review committee, whether they have changed role.

Notice what is not on that list. The deck is not preparation. It is usually the first thing that is ready and the last thing that determines how the conversation goes.

Where that information currently lives

An honest audit of where those six answers actually sit.

The CRM holds that the meeting happened, roughly how long it ran, and a few sentences of free text from whoever was in the room — what happens to an insight written in free text is its own problem and it starts here. The insight log holds whatever was filed, findable only if you can guess the words someone else chose. Your own notes are the most reliable source on the list, and only if the previous meeting was yours. Email holds the follow-up you promised and whether it went. The medical plan holds the talking points, unfiltered by who you are about to see. And your memory is quietly doing more work than everything else combined.

Two things are wrong with this and neither is that the information is missing.

Nothing is joined up. Five sources, no shared key, no single view. Assembly is manual every single time.

Everything is organised by the wrong unit. The CRM organises by meeting. The plan organises by product. Email organises by date. Documents organise by document. What you need is organised by clinician, and nothing on that list is.

And the case that exposes all of it: if you inherited the account, most of the above simply does not exist for you. The notes were someone else's, the memory was someone else's, and what survived the handover is a list of dates. A knowledge position that survives a change of MSL is a separate argument, but this is where its absence is felt.

The night-before problem

Preparation happens at the last possible moment. I want to be careful about why, because the usual explanation is wrong and it is unfair.

It is not disorganisation. It is that assembling those six answers properly takes something close to an hour, and an hour does not exist in a field medical week until the meeting is tomorrow and it has to. The work gets pushed to the last available slot because that is the only slot where the pressure is sufficient to create it.

Which means preparation reliably happens when you have the least capacity for it, and it is the first thing compressed when the day has already overrun.

Two consequences follow, and both are worth naming plainly.

You prepare for the meeting rather than the relationship. The last conversation gets recalled. The three before it do not, and the pattern across all four — which is usually the interesting thing — is invisible at eleven at night.

The unanswered question is the most likely casualty. It is not in the CRM in any findable form. It is in your notes if it is anywhere. And it is the single thing the clinician is most likely to remember having asked you.

There is a quieter cost that I think is the real one. When preparation is expensive, it gets rationed — not deliberately, but because an hour each cannot be given to every meeting. The accounts that get the hour are the ones that feel important, and "important" tends to mean the relationships you already know well. So the clinicians you understand least receive the least preparation, which is exactly backwards, and no individual decision in that chain was wrong.

None of this is a discipline problem, and I do not think it is reasonable to describe it as one. An hour of manual assembly per meeting, across a full week of meetings, is not a sustainable ask and it should not be made.

What changes when preparation is assembled rather than gathered

The difference between gathering and assembly is only who does the work of putting things in one place. That sounds small. It is not.

If the record is held by clinician rather than by meeting — what they understand, what is outstanding, what moved last time, what has changed since — then most of the six answers exist before you open anything. What is left is reading them.

Four things change, in order of how much they matter.

Preparation becomes review rather than construction. Reading a prepared position and adjusting it takes a few minutes. Building one takes an hour. It is the same difference as confirming a judgement versus producing one, and it is the whole reason the hour disappears.

It survives handover. Whoever takes the account next quarter starts from where you actually got to, rather than from a list of dates and a slide deck.

Rationing stops. If preparation costs five minutes, every meeting gets it, and the clinicians you know least gain the most — which is the opposite of what happens now.

The unanswered question stops vanishing, because it was captured as an open item with a status rather than as a clause inside a paragraph nobody will reread.

One caution I would rather state than skip, because it is the thing I would ask about if I were on the other side of this. Assembled preparation is only ever as good as what was captured. A system that assembles from poor records produces a brief that looks authoritative and is wrong, and that is more dangerous than no brief at all, because you will trust it. Capture quality is the upstream problem and it does not get solved by a preparation screen.

What preparation cannot do for you

This is the part I care most about getting right.

Preparation can put the science in front of you. It cannot tell you which of those six things matters to this clinician today, in this room, given what they say in the first two minutes. That judgement is the job. It is not a gap waiting for better technology, because it depends on things that are in no record anywhere: how something was said, what was conspicuously not said, whether this is a difficult week for them.

A prepared list of points is a starting position, not an agenda. The best conversations leave it. If a system ever makes you feel you have to get through the list, it has become the thing it was supposed to prevent — which is why coverage is not a scorecard, and why what a depth measure is built from deliberately rewards a conversation that went somewhere better than the plan.

Preparation also cannot make a thin relationship deep, and it cannot make a well-informed sceptic into an advocate. It should not try. What it removes is the excuse of not knowing, and what you do with the time that frees up is still entirely yours.

I said at the start that this sits next to it measures the conversation, not you, and this is why. Both pieces are about the same commitment from the other end. The value of good preparation is not that it tells you what to say. It is that you stop spending the first ten minutes of a scientific conversation reconstructing the last one.

RocketMSL holds what is known about a clinician in one place, so that preparing for the next conversation is a few minutes of review rather than an hour of assembly. See how preparation is assembled per clinician →