Your PM Nailed the Beta. Your PM Had No Answer on Positioning.

How RUO Life Science PM Directors Build Commercial Range That Survives Every Milestone

This is Part 2 of a two-part series. Part 1, You Are Not One Thing, covers the five modes framework for individual RUO life science PMs.

Ops and the Work Before the Work

Roman farmers called on Ops not at the moment of harvest, but months before it. Her festivals fell in December and August: the times of preparation and storage, not yield. The harvest itself was already decided by then. The soil had been turned or it hadn't. The seed had been stored correctly or it hadn't.

Ops was the deity of the conditions that precede abundance. The yield collected in October was decided by the work done in February.

RUO life science PM directors face the same arithmetic. The commercial range your team demonstrates at MS4 is not a function of what you coach in the launch readiness review. It is a function of what you built into your team's working conditions at MS2. A PM who arrives at the MS3 milestone review unable to hold a Strategist conversation did not develop that gap at MS3. You set the conditions for it months earlier, one way or the other.

A brief orientation if you are coming to this post without Part 1. The five modes are the leadership postures RUO life science PMs draw on across the commercialization process: Strategist (shaping commercial direction), Operator (driving execution and making outcomes visible), Activator (unblocking cross-functional teams, for example when a FAS team stalls on beta recruitment because success criteria were never made explicit), Connector (building relationships that survive milestone transitions), and Architect (designing how the team makes decisions). Operator is the mode most organizations reward by default, which makes it the mode most PMs develop first. As AI tools absorb more execution and reporting tasks, Strategist becomes the mode that cannot be automated. Building it now, deliberately, is not optional. The director's challenge is not spotting the default. It is building the conditions that expand it before the commercial stakes make it visible.

The Yield You Didn't Plan For

You have been in this room.

One of your PMs just closed beta recruitment two weeks early. Every site onboarded, success criteria documented, feedback loop established. You brought them into the MS3 milestone review feeling good about the portfolio.

Then the commercial team asked the positioning question. Who is this product for, specifically, and why does that segment buy from you instead of the incumbent?

They had no answer. Not a weak answer. No answer.

You left that review knowing something structural had gone wrong. Not with them. With the conditions you had built around them. They had learned exactly what got rewarded. Operator execution was what got rewarded.

The instinct after that review is to question whether they have the commercial range for this role. That instinct is the myth.

Myth: Mode-range is a talent problem. Some PMs have commercial range and some don't.

Reality: Mode-range is a conditions problem. It develops where it is required, resourced, and rewarded. That is the director's lever.

Coaching by Phase: MS2, MS3, MS4

The five modes function differently depending on where you sit in the phase gate process. Your coaching interventions need to match the phase you are in. Each phase has a distinct job.

MS2: Build the conditions

MS2 is where mode-range gets built, or doesn't. The commercial stakes are low enough for development work to be generative rather than corrective. Three interventions are worth making here.

A one-on-one mode audit. Sit with each PM and map which modes they occupy with confidence and which they avoid. Frame it as a development conversation: which situations feel natural, which feel exposed? A PM who avoids Strategist mode is not a weak strategist. They are a strategist who has not yet been given conditions to practice it safely.

Exposure assignments, not stretch goals. A stretch goal asks a PM to perform outside their mode range at the moment of highest commercial stakes. An exposure assignment creates a low-stakes context for mode practice before those stakes arrive. Assign your Operator-dominant PM to lead the competitive positioning brief at MS2. For kit and reagent programs, internal MS2 documents carry limited downstream consequence and an imperfect draft costs little. For instrument programs, check the scope of the assignment first: the goal is low-stakes practice, not low-stakes documents. That’s how Strategist range gets built. Not in the MS4 launch review with the room watching.

Explicit permission structures. If your organization rewards Operator outputs in every milestone review, your PMs have received a clear signal about which mode matters. Counter that signal where you have direct control: in your one-on-ones and team reviews. Use your MS2 milestone prep conversations as the moment to develop Strategist and Connector outputs, not just evaluate Operator ones. If your PM arrives at MS2 prep with no commercial framing drafted, that absence is the data.

MS3: Diagnose and protect

By MS3, the time for conditions work has passed. You are diagnosing gaps and protecting the commercial outcome with the team you have.

Four signals of mode-lock at MS3. Operator lock: outcomes described in process terms ('We completed FAS training' instead of 'We cut time-to-first-result from 14 days to 6'). Boundary avoidance: no pushback on R&D scope creep, no negotiated beta success criteria, no expectation-setting with commercial before go-live. Connector gap: key relationships stay transactional, limited to beta administration (whether those relationships are academic KOLs, OEM procurement managers, or diagnostic lab directors depends on your market, but the signal is the same). Activator gap: the PM knows what they need from cross-functional partners but cannot generate momentum in those relationships. For Activator gaps, the intervention is structural: clarify what each stakeholder needs to move, and the team will follow.

When you identify a mode gap at MS3, the intervention is direct and task-specific. Ask what this launch requires from the mode they are under-using and what structure they need from you to produce it. Schedule the development conversation for after go-live.

MS4: Scaffold, don't step in

At MS4, the director's job is to protect the commercial outcome without taking over the execution. Those are different things, and the distinction matters to your team.

If a PM in Operator mode is running a commercial partnership conversation, equip them before they walk in: clear talking points, a defined success outcome, a debrief structure for afterward. The PM still runs the conversation. You have prepared them to succeed in a mode that doesn't come naturally yet. The same principle applies across every MS4 commercial conversation, whether that is a KOL publication discussion, a distribution agreement, or a FAS readiness review. Stepping in and running the conversation yourself signals you don't trust the execution. Scaffolding signals you do.

Ops Was Right About February

The PM director who builds mode-range at MS2 does not notice it at MS4. The launch just works better. The commercial conversations hold. The positioning questions get answered. The KOL relationships convert into publication commitments.

The director who didn't build those conditions notices in the MS3 review, watching their best PM go quiet when the commercial team asked the one question that mattered.

This quarter, run one mode audit with one PM. Name the mode that is most load-bearing for their current phase. Ask whether the conditions around them are building that mode or defaulting to Operator. That is the February work. The October yield follows from it.

If you are an individual PM without direct reports, this framework runs in both directions. The mode audit your director should be running with you is a conversation you can initiate yourself.

Part 1 of this series, You Are Not One Thing, covers the five modes framework for individual PMs navigating their own mode-range. Read it at strivenn.com/thinking/you-are-not-one-thing.