Prior Knowledge Only Helps If You Can Actually Use It

FDA just issued draft guidance on using prior knowledge in gene therapy development.

That sounds technical.

It is.

But it also points to something very practical:

Speed does not come from skipping work.

Speed comes from knowing which work is actually necessary.

That is a different problem.

And it is one a lot of pharma teams underestimate.

Prior Knowledge Is Not a Free Pass

The idea is straightforward enough.

If a sponsor has access to relevant public knowledge, platform knowledge, CMC data, nonclinical information, or clinical experience, FDA may allow that knowledge to support development and reduce unnecessary duplication.

That is useful.

Especially in cell and gene therapy, where timelines are tight, patient need is real, and every redundant study or repeated technical exercise can slow the path forward.

But let's be clear:

Prior knowledge is not magic.

It does not replace product understanding.

It does not fix weak documentation.

It does not turn a messy CMC package into a coherent one.

And it definitely does not help if your team cannot explain why the prior knowledge applies to this product, this process, this patient population, and this risk profile.

The Real Work Is the Connection

Most teams do not struggle because they have no information.

They struggle because the information is scattered.

CMC has one version of the story.

Regulatory has another.

Clinical has a timeline problem.

Quality is trying to figure out whether the process is actually controlled.

Leadership wants to know if this helps the submission move faster.

And somewhere in the middle, someone is building a tracker that gets updated every Friday and trusted by no one.

Sound familiar?

The hard part is not saying, "We have prior knowledge."

The hard part is showing:

- What knowledge you are relying on

- Where it came from

- Why it is relevant

- What assumptions are being made

- What gaps still exist

- What risks still need direct evidence

- Who owns the story

That last one matters.

Because if nobody owns the story, the story usually falls apart.

Platform Knowledge Still Needs Product Discipline

Platform knowledge can be powerful.

If you have repeated experience with a vector, process, analytical method, manufacturing platform, delivery approach, or control strategy, that knowledge should not sit in a drawer while every new program starts from zero.

That is waste.

But there is a difference between leveraging a platform and hiding behind one.

FDA is not asking sponsors to wave at a platform and hope everyone feels good about it.

The question is whether the platform knowledge is scientifically appropriate to use.

That means teams need discipline.

They need to understand what is truly shared across programs and what is product-specific.

They need to know where comparability is strong and where it is thin.

They need to separate experience from assumption.

They need to avoid the very human temptation to call something "platform knowledge" because it makes the timeline look better.

That may get you through a meeting.

It will not get you through a serious review.

This Is Where Execution Shows Up

A guidance document can create opportunity.

It cannot create alignment inside your company.

That part is on you.

If your teams want to use prior knowledge well, they need a practical operating model:

- A clear inventory of relevant public, internal, and platform knowledge

- A decision framework for what can be leveraged and what cannot

- A gap assessment that is honest enough to be useful

- CMC, quality, regulatory, and clinical alignment before the submission scramble starts

- Documentation that explains the rationale in plain language

- Leadership willing to make decisions instead of letting every uncertainty become a side quest

None of that is glamorous.

Good.

Most useful work is not.

The Risk Is False Efficiency

There is a version of this where companies hear "prior knowledge" and immediately try to compress the timeline.

That is understandable.

It is also risky.

If the team uses prior knowledge to avoid redundant work, great.

If the team uses prior knowledge to avoid hard thinking, not great.

False efficiency looks like progress right up until the questions start:

Why does this data apply here?

What changed between the prior platform and this product?

What did you verify directly?

What assumptions are you carrying?

What is your control strategy?

Where is the evidence?

If those questions make the room go quiet, the problem is not the guidance.

The problem is readiness.

The Opportunity Is Real

This guidance matters because it recognizes something practical:

Not every program should have to rebuild the same evidence from scratch.

That is especially important for rare and life-threatening diseases, where patients do not have time for companies to repeat work just because the internal knowledge system is a mess.

But the opportunity only helps teams that are prepared to use it.

Prior knowledge has to be curated.

Rationale has to be written.

Gaps have to be named.

Ownership has to be clear.

The submission story has to hold together.

That is not paperwork.

That is leadership.

Start With the Story

If you are looking at this guidance and wondering what to do next, do not start by asking how much work you can remove.

Start by asking whether your team can tell the story.

What do we already know?

What can we defend?

What is truly applicable?

What still needs product-specific evidence?

Where are we guessing?

Who owns the decision?

If those answers are clear, prior knowledge can help you move faster.

If those answers are fuzzy, prior knowledge becomes another thing people cite in meetings while the real work stays stuck.

And stuck is expensive.

Especially when patients, investors, regulators, and internal teams are all waiting for the same thing:

Movement.

FDA may be creating more room for efficient development.

Now sponsors have to do the harder part.

Use it well.