The most consequential decision RDI ever made about its operating structure was who would run the trials. The conventional CRO answer is to hire a senior clinical operations leader — someone whose career has been spent running studies, who knows the project management discipline cold, who can be trusted to manage milestones and deliverables and sponsor relationships at scale. We made a different choice. The person who runs operations at RDI is an assay validation scientist by background, not a project manager who learned to be operational. Her name is Lara Flores. She is our COO. The choice has shaped everything about how the company operates, and it is the single most underused structural advantage I see when I look at how other IVD CROs are organized.
This framework describes what changes when the person running the trials thinks like an assay validation scientist. The change is not subtle. It shows up in the questions she asks at protocol review. It shows up in how monitoring deviations get triaged. It shows up in the structure of every workflow she touches. And — most importantly — it shows up in the people who work for her, who learn to ask validation-scientist questions because they spend their days alongside someone who asks them as a default.
I am writing this as CEO, but the framework is about Lara and the operating posture she embodies. The structural decision was that the person closest to the daily execution of every IVD study should be someone whose career has been about making assays work — not someone whose career has been about running projects. The framework below is what that decision actually means.
The scientific worldview asks different questions.
A project manager asks whether the milestone slipped. An assay validation scientist asks whether the data will hold up at submission. Both questions matter; only the second produces a clearable assay.
The first principle. A project manager and an assay validation scientist looking at the same study see different things. The PM sees a Gantt chart, a budget burn, a milestone calendar, a list of action items from the last sponsor call. The validation scientist sees those things too, but underneath them she sees the assay's eventual submission package and asks whether what is happening today produces evidence that will survive FDA review. The two views are complementary; they are not interchangeable. A study run only against the PM view hits its milestones and produces a submission that gets pushed back on. A study run only against the validation view produces clean data and slips its timeline.
What changes when the validation scientist is the one running operations is that the validation questions get asked at the moments when the answers can still influence the work. At protocol review: does the sample handling spec match the IFU's eventual intended-use claim? At kit design: do the QC records produce the audit trail a regulator will look for? At monitoring: do the protocol deviations being recorded reflect the categories the eventual statistical analysis plan will need to defend? None of these are PM questions. All of them are decisions made on every IVD study, and the studies whose decisions are made by someone who knows what the FDA reviewer will eventually ask are the studies that hold up at submission.
This is not a critique of project managers. The PM discipline is real, and PMs do work that validation scientists are not trained to do. What the framework is saying is that the operations leader — the person to whom every PM reports — should hold the validation worldview, so that the PM discipline is supervised by someone who knows what the work is for.
The principle is observable across our protocol reviews, where the questions Lara asks are systematically different from the questions a clinical-operations leader would ask. On a recent multi-cohort rescue, her review of the inherited protocol surfaced sample-handling specifications that were defensible under the prior CRO's monitoring plan but would have failed FDA scrutiny on stability documentation. The corrections were made before the study restarted, and the database lock came in clean as a result. A non-validation operations leader would not have asked the question that surfaced the problem.
For an IVD CRO, the operations leader's background should match the work the operations are for. If the work is making assays survive FDA review, the leader should be someone whose career has been about making assays survive FDA review. The discipline is teachable to PMs working under that leader; the leader's own discipline has to be the right one to start.
The worldview is viral. It spreads through the team.
The PMs and operators working under an assay validation scientist learn to ask validation-scientist questions. The whole team levels up because of who they work for.
The second principle is what makes the structural choice compound over time. People learn from the people they work for, and the way they learn most reliably is by absorbing the questions those leaders ask in real time. A PM working under a project-management leader learns project management. A PM working under an assay validation scientist learns project management plus the validation worldview that makes their project management actually serve the work the study is for.
The result is a team that asks better questions than the team's roster suggests it should. Junior PMs at RDI ask questions about sample stability documentation that would not occur to PMs at the same level elsewhere, because they have been in the room when Lara asked the same question on the prior study. They ask about CRF design at the question level, because they have heard her audit a CRF that way. They ask about the IFU's intended-use language at protocol review, because they know that is the question the operations leader is going to surface and they want to surface it themselves first.
This compounds. A PM who has spent two years working under a validation scientist is, functionally, a hybrid PM-validation operator — someone who can run the project management discipline and ask the validation questions in the same breath. That hybrid is rare in the industry, expensive to hire externally, and almost impossible to train without exposure to a validation-scientist leader. RDI grows them as a side effect of how the company is organized. The talent advantage is durable because it is structural, not because we are paying above market for already-trained people.
The viral effect requires the validation scientist to be operationally close to the team — in the room at protocol reviews, on the call when monitoring questions get triaged, present at the post-mortems. A validation-scientist COO who is too far from the work does not produce the spread. The spread is the thing the org chart is engineering.
It shows up in the systems, not just the decisions.
When an assay validation scientist takes a workflow apart and rebuilds it, the rebuilt workflow carries the validation worldview forward — long after she has moved to the next problem.
The third principle is the most durable. The validation worldview does not just show up in the decisions Lara makes day to day. It shows up in the systems she builds and the workflows she rebuilds when she finds them wanting. The kit QC checklist that names lot, expiry, label format, and second-checker signature; the sample spec sheet that captures every detail upfront and auto-builds the SOW; the kickoff document structure that names every team member by name and structures the work in weekly batches; the enrollment forecast at daily resolution per site per cohort with milestones threaded into the calendar — every one of these is a system she has built, and every one of them carries the validation worldview into the future as a default behavior the team operates from.
This is what distinguishes a leader who is a teacher from a leader who is just a decision-maker. A decision-maker leader produces good decisions while they are present and worse decisions while they are away. A teacher-leader produces systems and workflows that produce good decisions even in their absence, because the systems carry the worldview the leader brought to bear when they were built. The systems she has built at RDI are the cumulative product of fifteen years of validation-scientist scrutiny applied to the operational layer of a CRO. Other CROs can hire away individual operators; they cannot hire away the systems, because the systems are the artifact of having had a validation scientist running the operation for fifteen years.
The deeper move this enables is durability. RDI's operating advantage is not just that we have Lara today. It is that the systems she has built will keep producing the right decisions even on studies she never personally touches, because every workflow she has ever rebuilt carries her worldview forward as the default. New PMs joining the team inherit the systems and learn the worldview by operating within them. The structural choice keeps paying out long after the original decision was made.
The artifacts in the operations layer at RDI — the QC checklists, the spec sheets, the forecast templates, the kickoff document conventions — are not generic CRO templates. They are systems Lara took apart and rebuilt, sometimes more than once, and each rebuild incorporated something that the prior version had missed. The fifteen-year continuity of the company since 2011 is what allowed the rebuilds to compound rather than reset every time a new operations lead came in. The systems are the receipts of the structural choice.
The validation worldview produces systems, not just decisions. A CRO that wants to operate this way has to give the validation-scientist operations leader the time and authority to take workflows apart and rebuild them — not just to weigh in on individual study decisions. The rebuilds are where the durable advantage compounds.
What this framework rules out.
The three principles describe what changes when an assay validation scientist runs the trials. They also rule out a few conventions worth naming.
They rule out operations leadership as a generic discipline in IVD CRO work. The discipline of running studies is real; it is also not sufficient. The leader's worldview shapes the questions the team asks, and the questions the team asks shape the studies that result. The right worldview for IVD is the validation-scientist worldview.
They rule out hiring around the leader as a substitute. CROs sometimes try to compensate for a non-validation operations leader by hiring senior validation talent into individual roles. The compensation does not work, because the worldview spreads from the leader downward, not from individual hires upward. The leader is the one who sets what gets asked.
They rule out the systems as portable. Templates can be copied; the worldview that produced them cannot be. CROs that copy the artifacts without copying the structural choice produce empty templates that decay quickly without the validation discipline maintaining them.
The framework is not closed. When the study outcome matters, you call RDI. The structural choice that an assay validation scientist runs the trials is the most underused advantage in IVD operations. We made it in 2011 and have lived inside the consequences for fifteen years. They have been good consequences, and they continue to compound.