Measure What Matters: How OKRs and KPIs Fit Together at Every Stage Gate

MS1 is where the misalignment usually starts. The framework that fixes it works at every gate after that, too.

Stage gates are the points where Product Managers (PMs) and the cross-functional team commit to what success looks like. MS1 is the first one with real teeth, because the business case written at MS1 sets the direction for everything that follows: the development plan, the regulatory pathway, the commercial assumptions, the launch criteria. Some development budget is already in motion at MS1 because of concept feasibility work, and the volume of spend grows fast from there.

This is also the gate where many life sciences teams set themselves up for a tough launch review. Not because the team is wrong about what to build, but because the team has not yet aligned on how to tell whether the build worked. The business case ends up with key performance indicators (KPIs) carrying the weight of objectives, with no shared definition of what "won" actually looks like across R&D, Commercial, Regulatory, and Operations. The launch review at MS5 is the first time everyone realizes they were measuring different things, and the conversation becomes a negotiation rather than a verdict.

The good news is the fix is structural, not personal. Objectives and key results (OKRs) and KPIs are not in conflict. They sit at different altitudes of the same measurement system, and once a team aligns on which is which, the whole stage gate process gets easier.

The Romans had a deity for the discipline this requires.

Mens: The Goddess of Sound Judgment

Mens was the Roman personification of the rational mind, the deity of clear thinking and right judgment. Romans dedicated her temple on the Capitoline Hill during a period when the state needed to make a series of consequential decisions and wanted to mark the discipline of thinking clearly as something worth honoring publicly. Mens was not invoked for inspiration or for victory. She was invoked for the harder work of telling categories apart: which decisions need deep reflection, which need quick action, and which need shared agreement before anyone moves.

That is the cross-functional task at every stage gate. The team is making decisions about a product that does not yet exist, with stakeholders who hold different definitions of success. R&D is thinking about feasibility. Commercial is thinking about segment positioning. Regulatory is thinking about claims and clearance. Operations is thinking about scalability. All four are right. None of them, on their own, is sufficient. Mens is the discipline of building one shared measurement frame across all four perspectives, instead of letting the loudest function decide for everyone.

How OKRs and KPIs Actually Fit Together

There are two schools of thought worth knowing about, because the team will encounter both.

The orthodox view, traceable to Andy Grove at Intel and codified by John Doerr in Measure What Matters, treats OKRs and KPIs as different categories. Objectives are aspirational and time-bound. Key results are the measurable success criteria of the objective. KPIs are separate operational metrics that monitor product or business health on an ongoing basis. In this view, OKRs and KPIs run in parallel.

The integrated view, common in mature product organizations, nests them. The objective sits at the top: a clearly defined, time-bound bet on a market position. The key results define what "won" looks like and stake falsifiable evidence. KPIs sit underneath as the operational signals that tell the team whether they are on track to hit the key results. In this view, KPIs are the leading indicators of OKR progress.

For MS1 in life sciences, the integrated view is the one to adopt.

MS1 is where the cross-functional team needs a single shared picture of success. Splitting OKRs and KPIs into parallel tracks gives each function a place to hide: R&D watches the technical KPIs, Commercial watches the market KPIs, and the objective drifts above them all without anyone owning the integration. Nesting them forces the team to agree on the bet first, then derive the operational signals each function will watch from that bet. Everyone is reading the same story at different altitudes.

In RUO life sciences specifically, this matters because the buyer is technical and the sales cycle can be long. A reorder rate is a useful KPI. It tells the team that the product is performing in accounts that already bought. It is not the objective. The objective is a market position the team is staking, and the reorder rate is one of several signals that tell the team whether the position is being taken. Treating the reorder rate as the objective collapses the altitude difference and leaves the team without a vision for the team to rally around.

The MS1 Alignment Conversation

The most useful thing a PM can do at MS1 is convene a single working session where R&D, Commercial, Regulatory, and Operations build the OKR together. Not approve a draft, go ahead and build it. The conversation usually surfaces three things in the first hour:

• The functions are using the same words to mean different things. "Adoption" to Commercial means logo count. "Adoption" to R&D means active monthly users. "Adoption" to Operations means consumables velocity. The session is the first place these get reconciled.
• Last year's launch metrics are being copied forward. The KPIs from the previous product line have a way of becoming the default for the new one. Without a deliberate reset, the team builds a measurement frame for a product that is not the one they are launching.
• One function is carrying a measurement instinct the others do not share. Scientists who have moved into product management often arrive with a fully-formed KPI vocabulary from the bench: experiment completion rate, protocol validation timeline, lot release pass rate. These are excellent operational signals. They are not, on their own, the objective. Naming this in the room makes it easier for everyone to contribute their half of the picture without anyone feeling sidelined.

The output of the session is a single objective with three to five key results, written in language that every function can defend in their own department review. The KPIs each function will track sit underneath, mapped to the key results they support. Everyone leaves with the same picture.

Two Worked Examples: OKRs and Their Underlying KPIs

The clearest way to internalize the integrated model is to see it applied to two launch types most life sciences PMs recognize. The objective and key results sit at the top. The KPIs are the operational signals that sit underneath, telling the team whether they are tracking toward the key results.

Read across each row. The OKR names a market position the team is collectively trying to take and stakes specific, falsifiable evidence that the position has been taken. The KPIs are the operational signals each function will watch every month, knowing that drift in those signals is an early warning that the OKR is at risk. The team has one shared picture; each function has its own clear contribution.

Regulatory Milestones Are Not Objectives

In IVD development, this distinction is especially worth getting right at MS1. The 510(k) clearance date is a project milestone, not an objective. The objective is the market position the team is taking after clearance, for example achieve 8% share of mid-volume hospital labs in the cardiac biomarker segment within 24 months of clearance. Holding the clearance date as a milestone (alongside design verification, validation lots, and clinical study completion) and the market position as the objective gives the regulatory function a clear contribution to the OKR without making the regulatory pathway the entire definition of success.

The Same Framework, Different Content at Each Gate

This integrated model applies at every stage gate, with the content of the OKRs evolving as the product matures. At MS1 the OKR is about market position and concept-stage commercial bets. At MS3 the OKR is about design verification and beta program learning. At MS4 the OKR is about launch readiness across functions. At MS5 the team measures the post-launch OKR against the key results set at MS1, which is why getting MS1 right is so disproportionately valuable. The KPIs underneath each OKR also evolve, but the structure stays the same: one shared bet at the top, operational signals for each function underneath.

Mens at the Stage Gate

The Romans honored Mens because they understood that in any consequential decision, the discipline of thinking clearly is itself worth a temple. They did not invoke her for inspiration. They invoked her for alignment, for the patience to sort categories before acting on them.

That is the gift of a well-built MS1 OKR. The team agrees on the bet before the development clock starts. Each function knows its contribution and the operational signals it owns. The launch review at MS5 becomes a comparison against a shared definition, not a renegotiation of what success was supposed to mean. Build the bet together. Let the KPIs sit underneath it, owned by the function closest to each one. Refuse the rinse-and-repeat of last year's launch metrics. Mens is not glamorous, but at every stage gate she is the deity who keeps the team aligned. Romans honored Mens not because she gave them answers, but because she gave them the patience to build agreement