Bridging the Gap: Encouraging a Quality Mindset Without Friction

Exploring practical, respectful ways for teams to collaborate, reduce friction, and build a proactive GMP culture

Working in Quality Assurance (QA) can be professionally and emotionally demanding. Much of the role involves raising process deviations, challenging entrenched habits, and enforcing regulatory requirements in which colleagues may not immediately see the value. Over time, this can strain relationships – QA can be perceived as the team that stops work, rather than the partner who keeps patients safe and protects the organisation’s licence to operate. But a quality mindset is an ethos that needs to be shared by the whole organisation, not just QA.

In this blog we’ll review some practical approach to rebuilding that partnership, suggesting ways QA personnel can inspire a positive, proactive quality mindset across operations, laboratories, engineering, supply chain and support functions, and offering suggestions for non‑QA colleagues who want to communicate more effectively with QA.

The goal of us all is shared: to embody a Quality culture that safeguards patients through compliant, efficient, right‑first‑time manufacturing.

Why tension emerges – and why it matters

Tension between colleagues rarely comes from bad intent. It more often arises because of legitimate pressures that pull personnel in different directions: production needs throughput; engineering needs uptime; supply chain needs batch release; QA needs evidence, traceability and regulatory compliance. Add shift pressures, complex documentation, and audit findings, and you have a recipe for frayed tempers.

Activitely recognising this context helps staff to depersonalise the issue. Instead of ‘QA versus operations’, reframing the situation as ‘our process versus our patient risk’ can open a way forward to more constructive conversation. When everyone working with a quality mindset and anchoring their decisions on patient safety and product quality, disagreements can become process problems to be solved together – not personal conflicts.

Principles for QA: Creating pull rather than push

Sustained quality compliant behaviours are more likely to be adopted when people understand the why and feel ownership. Creating a “pull” through shared purpose, risk clarity, and consistency is more effective than “push” approaches that rely on policing or authority alone.

Starting with purpose

Beginning conversations with the “why” – protecting patients, ensuring batch release without rework, sustaining the site’s reputation and licence – aligns everyone around shared positive outcomes. People tend to support what they help define; inviting colleagues to articulate the patient impact in their own words is building ownership.

Coaching not catching

Shifting from ‘policing’ to ‘coaching’ can reduce defensiveness. Pose curious questions (e.g., ‘What would make this easier to do right first time?’) and use ‘show me’ walk‑throughs to help reveal constraints and improvement ideas that a checklist alone might miss.

Focusing on risk

Linking requirements to tangible risks – mix‑ups, contamination pathways, data integrity failure modes – helps colleagues see why a control is necessary. Using simple risk language and heat maps during on‑the‑floor conversations can help demystify QA decisions, avoiding the impression of arbitrary rules.

Being predictably consistent

Consistency builds trust. Being clear about what is negotiable (formatting, sequencing) and what is non‑negotiable (critical control points, verification steps) helps teams plan work. Publishing ‘non‑negotiables’ as a visual one‑pager might help reduce conflict in the moment.

Recognising good quality behaviours

Catching (and calling out) people doing the right thing (timely deviations, cleanroom discipline, clear batch record) even if it’s privately, not publicly, reinforces the culture you want. Recognition in forums such as shift meetings or dashboards signals that quality behaviour is expected and matters, not just output.

Making the right way the easy way

Where procedures are hard to follow, human factor errors can multiply. Co‑design SOPs and batch records with operators, simplify wording, and remove redundant steps to make compliance less effortful – an effect that will be welcomed by all. Quick‑reference visuals at the point of use (e.g. QR codes, annotated photos) can improve adherence without extra policing.

Practical techniques QA can try this month

Practice makes perfect! Try these tools to embody a positive Quality culture in your workplace:

Using a shared language for issues

Adopting a simple, blame‑free naming system for deviations (e.g., process design gap, equipment reliability, knowledge/skill, workload/shift pressure, human factors) can encourage accurate reporting. When colleagues see that ‘human error’ is not a dumping ground for blame, improved openness should follow.

Applying a coaching script in walk‑throughs

Plan some open questions appropriate to the scenario:

What makes this step tricky?
Where are you tempted to shortcut?
What hazards are we controlling here?
What would help you get this right every time?

Practicing these questions could help you develop a calm, inquisitive rather that interrogatory tone, even under time pressure.

Storytelling with near misses

Sharing anonymised, short case studies can makes abstract rules concrete. Ask your colleagues from across all departments to share their experiences. It will build a bank of local stories that anchor quality to real quality consequences but also solutions.

Visualising ‘non‑negotiables’ at the line

Designing small posters or laminated cards that list, for example, the top five critical behaviours for each area (e.g., gowning sequence, line clearance checks) reduces reliance on memory and long procedures.

Closing the loop visibly

When QA says ‘no’, being explicit about the pathway to ‘yes’:

What evidence is needed?
What revalidation or verification will suffice?
What timeline is realistic?

Publishing decisions and rationales in a shared space prevents rumours and misunderstanding and reduces repeated escalations.

Partnering for speed and compliance: Suggestions for non‑QA colleagues

Building a meaningful and respectful working relationship with a quality mindset shouldn’t be entirely the responsibility of QA. Here are some suggestions for all departments, including Production, Engineering, Supply Chain, so that the responsibility for on-site Quality can be shared:

Bringing QA in early: Involving QA at the concept stage of changes avoids late surprises. Early input on validation, data integrity and documentation can streamline delivery and prevent the need for rework.
Framing problems with context and evidence: When raising issues, summarising the intended outcome, the observed problem, the potential patient or compliance risk, and what has already been tried, will speed up triage. Screenshots, batch record extracts and photos make it easier for QA to respond constructively.
Asking for the rationale: If a requirement seems onerous, ask why it matters in risk terms rather than assuming bureaucracy. Understanding the hazard can reveal simpler, compliant alternatives that achieve the same control objective.
Proposing options, not ultimatums: Offering two or three viable, compliant paths – with pros and cons – invites QA to choose rather than defend. This collaborative approach reduces conflict and accelerates agreement.
Owning the fix and the follow‑through: Where a deviation occurs, documenting immediate containment, short‑term correction and the plan for sustainable prevention (e.g., training, SOP update, error proofing) demonstrates accountability and earns trust.

Communicating about problems without blame

Emotions run high when batches, investigations or audits are on the line. A simple structure can help teams stay factual and respectful:

Stating purpose up front: ‘I’m raising this so we protect patients and keep release on track.’ This signals intent and reduces defensiveness.
Describing facts neutrally: What was expected, what happened, where and when; avoid negative labels like ‘careless’ or ‘sloppy’.
Exploring contributing factors: Looking at task design, tools, environment, knowledge, workload, and human factors. This widens the lens beyond the individual.
Agreeing risk and next steps: Aligning on immediate containment, evidence required, decision‑maker and timeline. Confirm in writing to avoid drift.

Building skills: Micro-capabilities that change culture

Cultural change is an incremental process. Taking small steps will still get you to where you need to be:

Giving and receiving feedback kindly: Practising ‘observe – impact – invite’ statements keeps feedback specific and respectful. For example: ‘When the line clearance sign‑off is skipped, we increase mix‑up risk. Would adding a visual cue help this step?’
Making decisions with risk clarity: Using simple risk scoring and pre‑agreed criteria for go/no‑go decisions avoids inconsistency. Publishing these in area playbooks helps shifts act with confidence when QA is not immediately available.
Writing for users, not auditors: Drafting SOPs in plain language with photos or short videos increases adherence and reduces deviation risk. Auditors value clarity that helps operators do the job right.
Learning from every deviation: Treating deviations as process feedback – not personal failure – encourages early reporting. Closing the loop with ‘what changed’ reinforces that learning is real, not performative.

When a small misunderstanding can become an improvement action

On one site, recurring tension arose around line clearance. Operators felt the process slowed changeovers, while QA remained concerned due to previous near‑miss events. During a routine changeover, an operator discovered a stray printed label hidden beneath equipment – a step usually rushed because it ‘never found anything’.

QA paused the restart and calmly explained the risk: a single overlooked label could lead to mislabelling, batch rejection, or a recall with patient impact. Rather than escalating blame, QA shared an anonymised industry example showing how similar oversights had resulted in regulatory action.

That conversation shifted understanding. The team collaboratively mapped line‑clearance hotspots and simplified checklist wording into clearer, action‑based steps. Within weeks, changeovers became faster and more consistent. A moment of misunderstanding became a practical improvement, and trust between QA and operations noticeably improved.

What good looks like: signs your Quality culture is shifting

How will you know the relationship between QA and the rest of the site is improving? You might notice:

Earlier involvement of QA in change controls and investigations
Fewer last‑minute escalations and more planned, risk‑based decisions
Cleaner batch records and more consistent adherence to ‘non‑negotiables’
Increased reporting of near misses and richer root‑cause analyses
Faster, calmer responses during audits and walkthroughs
Higher engagement scores in quality climate or culture surveys

Practical next steps you could pilot this quarter

Creating a one‑page ‘Quality Non‑Negotiables’ for each area: Co‑author with operators and QA, laminate at the line, and review monthly in shift huddles.
Refreshing two high‑risk SOPs for usability: Run a 60‑minute co‑design session with operators to simplify wording, add visuals and remove ambiguity.
Introducing a 10‑minute weekly ‘Near Miss Story’: Share one local example with a ‘risk, fix and learning’. Rotate presenters to build ownership.
Piloting a coaching walk‑through script: Train supervisors and QA to use the same open questions. Collect three improvement ideas per area and implement at least one.

Closing thoughts

Quality is everyone’s job, but QA carries the daily burden of protecting patients when pressure is highest. By reframing conversations around shared purpose, simplifying systems so the right way is the easy way, and practising steady, respectful communication, teams can reduce friction and deliver safer products with less stress.

If your site would benefit from facilitation, SOP usability redesign, or tailored training in risk‑based decision‑making and human factors, PharmOut can partner with you to make these changes practical and sustainable.

This blog is the sixth in the Celebrating Quality series. For more reading about being a Quality professional, please read:

How PharmOut can help

PharmOut can support your organisation by translating quality principles into practical, sustainable improvements. Our consultants help redesign SOPs, streamline GMP processes, enhance human‑factor resilience, and build stronger QA–operations partnerships. By offering tailored training, facilitation and risk‑based guidance, we help teams embed a confident, proactive quality mindset across the site.

Explore elearning and public courses via onlinegmptraining.com, or contact us via the website or via email to tailor workshops to your needs, such as technical writing, root cause analysis, and CAPA effectiveness.

Frequently Asked Questions (FAQ)

How can QA reduce friction when raising issues with Production?

Using a coaching‑oriented approach, framing discussions around patient safety, and explaining the risk context behind decisions can help reduce defensiveness and build shared understanding.

What should operators do if they disagree with a QA decision?

Asking for the rationale respectfully, providing evidence, and proposing compliant alternative options can support constructive dialogue and accelerate agreement.

How can teams encourage earlier involvement of QA in project changes?

Inviting QA into concept discussions and change‑control planning ensures compliance considerations are identified early, preventing rework and last‑minute escalations.

What practical steps help build a stronger culture of quality on the shopfloor?

Co‑designing SOPs, using visual non‑negotiables, sharing near‑miss stories, and practising simple feedback techniques all help embed quality into daily routines.

How can communication about deviations be made less confrontational?

Focusing on facts, avoiding blame‑based language, and exploring contributing factors such as environment, workload, and human factors leads to clearer, calmer conversations.

What signs indicate that the QA–operations relationship is improving?

You may notice earlier QA engagement, more consistent adherence to critical behaviours, richer root‑cause analysis, increased near‑miss reporting, and smoother audit performance.