Planning Optimization

Planning in the Blue Ocean: Why Nobody Has Solved MSL Territory Planning

By MSL Blueprint · 10 min read · May 2026

Somewhere in a biopharma medical affairs office right now, a field medical director is staring at a spreadsheet. It has 47 tabs. The first tab maps KOLs to geographies. The second tab estimates travel time between academic medical centers. Tab 12 is a force-sizing model that someone built three years ago and nobody fully understands anymore. Tab 23 is the congress capacity calculator — how many MSLs can you send to ASCO given budget, booth meetings, satellite symposium support, and the fact that two of your people have a scheduling conflict with the regional investigators meeting?

This spreadsheet is the planning infrastructure for a team of 30 MSLs covering a $3 billion therapeutic area.

And it's the best system available. Because nobody has built anything better.

That's not hyperbole. It's a measurable gap in the industry's knowledge base — one that becomes obvious the moment you look for published methodology.

The Blue Ocean

We cataloged 191 published sources across the MSL profession's primary knowledge base — the MSL Journal, the MSL Institute, DIA's Medical Affairs and Scientific Communications Forum, relevant PubMed literature, and guidance from professional societies. We mapped every source to topic categories: competency development, KOL engagement, metrics, technology adoption, regulatory compliance, organizational design, planning.

Planning — territory design, capacity modeling, headcount justification, POA development — accounts for a handful of articles. Across the entire literature base.

Set that against what the rest of the field covers. Competency development: dozens of articles on skills, training, role definition, and professional development pathways. KOL engagement: heavily covered across best practices, relationship building, engagement strategy, and digital evolution. Metrics: growing coverage as the industry wrestles with measurement limitations. Technology: increasing coverage as CRM utilization, digital engagement, and AI applications mature.

Every MSL leader plans. Almost nobody has published how. Most inherited the spreadsheet or PowerPoint from their predecessor — or borrowed one from another therapeutic area lead — and iterated from there.

This isn't a niche topic that academics haven't gotten to yet. Territory design, capacity modeling, and objective-setting are the operational backbone of every field medical function in the industry. The literature has almost nothing to say about any of it. It's not underserved. It's unserved.

Why the Gap Exists

How is this possible? Four structural forces explain it.

Planning Is Local, Not Universal

Every company's planning context is different — therapeutic areas, team sizes, geographic coverage, product lifecycle stages, organizational structure. A new 10-person oncology team at a launch-stage biotech plans differently than a 100-person multi-TA function at a top-10 pharma. The industry has assumed that planning is too context-dependent to generalize.

Planning Knowledge Doesn't Transfer

When a field medical director leaves a company, their planning methodology leaves with them. The spreadsheets and powerpoints stay behind, but the logic, assumptions, and institutional knowledge that make them work don't. The next leader starts over — building their own spreadsheet, their own territory model, their own capacity assumptions. New team? Grab the templates from another TA or start from scratch based on how many FTEs got approved and whatever commercial leadership will support. This happens at every transition, at every company, across the entire industry.

The cost is invisible because it's embedded in every new leader's first six months on the job. The industry has been paying the price of reinventing planning infrastructure at every leadership change for decades.

The Industry Focused on Execution, Not Planning

The professional societies — the MSL Society, MAPS, the MSL Institute, DIA's Medical Affairs and Scientific Communications Forum — focus on what happens after the plan is made. How to execute KOL engagement. How to train MSLs. How to run a congress. How to measure interactions. Planning is treated as the prerequisite that everybody figures out on their own, rather than a discipline worth formalizing. That prioritization makes sense for practitioner-facing organizations. But it leaves the leadership-facing work undone — and the downstream effect is predictable. Without planning frameworks to anchor strategy, team leads default to what they can control: execution. More programs, more activities, more deliverables. Not because they lack leadership ability, but because nobody gave them the infrastructure to connect their team's work to a strategic value proposition. Every MSL has worked with — or been — a leader stuck in that mode. The path forward isn't to criticize the operational instinct. It's to give leaders the planning architecture that channels it toward impact.

No Natural Category Owner

Who would build field medical planning tools? CRM vendors optimize for interaction logging, not territory design. Consulting firms do custom planning engagements but don't publish shared frameworks. The professional societies focus on practitioner standards. Nobody's business model was "build planning infrastructure for field medical leadership."

What Planning Actually Looks Like Today

Stand behind a field medical leader's shoulder during planning season and the same patterns emerge regardless of company, therapeutic area, or team size. The problems are universal even if the contexts differ.

Territory Design

In most organizations, MSL territory design starts with a question: how many MSLs did we get from the budget ask? That's the first input — not strategic need, not KOL landscape analysis, not institutional opportunity mapping. Headcount allocation comes from finance, and then someone opens a map, draws boundaries, and assigns MSLs based on geography and existing relationships. The secondary inputs are straightforward: Where do our KOLs practice? Where do our MSLs live? How far is the drive?

What's missing: KOL density weighting, institutional complexity scoring (AMCs versus community practices), clinical trial support and clinical site geography, product lifecycle stage adjustments, competitive landscape considerations — any input that goes beyond geography and convenience.

The result is that some MSLs have 10 Tier 1 KOLs and others have 50 — not because of a strategic allocation model, but because of how the lines were drawn.

Capacity Modeling

How many MSLs do you need? Ask five field medical directors and you'll get five different methods. Some benchmark against peers — "Pfizer has 30 for this TA, so we need 25." Some use KOL-to-MSL ratios. Some build bottom-up models from interaction targets. Almost nobody can defend their headcount to a CFO with a methodology that would be recognized as rigorous. So instead the CFO and medical leadership just look to the commercial GM for the nod of support and move on.

What's missing: a capacity framework that integrates KOL universe size, interaction depth targets (not just counts), congress and advisory board load, evidence generation commitments, speaker program and sales support obligations, administrative burden, and product lifecycle phase. All of these are real demands on MSL capacity. None of them appear in most headcount justifications.

POA Development

The MSL Plan of Action in most organizations is a PowerPoint deck presented at the beginning of the year. It lists activity targets, KOL engagement priorities, congress attendance plans, and training objectives. It gets dusted off and updated somewhat at midyear. Then it again sits in a shared drive folder that nobody opens between planning cycles.

What's missing: objective cascades that connect scientific platform strategy to medical affairs objectives to field medical team objectives and key results to individual MSL plans. Quarterly reviews with measurable milestones. Feedback loops from field insights back to strategy. Monthly reports that demonstrate outcomes vs just activities. The connecting tissue between what the company says it's trying to accomplish scientifically and what an individual MSL is doing on a Tuesday afternoon.

The Scientific Platform Cascade

This disconnect — between strategy and daily field execution — points to the planning concept that deserves the most attention.

Most organizations have fragments of a planning cascade. They may have a scientific platform. They definitely have MSL activity targets. What they rarely have is the connecting tissue between them — the explicit set of links that translates what the company's scientific strategy says into what activities MSLs are allowed to do, what they should prioritize, and how individual territory plans serve the overall scientific mission.

The cascade, fully articulated, looks like this: Scientific Platform Strategy flows into Medical Affairs Objectives, which translate into field medical team objectives and key results, which shape territory plans, which drive individual activity priorities, which generate field insights — and those insights feed back into the scientific platform.

When the cascade is broken — and at most companies, it's broken at one or more joints — planning becomes disconnected from strategy. Activity targets exist in a vacuum. MSLs execute without understanding how their work connects to the scientific platform. And leadership can't explain to the C-suite what the field medical investment is producing, because the link from activity to strategic outcome was never explicitly built. Without that strategic alignment at the executive level, field medical teams end up negotiating individual slide decks and tactical resources through legal, regulatory, and compliance reviews — resource by resource, one review at a time. The conversations happen at the wrong altitude. Instead of aligning company-wide on the field medical function's strategic remit and building review guardrails from that, every deliverable becomes a standalone risk discussion. The result: a junior reviewer can raise a concern that reshapes an MSL resource critical to the team's core objectives, because there's no broader strategic framework that sets the boundaries for those field medical specific reviews upfront.

This cascade framework gets its own dedicated piece. For now, the point is this: the planning gap isn't just about better spreadsheets. It's about building the architecture that connects corporate scientific strategy to what happens in the field.

What Formalization Would Look Like

Imagine a field medical leader who can model headcount needs with inputs executive leadership, including the CFO, recognize as rigorous. Who designs territories based on weighted KOL density, institutional complexity, and strategic priority — not just geography. Who builds plans that cascade from the MSL value proposition and scientific platform strategy through measurable objectives to individual MSL priorities. Who can redraw territories when the team grows or contracts without treating it as a clean-sheet exercise — because the model accounts for relationship continuity, not just geography.

KOL relationships are the primary asset field medical teams build. They take years to develop and moments to damage. Any planning methodology that doesn't account for relationship continuity isn't planning for the real world. The best field medical leaders already know this intuitively. They just don't have a framework that operationalizes the intuition.

This isn't aspirational. It's operational. It's what planning looks like when it has methodology, not just effort.

We're building the frameworks and tools to make this real. Start with the assessment to find where your planning maturity stands.

[Take the Assessment →](/assess)

[Explore the Framework →](/framework)

The author is the founder of MSL Blueprint and has spent the last 20 years building, leading, and scaling field medical teams at several biopharmaceutical companies — from team design and territory optimization through scientific platform strategy, KOL engagement frameworks, and qualitative outcome measurement. MSL Blueprint is building the strategic planning and measurement layer that the field medical function has been missing since 1967.