惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

雷峰网
雷峰网
WordPress大学
WordPress大学
MyScale Blog
MyScale Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
The Blog of Author Tim Ferriss
U
Unit 42
罗磊的独立博客
G
Google Developers Blog
Microsoft Azure Blog
Microsoft Azure Blog
The Cloudflare Blog
aimingoo的专栏
aimingoo的专栏
Vercel News
Vercel News
N
Netflix TechBlog - Medium
H
Hackread – Cybersecurity News, Data Breaches, AI and More
云风的 BLOG
云风的 BLOG
Hugging Face - Blog
Hugging Face - Blog
大猫的无限游戏
大猫的无限游戏
F
Fortinet All Blogs
博客园 - 聂微东
Stack Overflow Blog
Stack Overflow Blog
小众软件
小众软件
博客园 - 【当耐特】
H
Help Net Security
The GitHub Blog
The GitHub Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Quality culture vs quality theatre — what inspectors actu...
Priya Nair · 2026-04-28 · via DEV Community

Priya Nair

I’ve been on both sides of audits and inspections enough times to tell which companies have genuine quality culture and which are performing for the auditor. To be fair, the distinction isn’t always black-and-white — teams can be sincere but under-resourced — but inspectors are remarkably good at spotting theatre. In practice this means they look for repeatable behaviour, not polished slides.

Why the difference matters (beyond "tick-box" compliance)

Quality theatre gets you a tick on a checklist. Real quality keeps patients safe and reduces rework. Under MDR, the regulator expects manufacturers to implement an effective quality management system and produce Technical Documentation that reflects how the device is designed, produced and monitored (see MDR Article 10 and Annex I/II). Notified bodies and competent authorities assess not just whether you have processes, but whether they are effective.

Put differently: a neat training matrix satisfies Annex IX documentary requirements, but it does not demonstrate that training has a measurable impact on non-conformities, CAPAs, or supplier quality. Inspectors know that.

What inspectors actually look for

During an audit they don’t watch your slide deck; they watch your people and records. Things that raise confidence:

  • Staff can explain their daily tasks and how those tasks feed the QMS — not recite policy language, but describe actions and consequences.
  • CAPAs show depth: clear detection point, robust root cause analysis, effective corrective actions, and verification that the actions actually reduced recurrence. CAPA-driven risk assessment is a real differentiator here.
  • Findings convert to quality events quickly. When a complaint or audit finding appears, it should already be in your change-control/CAPA workflow with traceability to affected product lots and relevant documents.
  • Trend analysis that drives decisions — e.g., supplier trend that triggered a supplier audit or design risk control.
  • Management review that discusses effectiveness metrics, not just status updates. Demonstrable decision-making (budget, resource changes, escalation) is what counts.
  • Evidence of continuous monitoring: post-market surveillance, PMCF activities where applicable, and complaint handling that closes the loop back to design and production.

And the things that set off alarm bells:

  • Reams of "evidence" created immediately before the audit: training records with identical timestamps, last-minute risk assessments, or "corrective action" entries with no follow-up evidence.
  • Overly rhetorical management review documents with no resource allocation or measurable outcomes.
  • CAPAs closed with procedural changes only, without verified effect.
  • Documents that claim "all good" with no data: no trends, no returns, no supplier performance metrics.

Concrete behaviours that separate culture from theatre

From my time defending Technical Files to notified bodies, the following patterns appear again and again.

Quality culture — what I see:

  • Engineers show me the non-conformance log and point to a recurring item. They explain the workaround and the long-term fix that’s in progress.
  • Supplier QRs are embedded in procurement: supplier scorecards feed supplier audits, and poor scores create automatic escalation.
  • Findings immediately spawn a quality event (not a separate, detached spreadsheet). The whole chain — finding → investigation → CAPA → verification — is traceable.
  • Staff discuss "why" rather than "who". Root cause analysis actually looks for system causes, not person-fault.

Quality theatre — what I see:

  • The QMS folder is immaculate, but no one outside QA knows how to record a complaint or initiate a CAPA.
  • Training completion is 100 per cent on paper, but producers revert to informal processes on the line because the documented process is unusable.
  • A mountain of "continuous improvement" forms that are never prioritised; they live in a backlog, never implemented.

Practical steps to move from theatre to culture

I work in a mid-sized company where resourcing is always under pressure, so these are realistic, actionable steps I’ve used or defended with notified bodies.

  • Make findings into events, not files: ensure every audit finding, customer complaint, and non-conformance automatically creates a traceable quality event in your QMS. This reduces theatre and increases accountability.
  • Link CAPA to risk and design control: require CAPA owners to complete a CAPA-driven risk assessment that updates the risk file and design documentation where relevant.
  • Use native workflow integration (or at least connected workflow) so change control, CAPA, and document control aren’t siloed. In practice this means you can follow a single item from detection to verification without manual stitching.
  • Train for competency, not completion: require demonstrable competence (observed work, quizzes focused on scenario-based tasks), not just a signed attendance list.
  • Make management review meaningful: present decisions framed as risks, options, and resources required. If the review doesn’t change anything, you should ask why you held it.

To be clear: automation helps, but it is not a cure-all. Automated CAPAs and AI-assisted triage can speed detection and classification, but the underlying quality judgement must still be human, reviewable, and traceable.

What I tell teams before an audit

I tell them: expect questions that start "why". Be prepared to show how a single complaint influenced a change in product, supplier oversight, or instructions. Bring the chain of evidence. If you can’t show it, you have theatre, not culture.

Inspectors have limited time. They will make sampling decisions based on what people say in interviews and whether records are coherent. So rehearsed answers are less useful than being able to walk through a real example — a closed CAPA with evidence of verification, or a supplier escalation that led to a documented decision.

What have you done that actually changed behaviour in your company — one small procedural change that killed quality theatre and produced repeatable culture?