Why More QA Resource Doesn’t Always Solve the Problem

When everyone is busy, more people feel like the obvious answer

The audit schedule is slipping.

CAPAs are taking too long to close.

Documents are waiting for review.

Vendor oversight activity is happening, but not always with the level of confidence leaders would like.

Clinical or preclinical teams are pushing work forward, but QA seems to be where everything slows down.

The quality team is working hard. The operational teams are frustrated. Senior leaders are asking why things are not moving faster.

At that point, the answer can seem obvious:

“We need more QA resource.”

Sometimes, that is true.

There are points in every growing organisation where the volume of work exceeds the capacity available. A temporary contractor, additional QA support, an external auditor, or specialist project help may be exactly what is needed.

But not always.

In many pharmaceutical R&D and GxP-regulated organisations, resource pressure is real, but it is not the whole problem. It is the visible symptom of something deeper.

The issue may be unclear ownership.

It may be poorly designed processes.

It may be too many review loops.

It may be late QA involvement.

It may be weak prioritisation.

It may be an operating model that made sense when the organisation was smaller, but no longer supports the work being done.

If that is the case, adding more QA resource may provide short-term relief without solving the real problem.

It can even make the system more expensive while leaving the underlying friction untouched.

The better question is not simply:

“How many more people do we need?”

It is:

“What is creating the pressure in the first place?”

Resource pressure is often a symptom, not the root cause

When QA is under pressure, the symptoms are usually easy to see.

You might notice:

• audit reports taking longer than expected;

• delayed review of study documentation;

• repeated CAPA extensions;

• quality input arriving too late in projects;

• vendors not being assessed or followed up consistently;

• CSV activities becoming stuck between QA, IT, users and suppliers;

• training records being completed but competence still feeling uncertain;

• senior leaders relying on one or two key people to hold the system together.

These are all legitimate concerns.

But they do not automatically prove that the organisation simply needs more QA people.

A document waiting in QA may have arrived late, incomplete or poorly prepared.

A CAPA delay may reflect unclear ownership, weak root cause analysis or actions that were never realistic.

A vendor oversight issue may not be caused by lack of audit resource, but by the absence of a meaningful oversight model.

A CSV delay may not be caused by QA being slow, but by unclear intended use, poor supplier documentation or nobody agreeing who owns the process.

A stretched QA manager may not only need another pair of hands. They may need better escalation routes, clearer authority, stronger leadership support and a quality system that does not depend on heroic individual effort.

This is why resource pressure deserves diagnosis before action.

If the real problem is workload, additional resource may help.

If the real problem is system design, additional resource may simply feed the system that is already struggling.

Why adding people feels so attractive

Adding people is attractive because it is tangible.

It feels practical. It gives leaders something visible to do. It shows the team that the problem has been heard. It can reduce immediate pressure, and, in some situations, it is absolutely necessary.

It is also easier than asking harder questions.

For example:

• Why do documents need so many review cycles?

• Why is QA being asked to solve issues that should have been prevented earlier?

• Why are CAPAs being extended rather than completed effectively?

• Why is vendor oversight dependent on individual memory and spreadsheets?

• Why are operational teams unclear about what QA needs from them?

• Why do quality decisions escalate slowly or inconsistently?

• Why does everyone feel busy, but progress still feels slow?

Those questions can be uncomfortable because they move the conversation away from headcount and towards leadership, process, culture, ownership and decision-making.

But that is where many quality performance issues actually live.

The issue is rarely that nobody cares.

In most organisations, people are working hard and trying to do the right thing. The problem is that the system around them makes good work harder than it needs to be.

Adding people to that system may help temporarily.

Improving the system helps permanently.

What this looks like in practice

Consider a small preclinical organisation preparing for more formal regulated work.

The scientific team is growing. Studies are becoming more complex. More records need review. Quality expectations are increasing. The QA lead is competent and committed but is being pulled into everything: SOPs, training, audits, vendor questions, study documentation, deviation review, CAPA, management updates and informal advice.

The organisation concludes that QA is under-resourced.

That may be true.

But when the situation is examined more closely, several other issues appear.

Operational staff are unsure which quality decisions they can make themselves and which need QA input.

SOPs are written in a way that creates unnecessary review burden.

Study teams involve QA too late, so preventable issues arrive at the point of review.

CAPAs focus on actions rather than meaningful root cause.

Vendor oversight is treated as an audit event rather than an ongoing control process.

Senior leaders want quality assurance, but they have not clearly defined what level of quality maturity the organisation is trying to build.

In that context, bringing in extra QA support may clear some immediate work.

But unless the organisation also addresses ownership, process design, decision routes and quality maturity, the same pressure will return.

Now consider a small clinical sponsor relying heavily on CRO and vendor delivery.

The sponsor receives reports, attends meetings and reviews trackers. Yet there is a lingering concern that oversight activity is not giving the organisation enough real control. Issues emerge late. TMF quality is difficult to interpret. Escalations feel reactive. The internal team spends too much time trying to understand what is really happening.

Again, the problem may look like insufficient quality resource.

But the deeper issue may be sponsor oversight design.

Who is looking at which signals?

What is escalated, when, and to whom?

Which risks are being monitored actively?

What evidence shows that the sponsor has not only received information, but used it to make informed decisions?

In this situation, adding another person to attend more meetings or review more documents may help, but only if the oversight model itself is sound.

The core problem is not always lack of effort.

It is lack of clarity.

The hidden cost of adding resource too quickly

When organisations add resource before understanding the system, several risks appear.

The first is cost without improvement.

More people are brought in, but delays continue because the work still moves through unclear processes, duplicated reviews or weak decision points.

The second is false reassurance.

A bigger QA team can create the impression that risk is better controlled, even if the underlying controls are still poorly designed.

The third is dependency.

External support becomes a way of keeping the system moving without addressing why the internal system cannot sustain itself.

The fourth is frustration.

Contractors, consultants or additional staff may be blamed for slow progress, when the real barriers sit in the organisation’s processes, leadership expectations or cross-functional behaviour.

The fifth is missed opportunity.

The organisation spends money on capacity when the bigger gain would have come from simplifying work, clarifying responsibilities, improving prioritisation or strengthening internal capability.

None of this means additional resource is wrong.

It means additional resource should be introduced into a system that has been understood.

Otherwise, you risk treating pressure as the problem, when pressure is only the evidence that the problem exists.

The difference between capacity pressure and system pressure

A useful distinction is the difference between capacity pressure and system pressure.

Capacity pressure means there is genuinely more work than the available people can reasonably complete. The process is sound, the responsibilities are clear, the standards are understood, but the volume is too high.

System pressure means the work is harder than it needs to be because the system around it is unclear, inefficient or poorly designed.

These can look similar on the surface.

Both create delays.

Both create frustration.

Both make teams feel overwhelmed.

But they require different responses.

This distinction matters because the solution changes.

Capacity pressure may require more people.

System pressure requires better design.

Many organisations have both. The mistake is assuming that because capacity is part of the issue, it is the whole issue.

Questions leaders should ask before adding QA resource

Before adding resource, it is worth asking a few practical questions.

1. Where exactly is the pressure appearing?

Is the pressure in audit delivery, report writing, document review, CAPA follow-up, vendor oversight, CSV, training, inspection readiness or day-to-day advice?

“QA is busy” is too broad to be useful.

The more specifically the pressure is described, the easier it becomes to understand whether the problem is volume, process, ownership or capability.

2. Where is the pressure being created?

This is a different question.

The delay may appear in QA, but it may be created upstream.

A document review delay may begin with poor document preparation.

A CAPA delay may begin with weak investigation.

A vendor issue may begin with unclear expectations at qualification.

A CSV problem may begin before validation starts, when intended use and ownership were not properly defined.

The visible queue is not always the origin of the problem.

3. Is the work clearly prioritised?

A stretched QA team cannot treat everything as equally urgent.

If prioritisation is weak, more resource may simply allow more low-value activity to continue.

Leaders should ask:

Which work genuinely protects patient safety, data integrity, regulatory confidence, scientific credibility or business continuity?

Which work is routine but necessary?

Which work is being done because “we always do it this way”?

Which work could be simplified, risk-based or stopped?

Quality resource should be directed where it creates the greatest protection and value.

4. Are responsibilities clear outside QA?

QA pressure often increases when operational teams are unclear about their own quality responsibilities.

If teams believe that quality is something QA checks at the end, QA will always become a bottleneck.

In a healthier model, operational teams understand what they own, what good looks like, when to involve QA, and when to escalate.

QA should provide assurance, challenge, advice and oversight.

It should not become the organisation’s final safety net for every unclear process.

5. Are you asking QA to compensate for poor system design?

This is one of the most important questions.

If SOPs are too complex, QA will spend more time explaining and correcting them.

If templates are unclear, review cycles will increase.

If decision rights are vague, issues will bounce between people.

If vendor oversight is not risk-based, effort will be spent in the wrong places.

If leadership expectations are unclear, QA will be pulled between compliance, delivery and organisational politics.

In that situation, more QA resource may help people cope.

But it will not necessarily make the system better.

When more resource is the right answer

There are times when more resource is absolutely appropriate.

For example, additional support may be needed when:

• there is a temporary spike in audit demand;

• a key person is absent or leaving;

• a major project requires specialist input;

• the organisation is entering a new regulated area;

• a clinical or preclinical programme has grown beyond existing oversight capacity;

• an inspection, sponsor audit or vendor qualification creates short-term pressure;

• specific technical expertise is not available internally.

In these situations, external support can be extremely valuable.

The important point is to match the support to the need.

If the need is defined delivery, a contractor or auditor may be appropriate.

If the need is specialist judgement, a consultant may be more valuable.

If the need is internal development, mentoring or coaching may create more sustainable benefit.

If the need is both immediate relief and longer-term improvement, a blended approach may be needed.

For example, an organisation might bring in external audit support while also reviewing whether the audit programme is risk-based and appropriately prioritised.

Or it might use specialist CSV support while also clarifying internal ownership of system lifecycle management.

Or it might support a new QA manager through mentoring while reviewing the quality operating model around them.

The strongest solutions are often not simply “more resource”.

They are the right resource, used in the right way, for the right problem.

What better looks like

A better approach starts by stepping back before acting.

Not for months. Not through unnecessary analysis. But enough to avoid buying the wrong solution.

A practical resource diagnostic might look like this:

1. Define the visible pressure.

   What is delayed, overloaded, inconsistent or causing concern?

2. Identify where the pressure begins.

   Is it created in QA, or does it arrive there from elsewhere?

3. Separate volume from friction.

   Is there too much work, or is the work harder than it needs to be?

4. Clarify the risk.

   What could happen if nothing changes? Delay, inspection exposure, weak sponsor oversight, staff fatigue, poor data integrity, vendor failure, loss of confidence?

5. Decide the support type.

   Do you need capacity, independent assessment, expert advice, mentoring, or strategic review?

6. Build internal learning into the solution.

   How will the organisation become clearer, more capable or more controlled as a result?

This does not need to be complicated.

But it does need to be deliberate.

The leadership issue behind QA resource pressure

QA resource problems are rarely only QA problems.

They are often leadership signals.

They may show that the organisation has outgrown informal ways of working.

They may reveal that quality expectations have increased but operating models have not matured.

They may indicate that QA is being expected to provide control without enough authority.

They may show that operational teams are unclear about their responsibilities.

They may reveal that leaders are using QA as a buffer between scientific ambition and regulated reality.

This is why the conversation matters.

If leaders treat QA pressure only as a staffing issue, they may miss the opportunity to build a better organisation.

If they treat it as a performance signal, they can ask more useful questions.

What work should QA be doing?

What work should operational teams own?

Where are decisions getting stuck?

Where are we creating unnecessary review burden?

Where are we relying too heavily on individual knowledge?

Where would better systems reduce pressure without reducing control?

Where would mentoring or capability development give us more resilience?

These are not abstract questions. They affect delivery, cost, confidence, inspection readiness, staff retention and the credibility of the organisation’s research.

The bottom line

More QA resource can be the right answer.

But it should not be the automatic answer.

When quality teams are stretched, the visible pressure may be caused by genuine workload. It may also be caused by unclear ownership, poor process design, weak prioritisation, late QA involvement, ineffective oversight, overcomplicated systems or insufficient internal capability.

If you add people without understanding the cause, you may buy temporary relief rather than lasting improvement.

The better decision is to diagnose the pressure first.

Then decide whether you need capacity, assurance, advice, mentoring, or a more strategic review of how quality work is designed and governed.

In regulated R&D, the goal is not simply to have enough people to keep up.

The goal is to build a quality approach that protects the science, supports the business, and gives leaders confidence that the organisation is genuinely in control.

What to do next

If your organisation is feeling QA resource pressure, it may be tempting to move straight to recruitment, contracting or outsourcing.

That might be the right step.

But before you do, it is worth asking whether the pressure is mainly caused by volume, friction, unclear ownership or a system that has become too dependent on a few stretched individuals.

Headway Quality Evolution works with pharmaceutical R&D and GxP-regulated organisations to understand the real causes behind quality pressure, resource strain and operational friction.

That may lead to external QA support. It may lead to an audit or independent review. It may lead to strategic consultancy, vendor oversight improvement, CSV guidance, QA mentoring, leadership support or a more proportionate quality operating model.

The starting point is not assuming that more resource will solve the problem.

The starting point is understanding what kind of problem you actually have.