Medical science liaison metrics: tracking strategic impact

A calendar full of meetings, a generous count of KOL interactions, and a dashboard glowing with green activity indicators can create excellent optics. They can also conceal a function that is producing very little strategic value.

The uncomfortable data is familiar by now: only 40% of Medical Affairs organisations in a global survey reported that they actively measure MSL impact. Meanwhile, 76% identified the definition and measurement of activity quality as a primary challenge, and 61% acknowledged relying on quantitative standards that do not reflect the actual value of the work.

This is not a data shortage. It is a design failure.

I have seen medical science liaison performance metrics treated as if the field team were a delivery service: count the visits, count the accounts, count the follow-ups, then congratulate everyone for operational excellence. The model is tidy, auditable, and almost entirely inadequate. An MSL is not paid to accumulate conversations. The function exists to improve scientific understanding, surface relevant external insight, support evidence generation, and help the organisation make better medical decisions.

That is harder to count. It is also the work that matters.

The failure of quantitative standards

The traditional MSL scorecard usually begins with activity volume. A liaison may be expected to maintain a network of 35 to 45 active KOL relationships, complete a certain number of interactions, document field insights, and support internal requests. None of these measures is inherently useless. The problem starts when they become a substitute for judgement.

A target such as 35 to 45 KOL relationships can be a reasonable planning reference. It may help a team think about territory coverage, scientific relevance, and workload. It becomes a poor performance metric when it assumes that every relationship has equal value, requires equal attention, or produces equal insight.

A ten-minute exchange with a highly relevant investigator may alter a clinical development assumption. A long series of routine meetings may produce nothing beyond polite agreement and another entry in the CRM. If both interactions receive the same credit, the system rewards motion rather than contribution.

The same problem appears in visit frequency. Frequent engagement can indicate a productive scientific relationship, but it can also indicate a weak engagement strategy—one that confuses access with influence and repetition with depth. MSL activity tracking best practices should therefore distinguish between:

• the number of interactions completed;
• the relevance of the stakeholder to the current medical objective;
• the scientific substance of the discussion;
• the quality of the insight captured;
• the action taken as a result;
• the eventual contribution to a medical or evidence-generation priority.

The last three are where many dashboards become strangely quiet.

A full calendar proves that an MSL was busy. It does not prove that Medical Affairs became wiser.

Quantitative metrics survive because they are convenient. They are easy to define, easy to compare, and easy to insert into a quarterly business review. Quality metrics demand context. They require a clear medical strategy, disciplined insight taxonomy, and managers willing to assess work rather than count it. In other words, they require management.

What activity metrics can—and cannot—tell you

Activity data still has a place. It can reveal coverage gaps, uneven workload distribution, unaddressed priority accounts, or a team spending too much time with stakeholders who no longer match the product lifecycle. The mistake is not using activity metrics. The mistake is treating them as evidence of impact.

This distinction matters because a metric can be accurate and still be strategically misleading. The number may be correct. The conclusion drawn from it may not be.

A four-pillar framework for MSL performance

A more credible approach combines activity data with evidence of scientific contribution. A recognised four-pillar model provides a useful starting point:

1. interaction quality;

2. project-based scientific outputs;

3. external KOL satisfaction;

4. internal stakeholder satisfaction.

The model is not a magic formula. It is a practical correction to the usual one-dimensional scorecard. It acknowledges that field medical value appears in several places—and not all of them are visible in a visit log.

1. Interaction quality

Interaction quality should assess whether an engagement had a clear scientific purpose and produced meaningful dialogue. That does not mean demanding a rigid agenda for every conversation; science is not a call-centre script. It does mean distinguishing a substantive exchange from a ceremonial touchpoint.

A useful assessment can examine:

• whether the stakeholder was selected for a defined medical reason;
• whether the discussion addressed a relevant evidence or clinical-practice question;
• whether the MSL demonstrated scientific preparation;
• whether the conversation generated a new perspective, challenge, or clarification;
• whether the follow-up action matched the discussion;
• whether the interaction strengthened the organisation’s understanding of the external environment.

This is where manager calibration matters. If one manager rates every well-documented meeting as high quality while another expects evidence of a strategic outcome, the framework becomes another exercise in local interpretation. Teams need shared definitions, examples of strong and weak insight reports, and periodic review of scoring consistency.

The aim is not to turn every scientific exchange into a bureaucratic examination. It is to stop rewarding interactions that exist primarily to make the dashboard look healthy.

2. Project-based scientific outputs

The second pillar captures work that may not generate a large number of individual engagements but still affects important Medical Affairs priorities. Examples include support for an advisory board, contribution to an investigator-initiated research process, development of a medical education initiative, or structured input into a real-world data programme.

Project metrics should focus on contribution and usefulness rather than ownership theatre. Medical Affairs is full of initiatives where several functions contribute, and the loudest person in the meeting is not automatically the person who created the value.

Possible measures include:

• whether the MSL contributed relevant external scientific insight to project design;
• whether field input changed a protocol, educational objective, or evidence question;
• whether the project met its defined scientific milestones;
• whether stakeholder recruitment reflected the medical strategy;
• whether the output addressed a documented knowledge or practice gap;
• whether lessons from the project were transferred into future planning.

This approach also prevents a common category error: measuring all MSL work through personal engagement counts when some of the most valuable work is collective, longitudinal, and project-based.

An MSL who identifies a recurring clinical evidence gap, helps shape a viable research question, and supports the right investigators may create more strategic value than an MSL who completes twice as many routine meetings. The latter looks better in a simplistic report. The former improves the medical plan.

3. External KOL satisfaction

External feedback offers a useful counterweight to internal assumptions. In a global evaluation survey, 52% of respondents supported using KOL engagement impact scores as a performance metric. That preference reflects a sensible principle: if the function claims to build trusted scientific relationships, the people in those relationships should have some voice in evaluating their quality.

KOL satisfaction should not become a popularity contest. High satisfaction can reflect convenience, responsiveness, or personal rapport without demonstrating scientific value. A well-designed survey therefore needs to assess the substance of the relationship.

Questions might explore whether the MSL:

• provides scientifically relevant and balanced information;
• understands the KOL’s clinical or research priorities;
• facilitates useful scientific exchange;
• follows up appropriately;
• contributes insight rather than simply distributing company materials;
• operates with credibility and appropriate compliance boundaries.

The survey should also account for the fact that KOL expectations differ by context. An investigator involved in early development may value rapid scientific dialogue and evidence-generation support. A clinical specialist later in the product lifecycle may need nuanced discussion of emerging data, treatment pathways, or implementation challenges. One generic satisfaction score will flatten those differences into a number with the emotional depth of a hotel Wi-Fi rating.

4. Internal stakeholder satisfaction

The fourth pillar examines whether the MSL function is useful to colleagues in Medical Affairs and related teams. Internal satisfaction does not mean asking whether everyone enjoyed working with the field team. It means evaluating whether the team delivered relevant, timely, and trustworthy scientific intelligence.

Internal stakeholders may include medical directors, scientific communications teams, clinical development, health economics and outcomes research, safety, medical information, and regional Medical Affairs leadership. Their questions are different from those of external stakeholders:

• Did the insight arrive in time to influence a decision?
• Was it specific enough to use?
• Did the MSL distinguish an isolated opinion from a recurring signal?
• Did the field report clarify a clinical-practice issue?
• Did the team close the loop with the stakeholder?
• Did the information improve planning or reduce avoidable rework?

This is also where organisations need to confront their own behaviour. If internal teams request field insights, ignore them for three planning cycles, and then complain that MSL reports lack impact, the performance problem may not be located in the field. Medical Affairs value depends on an operating model capable of receiving, interpreting, and acting on what the field learns.

Lifecycle-specific metrics are not optional

The right KPI for an MSL depends heavily on where the product sits in its lifecycle. Applying one permanent scorecard across early development, pre-launch, and launch is a reliable way to create irrelevant targets—and then blame the field for missing them.

Early-phase development

In early development, the central question is often whether the organisation understands the clinical landscape well enough to make sound evidence decisions. Relationship-building matters, but the purpose is not to collect prestigious names for a slide deck.

Useful measures may include:

• the quality of the thought-leader map;
• identification of relevant clinical and research gaps;
• advisory board contribution and follow-through;
• quality of feedback on the development programme;
• support for investigator-initiated research discussions;
• identification of potential evidence-generation partners;
• clarity of recurring objections or unmet needs in the treatment landscape.

The emphasis should be on learning. Early-phase field medical work may have limited visible output because the function is reducing uncertainty rather than promoting a finished proposition. That is strategically valuable, although it does not always photograph well in a quarterly dashboard.

Pre-launch

Before launch, MSL performance metrics should reflect the need to understand frontline expectations, prepare scientific dialogue, and identify barriers to appropriate clinical use. Visit frequency may become more relevant, but it should serve a purpose rather than operate as a quota in disguise.

Measures can include:

• engagement with priority stakeholders identified in the medical strategy;
• quality and consistency of front-line insights;
• readiness of scientific exchange plans;
• identification of evidence gaps likely to affect adoption or appropriate use;
• support for medical education planning;
• quality of cross-functional insight integration;
• retention and development of strategically important KOL relationships.

A pre-launch team should not be judged solely on how many people it has met. It should be judged on whether it has improved the organisation’s understanding of the questions clinicians will ask when the evidence meets practice.

Launch and post-launch

At launch, the pressure to count everything usually intensifies. More meetings, more requests, more internal attention, more opportunities for the organisation to mistake velocity for strategy.

The field team’s role may now include:

• maintaining scientifically credible relationships with priority KOLs;
• identifying emerging clinical questions;
• supporting appropriate interpretation of new evidence;
• detecting changes in treatment patterns or patient-management challenges;
• contributing to evidence-generation priorities;
• communicating relevant insights back into medical planning;
• sustaining engagement beyond the initial launch cycle.

Face-to-face engagement and KOL retention can become useful measures in this phase, but neither should stand alone. A retained relationship that produces no meaningful exchange is not necessarily an asset. Conversely, a newer relationship with a highly relevant clinical expert may deserve more strategic attention than an established contact who appears on every historical stakeholder list.

The scorecard should evolve as the medical strategy evolves. A static metric architecture is an administrative convenience, not a sign of maturity.

Quantifying KOL engagement quality without reducing it to a popularity score

The phrase “relationship depth” sounds suspiciously like the sort of thing that appears in a consulting presentation just before the real work is outsourced to a spreadsheet. Yet the underlying concept is valid. The question is how to make it observable.

I recommend treating KOL engagement quality as a composite judgement built from several signals rather than one inflated score. Those signals can include:

• relevance of the stakeholder to the current scientific objective;
• frequency appropriate to the relationship and lifecycle phase;
• evidence of two-way scientific exchange;
• continuity between discussions;
• responsiveness to follow-up;
• willingness to discuss uncertainty or challenge assumptions;
• contribution to evidence-generation or educational objectives;
• quality of insights generated over time.

The crucial phrase is “over time”. A relationship is not deep because one meeting went well. It becomes strategically useful when the exchange develops: the MSL understands the stakeholder’s priorities, the stakeholder trusts the MSL’s scientific credibility, and both sides can address difficult questions without retreating into promotional choreography.

A practical maturity scale can help managers evaluate this without pretending to create laboratory-grade precision:

• Transactional: the interaction is primarily informational, with limited dialogue or follow-up.
• Responsive: the MSL addresses relevant questions and maintains reliable communication.
• Collaborative: the stakeholder contributes to an ongoing scientific exchange linked to a defined medical objective.
• Strategic: the relationship generates recurring, high-quality insight and supports meaningful evidence or education priorities.

These labels should guide discussion, not become a new form of mechanical scoring. If an organisation assigns a “4” to every prominent KOL because the relationship feels important, it has not solved the problem. It has simply given the old vanity metric a more sophisticated name.

Measuring scientific insight impact

Insight quality is often the missing link between field activity and medical strategy. Many organisations collect large volumes of field observations but fail to distinguish signal from repetition.

A useful insight assessment asks five questions:

1. Is it new?

Does the insight add information not already available through internal data, published literature, or previous field reports?

2. Is it specific?

Can the organisation identify the clinical context, stakeholder type, patient population, or evidence question involved?

3. Is it credible?

Does the insight reflect a reasoned scientific perspective, or is it merely an unexamined preference?

4. Is it relevant?

Does it connect to a current medical strategy, evidence gap, clinical workflow, or patient-care issue?

5. Did it lead somewhere?

Was it used to inform a decision, shape a project, refine communication, identify a research question, or alter field priorities?

Not every valuable insight will immediately trigger a visible action. Medical strategy is not a vending machine in which a field report produces a project within five business days. Some insights accumulate and become meaningful only when combined with other evidence. The framework should allow for that—but it should still record whether the insight entered a decision pathway.

One useful distinction is between reported impact and potential impact. Reported impact refers to a documented action already taken. Potential impact identifies a credible implication that requires further evaluation. Both matter, but they should not be confused. Otherwise, every interesting observation becomes a strategic breakthrough, and the echo chamber congratulates itself for having discovered clinical reality.

The value of an insight is not determined by how elegantly it is written in the CRM. It is determined by whether it improves what Medical Affairs does next.

Linking field medical work to organisational strategy

The most sophisticated MSL dashboard will fail if it sits apart from the medical plan. Metrics should reflect strategic priorities, not the other way around.

Before choosing KPIs for field medical teams, Medical Affairs leadership should be able to answer a more basic question: what does the organisation need to learn, influence, or enable during this lifecycle phase?

That may involve:

• clarifying an unmet clinical need;
• understanding variation in treatment pathways;
• identifying evidence gaps;
• supporting an investigator-initiated research strategy;
• improving scientific education;
• preparing for new data;
• strengthening patient-care implementation;
• identifying safety or tolerability questions that require further investigation.

Once the priority is clear, the MSL contribution becomes easier to define. A field team supporting an evidence-generation priority should not be measured primarily through generic engagement volume. A team focused on scientific education needs measures that address the relevance and quality of the educational gap, not simply the number of programmes supported.

This alignment also prevents a familiar corporate failure mode: each function creates its own definition of value, then discovers during the annual planning meeting that the definitions are incompatible. Commercial teams may track reach and market activity. Clinical development may focus on recruitment and study execution. Medical Affairs must preserve its independence from commercial sales while still demonstrating how scientific work supports better decisions and better care.

That means resisting the temptation to use sales volume or prescription revenue as direct MSL KPIs. Those measures may be important to the wider business, but they do not establish whether an MSL delivered credible, non-promotional scientific engagement. Conflating the two damages both the measurement system and the function’s compliance posture.

Building a practical scorecard

A workable scorecard does not need dozens of indicators. It needs a small number of measures connected to defined decisions.

A balanced structure might look like this:

This is deliberately less glamorous than a dashboard filled with composite indices. That is a feature. A metric should make a decision easier, not merely make a presentation look more rigorous.

Governance, calibration, and the problem of bad incentives

Measurement systems do not remain neutral for long. People adapt to what the organisation rewards. If leadership rewards the number of documented interactions, teams will optimise documentation and interaction volume. If leadership rewards insight quality, teams will need the time, training, and managerial support to produce it.

Three controls are particularly important.

Define the unit of value

A meeting is not an insight. An insight is not an action. An action is not necessarily an outcome. These categories should remain separate in the data model and in performance discussions.

When organisations collapse them into one chain, they often overclaim impact. A meeting generated an insight; the insight was submitted; therefore, the meeting influenced strategy. That conclusion may be true, but it requires evidence. The framework should show the intermediate steps rather than quietly skipping them.

Review quality consistently

Managers need calibration sessions in which they review anonymised examples of engagement records and insight reports. The purpose is not to enforce identical writing styles. It is to establish a common view of what constitutes relevance, novelty, credibility, and actionability.

Without calibration, quality scores become a reflection of manager preference. One territory receives high marks for detailed narrative; another receives high marks for brevity. Neither approach says much about medical impact.

Measure the system’s response

Medical Affairs leaders should track what happens after insights are submitted. Are they reviewed? Categorised? Routed to the right team? Discussed in governance forums? Connected to evidence-generation planning? Closed with the MSL?

If field teams repeatedly report that insights disappear into an organisational void, the answer is not another training module on insight quality. The organisation needs a functioning insight-to-action process.

This is a point many companies prefer to avoid because it shifts the scrutiny upward. It is easier to tell MSLs to improve their reports than to admit that senior teams have no reliable mechanism for using them.

The operating rhythm matters more than the annual framework

Even a well-designed metric framework can become irrelevant if leadership reviews it only during the annual planning cycle. Medical science liaison performance metrics should live in the rhythm of Medical Affairs management.

A sensible operating cadence might include:

• monthly review of coverage, workload, and urgent gaps;
• quarterly review of insight themes and strategic relevance;
• periodic assessment of KOL relationship quality;
• project-level review of field medical contributions;
• lifecycle-based revision of targets and definitions;
• annual evaluation of whether the metrics still reflect the medical strategy.

The point is not to create more meetings. Medical Affairs already has enough meetings to populate a small city. The point is to use existing governance moments more intelligently.

For example, a quarterly review should not ask only how many interactions occurred. It should examine which scientific themes are recurring, which stakeholder perspectives challenge internal assumptions, where evidence gaps remain unresolved, and which insights have moved into action. That conversation has strategic value. A slide showing that engagement volume increased by 8% does not, by itself, have any.

The same applies to field medical excellence programmes. Training should cover not only scientific communication and compliance but also stakeholder segmentation, insight elicitation, documentation quality, and strategic interpretation. An MSL cannot generate meaningful field intelligence if the organisation has not defined what it wants to learn.

What leaders should change first

The transition away from activity counting does not require a grand transformation programme with a branding exercise and a steering committee named “Project North Star”. It requires a few practical changes applied consistently.

1. Keep activity metrics, but demote them.

Use interaction counts and relationship coverage to understand capacity and reach—not as proof of impact.

2. Define quality in operational language.

Explain what makes an interaction or insight relevant, credible, specific, and actionable. Avoid vague expectations about strategic value.

3. Align KPIs with lifecycle and medical priorities.

Early development, pre-launch, and post-launch field work produce different forms of value. The scorecard should acknowledge that reality.

4. Create an insight taxonomy that people can use.

If categories are too elaborate, MSLs will select the nearest available option and move on. If they are too broad, leadership will receive a warehouse of undifferentiated observations.

5. Add external and internal feedback.

KOL engagement quality cannot be assessed entirely from inside the company, and field medical usefulness cannot be understood solely through CRM data.

6. Track what the organisation does with insights.

A report that disappears into a repository has not yet demonstrated strategic impact. Build visible pathways from insight to review, decision, or further investigation.

7. Separate evaluation from theatre.

Do not introduce a score because it looks sophisticated. Every metric should answer a real management question.

The pragmatic conclusion

Medical Affairs leaders do not need to prove that MSLs are busy. The calendar already does that. They need to demonstrate that field medical work improves scientific understanding and strengthens decisions across the product lifecycle.

The shift from volume-based KPIs to hybrid evaluation frameworks is therefore not a matter of finding a more elegant dashboard. It is a change in what the organisation considers evidence of value. Interaction quality, project-based scientific outputs, KOL satisfaction, internal stakeholder usefulness, and insight-to-action pathways provide a more credible picture than activity counts alone.

The 40% impact-measurement figure should not be treated as a minor reporting gap. It signals that much of the industry still measures the visible surface of Medical Affairs while leaving the consequential work largely unexamined.

I would start with one deliberately uncomfortable question: if we removed every interaction count from the quarterly review, what evidence would remain that the field medical team changed a scientific decision, improved an evidence plan, or clarified a problem in clinical practice?

If the answer is very little, the issue is not that MSL impact is impossible to measure. The issue is that the organisation has chosen metrics that protect its optics from scrutiny.

That is alignment, of a sort. Just not the useful kind.