The Hidden Cost of Organisational Friction in Pharmaceutical R&D

When everyone is working hard, but progress still feels slow

The study team has done its part.

The laboratory is waiting for approval.

QA is reviewing the documentation.

The vendor has responded, but not quite to the question that was asked.

A CAPA action is technically open, although nobody is entirely clear what decision is needed to move it forward.

The next meeting is already in the diary.

Everyone is busy. Everyone is trying. Nobody is deliberately blocking progress.

And yet the work still feels slow.

This is one of the most frustrating patterns in pharmaceutical R&D and GxP-regulated organisations. The visible problem often appears as delay, rework, repeated questions, unclear escalation, late-stage quality issues or pressure on QA. But the deeper issue is not always lack of effort, lack of competence or lack of compliance knowledge.

Often, the real issue is organisational friction.

Organisational friction is the drag created when people, processes, systems, teams and decisions do not connect cleanly. It appears in the spaces between departments. It builds up around handoffs, unclear ownership, duplicated reviews, poorly designed processes, unresolved decisions and communication gaps.

It rarely arrives dramatically.

It accumulates quietly.

A study takes longer than expected. A document goes through five review cycles. A vendor issue is discussed several times before anyone decides what to do. QA is involved late and then blamed for slowing the work down. A system is implemented before intended use is fully understood. A CAPA remains open because the action is written, but the real cause has not been addressed.

None of these problems may look serious on their own.

Together, they drain time, confidence, energy and control.

The hidden cost of organisational friction is that it makes good people less effective.

R&D delay is often created between teams

When work slows down, leaders often look for the team responsible.

Is QA taking too long?

Is operations preparing poor documentation?

Is the vendor underperforming?

Is the study team disorganised?

Is clinical operations overloaded?

Is the laboratory not communicating clearly?

Sometimes, the answer really does sit within one function. But very often, the delay is created between functions.

A study team may believe a document is ready for QA review, but QA is expecting a different level of detail.

A vendor may believe an issue has been escalated, but the sponsor does not believe enough information has been provided to make a decision.

A laboratory may be ready to progress, but a quality decision is waiting on input from someone who does not realise they are the decision owner.

A clinical team may assume the CRO is managing an issue, while the CRO is waiting for sponsor direction.

A QA manager may ask for clarification because the SOP, protocol or project plan does not make ownership clear.

Nobody is necessarily wrong.

The system is unclear.

That is why organisational friction is so difficult to see. Each team can be working reasonably within its own view of the world, while the organisation as a whole loses momentum.

This is especially common in growing organisations. Informal ways of working can carry a small team surprisingly far. People know who to ask. Decisions happen through conversation. The same individuals hold the organisational memory.

But as the organisation grows, the informal system starts to strain.

More studies. More vendors. More systems. More regulated work. More people. More handoffs. More documentation. More leaders wanting visibility. More pressure to keep pace.

At that point, the organisation does not just need more activity.

It needs clearer connection.

What organisational friction looks like in practice

Organisational friction can show up in many ways.

It may appear as slow document review, but the real cause is unclear expectations about what “ready for review” means.

It may appear as a QA bottleneck, but the real cause is late QA involvement in study planning or process design.

It may appear as recurring CAPA delays, but the real cause is weak root cause analysis, unrealistic actions or unclear action ownership.

It may appear as vendor underperformance, but the real cause is poor service-level clarity, weak escalation routes or lack of risk-based oversight.

It may appear as inspection-readiness anxiety, but the real cause is that evidence has been generated in fragments and does not tell a coherent story.

It may appear as CSV complexity, but the real cause is that nobody has clearly agreed what the system is intended to do, what risk it creates, or who owns the process.

It may appear as staff frustration, but the real cause is that people are repeatedly asked to compensate for unclear systems.

That last point matters.

In regulated R&D, people often absorb friction personally. They work longer hours. They chase responses. They rewrite documents. They sit in extra meetings. They hold knowledge in their heads. They step around weak processes because the work still needs to move.

This can create an illusion of control.

The organisation appears to be functioning because committed people are making it function.

But that is not the same as a resilient operating model.

If progress depends on the memory, goodwill or personal effort of a few individuals, the organisation is more fragile than it may realise.

The business cost is bigger than the visible delay

The most obvious cost of friction is lost time.

But time is only one part of the problem.

Organisational friction also creates rework. Documents are revised repeatedly because expectations were not clear at the start. CAPAs are reopened because the original action did not address the real cause. Vendor issues are revisited because earlier discussions did not lead to clear decisions.

It creates poor use of expert time. Senior scientists, QA leads, project managers and operational leaders spend time clarifying, chasing, correcting and interpreting rather than doing the work that most needs their expertise.

It creates decision fatigue. When ownership is unclear, too many issues require escalation. Leaders become involved in operational details that should have been resolved earlier. Teams wait for decisions that nobody has been clearly authorised to make.

It creates inspection vulnerability. Not because the organisation has done nothing, but because the evidence is fragmented. It may be difficult to show what happened, why it happened, who knew, what was decided, and how the organisation controlled the risk.

It creates poor sponsor or management control. Dashboards, reports and meetings may exist, but leaders may still not have confidence that the right signals are being seen early enough.

It creates cultural damage. Teams start to blame each other. QA becomes “the blocker”. Operations becomes “the source of poor-quality inputs”. Vendors become “unreliable”. Leaders become “too far removed”. The system problem becomes a people story.

And once that happens, organisations can spend a great deal of energy managing symptoms rather than improving performance.

Why friction is often mistaken for a QA problem

QA often becomes the place where organisational friction becomes visible.

That does not mean QA created the friction.

By the time an issue reaches QA, the cause may already be embedded in earlier decisions, unclear expectations or incomplete ownership.

For example, a study document may reach QA late because the team underestimated how much review was needed. QA then becomes the visible source of delay, even though the timeline was unrealistic from the beginning.

A CAPA may sit open because the action owner has not understood what evidence is needed to show effectiveness. QA then becomes the team chasing closure, even though the action was poorly designed.

A vendor audit may identify repeated issues because previous performance signals were not reviewed or escalated effectively. QA then becomes associated with the finding, even though oversight weakness developed over time.

A CSV package may become stuck in review because user requirements, intended use and supplier evidence were not properly clarified before validation documentation was assembled. QA then appears demanding, when the real issue is that confidence was not built into the project early enough.

This is why leaders need to be cautious before asking whether QA is moving fast enough.

A better question is:

“What is arriving in QA, in what condition, and why?”

If QA receives unclear, incomplete or late inputs, the organisation should not be surprised when QA review becomes slow, difficult or repetitive.

QA can and should improve its own processes where needed. But in many cases, the bigger gain comes from improving the system around QA.

Friction hides inside normal working practices

One reason organisational friction persists is that it often hides inside practices that feel normal.

Meetings are normal.

Review cycles are normal.

Emails chasing clarification are normal.

CAPA extensions are normal.

Vendor follow-up is normal.

Escalation is normal.

Because these things are familiar, organisations stop questioning whether they are proportionate or effective.

The issue is not whether meetings, reviews, emails or escalations should exist. Of course they should, when they serve a purpose.

The issue is whether they are compensating for something that should be clearer.

A meeting may be useful. But if the same decision appears in three meetings without resolution, the meeting is not the control. It is evidence that the control is weak.

A review cycle may be necessary. But if the same type of document repeatedly needs extensive correction, the review is not the root solution. It is a signal that expectations, training, templates or ownership need attention.

An escalation may be appropriate. But if routine issues regularly need senior intervention, the organisation may have unclear decision rights.

A CAPA extension may sometimes be justified. But repeated extensions can suggest that the action was not realistic, the owner was not clear, or the root cause was not properly understood.

A vendor update may provide useful visibility. But if leaders still feel uncertain after receiving it, the oversight model may not be giving them the right information.

Friction is often found by asking:

“What are we repeatedly working around?”

A practical friction map

A useful way to diagnose organisational friction is to map where work loses momentum.

Not in abstract terms, but by looking at specific pieces of work and asking where time, clarity or confidence is lost.

This kind of mapping does not need to become a major project.

It can begin with one delayed study, one recurring CAPA, one vendor issue, one overloaded QA process or one inspection-readiness concern.

The goal is not to blame.

The goal is to see the system.

What organisations often do instead

When friction becomes painful, organisations often respond in predictable ways.

They add more meetings.

They create another tracker.

They ask QA to review more closely.

They add an approval step.

They rewrite an SOP.

They bring in temporary resource.

They escalate more often.

They ask people to communicate better.

Some of these actions may help. But they can also add more friction if they are not linked to the real cause.

A new tracker does not create ownership.

A meeting does not create decision rights.

An SOP does not create good judgement.

An extra approval step does not necessarily create control.

More QA review does not prevent poor-quality inputs.

A contractor does not fix an unclear process.

Communication reminders do not solve structural ambiguity.

This is not an argument against meetings, trackers, SOPs, approvals or external support. They all have their place.

The point is that adding more control activity is not the same as improving control.

In fact, too much poorly designed control activity can make organisations slower without making them safer, more compliant or more confident.

Good quality systems should reduce unnecessary friction.

They should not institutionalise it.

What better looks like

A lower-friction organisation is not one with fewer standards.

It is one where the standards are clearer, better understood and easier to apply.

In practice, that means people know what they own. They understand when QA needs to be involved. They know what good evidence looks like. Vendors understand expectations beyond the audit. Leaders receive information that supports decisions, not just activity updates. CAPAs address causes rather than symptoms. Systems are implemented around intended use rather than documentation burden.

A healthier organisation has fewer surprises.

Not because nothing goes wrong, but because issues are seen earlier, escalated appropriately and managed through clearer routes.

The handoffs are cleaner.

The decisions are more visible.

The evidence tells a better story.

QA is still independent, still challenging and still protective of quality. But it is not forced to compensate for avoidable confusion elsewhere in the system.

This is the important distinction:

The goal is not to remove all friction.

Some friction is necessary. Challenge, review and independent assurance are part of good quality. In regulated work, speed without control is not success.

The goal is to remove unnecessary friction.

The kind that does not protect patients, data, science, compliance or business performance.

The kind that makes work slower without making decisions better.

Questions leaders should ask

If your organisation is feeling slow despite high effort, these questions can help identify whether friction is part of the problem.

Where does work most often wait?

Where do the same questions keep recurring?

Where are decisions unclear or repeatedly escalated?

Where does QA become involved later than would be ideal?

Where do documents or records go through avoidable rework?

Where are vendors providing updates but not enough confidence?

Where do CAPAs close administratively but fail to change behaviour?

Where are people relying on informal knowledge rather than clear process?

Where are senior people spending time on issues that should not need senior attention?

Where are teams optimising their own work while creating difficulty for the next team in the chain?

These questions are not designed to create blame.

They are designed to move the conversation from “Who is slowing this down?” to “Where is the system creating drag?”

That shift matters.

Once the organisation can see where friction is created, it can make better decisions about process, resource, QA involvement, vendor oversight, training, mentoring, system design and leadership focus.

When external support helps

External support can be particularly useful when friction has become normal inside the organisation.

People inside the system often know where the pain is. But they may not have the time, independence or authority to step back and diagnose it properly.

They may also be too close to the work.

A team that has lived with a cumbersome process for years may stop seeing it as unusual. A QA lead may know the system is inefficient but feel unable to challenge it without external support. Leaders may see delay but not the sequence of handoffs and decisions that create it.

This is where consultancy can add value.

Not by producing a generic process improvement report.

Not by telling capable people what they already know.

But by helping the organisation see the pattern, understand what is driving it, and decide what to change first.

That might involve reviewing a quality operating model.

Mapping a process from scientific activity through QA review and final decision.

Examining why CAPAs repeat or extend.

Looking at how vendor oversight information flows to sponsor decision-makers.

Assessing whether SOPs support the work or create unnecessary burden.

Helping a QA leader influence more effectively across operational teams.

Supporting senior leaders to decide what quality maturity should look like for the organisation’s size, risk and ambition.

The best external support should improve control without creating dependency.

It should leave the organisation clearer about what matters, what can be simplified, where risk sits, and how people should work together.

The bottom line

Organisational friction is easy to underestimate because it rarely appears as one obvious failure.

It appears as waiting, chasing, rework, repeated meetings, slow decisions, unclear ownership, late QA involvement, vendor uncertainty, CAPA drift and inspection-readiness anxiety.

In pharmaceutical R&D, those symptoms matter.

They affect study delivery, data integrity, scientific credibility, sponsor control, staff workload, inspection confidence and business performance.

The answer is not always more people.

It is not always another SOP.

It is not always another audit.

Sometimes the answer is to understand where the organisation is losing clarity, confidence and momentum between teams.

R&D delay is often not caused by one slow team.

It is created between teams.

And that means the opportunity is also between teams: in the handoffs, decisions, responsibilities, conversations, systems and controls that determine whether work moves with confidence or gets stuck in organisational drag.

What to do next

If this reflects what is happening in your organisation, it may be worth stepping back before adding more resource, rewriting another procedure or commissioning another isolated review.

Headway Quality Evolution works with pharmaceutical R&D and GxP-regulated organisations to identify where quality, oversight, leadership and operational systems are creating avoidable friction.

That may involve strategic quality consultancy, process review, vendor oversight improvement, QA leadership support, inspection-readiness review, CSV guidance, mentoring or helping leaders build a more proportionate quality operating model.

The aim is not to make quality lighter by reducing control.

The aim is to make quality clearer, more effective and better connected to the way the organisation actually needs to work.

If your teams are busy but progress still feels slow, the issue may not be effort.

It may be friction.