Every quality manager knows the truth: ISO 13485 looks simple on paper. But implementing it? That's where reality hits hard. I've audited dozens of medical device manufacturers, and one pattern keeps emerging: Companies often miss the forest for the trees. They focus on individual requirements without seeing how everything connects. Here's what 15 years of working with quality management systems have taught me: 1. Core QMS Foundation ↳ Your quality system isn't just documentation—it's your operational backbone ↳ Start with clear processes before diving into procedures ↳ Remember: A good QMS should make work easier, not harder 2. Design Control Integration ↳ This isn't a checkbox exercise—it's your product development roadmap ↳ Link user needs directly to verification steps ↳ Make design reviews meaningful, not just meetings 3. Risk Management Evolution ↳ Stop treating risk management as a one-time exercise ↳ Build it into every process decision ↳ Use real-world data to challenge your initial assumptions 4. CAPA That Actually Works ↳ Most CAPAs fail because they solve symptoms, not causes ↳ Invest time in proper root cause analysis ↳ Track effectiveness checks like they matter—because they do 5. Post-Market Intelligence ↳ Your QMS should be learning and evolving ↳ Turn complaint trends into design improvements ↳ Use post-market data to validate your risk assumptions The secret to ISO 13485 success isn't in the standard's text. It's in how you make these elements work together seamlessly. Think of your QMS as a living system, not a stack of documents. P.S. What's your biggest challenge in making these elements work together? ⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡⬡ MedTech regulatory challenges can be complex, but smart strategies, cutting-edge tools, and expert insights can make all the difference. I'm Tibor, passionate about leveraging AI to transform how regulatory processes are automated and managed. Let's connect and collaborate to streamline regulatory work for everyone! #automation #regulatoryaffairs #medicaldevices
Quality Management Systems Advice
Explore top LinkedIn content from expert professionals.
Summary
Quality management systems (QMS) are organized frameworks that guide companies in consistently delivering products and services that meet customer and regulatory requirements. These systems go beyond documentation—they support continuous improvement, risk management, and accountability across the entire organization.
- Update procedures regularly: Make sure your standard operating procedures are clear, accessible, and reflect real-world processes so teams know what to follow and why it matters.
- Encourage open feedback: Create a work environment where people feel safe to speak up about issues or mistakes, turning problems into opportunities for improvement rather than sources of blame.
- Share quality ownership: Promote a mindset where every department, not just QA, understands its role in maintaining and improving quality throughout product development and daily operations.
-
-
📢 "Our QMS should serve us, not the other way around!" 📢 This was a key message in our All Hands Meeting yesterday as we kicked off a company-wide initiative to revitalise our processes. As an ISO 13485 certified manufacturer, we know robust processes are vital in meeting quality objectives - but they need to work for the teams using them. Otherwise the fundamental purpose of a QMS - a set of processes and procedures that ensure a business consistently meets customer requirements and delivers quality products and services - is undermined. ❤️ I might have pushed the boat out a little too far when I suggested that it might even be possible to love an SOP but we live in hope. ⚠️ Here are 5️⃣ warning signs your SOPs might need a refresh (and how to fix them): 1️⃣ The "Optional" Perception When teams view SOPs as optional guidelines rather than essential tools, it often signals a disconnect between process and purpose. Make the link explicit between SOPs and quality outcomes. Attaching meaningful metrics to SOPs can further strengthen this link - does the SOP do what it’s meant to do? 2️⃣ The Knowledge Gap If your team doesn't know SOPs exist or where to find them, centralisation is key. In SaMD development, tribal knowledge isn't enough - we need consistent, accessible, controlled documentation. 3️⃣ The Utility Problem SOPs should be written by and for the people doing the work. In SaMD development, this means ensuring procedures reflect actual workflows while meeting regulatory requirements. A good test for whether a process is useful: does anyone want to own it?! 4️⃣ The Trust Issue Outdated or incorrect SOPs erode confidence. Create clear paths for updates and feedback - quality systems should evolve with processes. 5️⃣ The Perfectionist Trap An SOP needs to be practical yet comprehensive - a difficult balance to strike! Too much can be as problematic as too little. Make SOPs skimmable with clear checklists for validation. 🎯 The goal isn't bureaucracy - it's enabling consistent, high-quality outputs while meeting regulatory requirements. An effective QMS should feel like a helpful framework rather than a constraining box. 💡 Consider providing TL;DRs for each SOP. Make it clear when an SOP applies and when it doesn’t, not too dissimilar to indications for use. Cater for different types of information absorption: written, graphics, audio and, dare I say it, videos. What's your experience? How do you balance regulatory compliance with practical usability in your SOPs?
-
The most dangerous myth in MedTech? That quality is solely QA’s job. That belief costs companies millions. Think about it: • Remediation • Delayed launches • Damaged reputations The impact is real. Quality is not a department. It is a shared responsibility across product development, operations, leadership, and every function that touches the patient. But here’s the nuance I’ve learned after more than 25 years in biotech, pharmaceuticals, and medical devices: Shared responsibility does not erase individual roles. It clarifies them. Here is how quality ownership should actually be distributed across an organization: 1. What a QA Manager is truly responsible for: • Building and maintaining the QMS • Preparing for FDA, ISO, MDR, IVDR, and MDSAP audits • Leading CAPA management and long-term effectiveness • Overseeing documentation and change control • Ensuring compliance with all regulatory requirements 2. Where companies consistently go wrong: • Expecting QA to catch every defect or oversight • Asking QA to write technical procedures for other departments • Isolating risk management within QA instead of placing it with departmental or process experts • Pushing last-minute compliance cleanups onto QA • Treating quality as the “police” instead of a strategic partner 3. What requires real cross-functional partnership: • Partnering with engineering on strong design controls • Closing CAPAs by fixing systemic issues • Monitoring post-market performance • Improving supplier quality with shared ownership • Helping teams use documentation for safety and consistency QA managers cannot and should not function as quality superheroes. You need an entire organization of quality champions. Here are questions that every team should think about: • Who actually owns design controls? • Is QA guiding or just cleaning up? • Has anyone outside QA had recent compliance training? • Are we fixing root causes or patching symptoms? • Do non-QA teams see how their choices affect audits and patients? Shifting from “quality is their job” to “quality is our job” takes discipline, but the payoff is undeniable: • Higher team alignment • Safer, more reliable products • Stronger relationships with regulators • Faster readiness for certification and market entry The results speak for themselves when quality becomes part of the culture, not just the checklist. P.S. If you asked me how to explain to a CEO that QA is not a document-writing silo, I’d say this: Quality protects the patient, the brand, and the business. Its value comes from partnership, not paperwork. As someone who has spent decades in biotech and MedTech quality and compliance, I continue to help teams strengthen this mindset. I’m also opening new training sessions on ISO certification, internal auditing, and compliance fundamentals for cross-functional teams, ensuring compliance with ISO, FDA, and any other applicable requirements. Let me know if you’d like the details.
-
🔍 What is QMS? A QMS (Quality Management System) is a structured system that documents processes, procedures, and responsibilities for achieving quality policies and objectives. It is not just a set of documents, but a living framework that supports continuous improvement, risk management, and regulatory compliance. 📌 Key Components of QMS in QA: 1. Document Control – Ensures all SOPs, batch records, and policies are current, approved, and accessible. 2. Change Control – Systematic handling of changes to avoid unintended impact on product quality. 3. Deviation Management – Investigation and root cause analysis of any unexpected events. 4. CAPA (Corrective and Preventive Actions) – Identifying, implementing, and verifying actions to eliminate root causes. 5. Training Management – Ensuring all personnel are qualified and trained for their responsibilities. 6. Internal Audits – Periodic reviews to evaluate compliance and identify improvement opportunities. 7. Risk Management – Proactive identification and mitigation of risks throughout the lifecycle. 8. Supplier Quality Management – Evaluation and monitoring of vendors to maintain supply chain integrity. 9. Product Quality Review (PQR/APQR) – Annual analysis to confirm consistency and identify trends. 10. Customer Complaints Handling – A feedback loop to improve product and process quality. 🌟 Why QMS Matters: Drives regulatory compliance (cGMP, ICH Q10, ISO standards) Ensures patient safety and product efficacy Promotes a culture of quality across the organization Enables continuous improvement 📈 Implementing and maintaining a strong QMS is not just a regulatory requirement but a strategic advantage. It reflects an organization’s commitment to quality, safety, and excellence. . . . #QualityAssurance #QMS #PharmaceuticalIndustry #GMP #CAPA #QualityCulture #Compliance #PharmaProfessionals #ICHQ10 #ContinuousImprovement #QAProfessionals #LifeSciences
-
The Ex Vice Chairman of Tata Steel tells me, Total Quality Management cannot grow in a company where people are afraid of the truth. Above strategy and execution, this is the fundamental one has to start with and it is really uncomfortable space to be. You may install daily management boards. You may run problem solving workshops. You may talk about continuous improvement in conferences. None of this will create real quality if people feel unsafe to speak honestly about what is going wrong. When an operator fears punishment for a defect, he will hide it. When a manager fears blame for a delay, she will adjust the numbers. When a leader silently signals that only good news is welcome, the entire company learns to decorate reality. At that moment, data becomes a performance. Reports become theatre. The organisation loses the basic raw material of improvement, which is accurate information. In organisations where TQM truly flourishes, I have seen a very different climate. People are invited to surface problems early. When a mistake happens, leaders ask what in the process allowed it, not which person to blame. Senior management accepts that the system they designed can be improved, and takes responsibility for improving it. Meetings then change in character. They become places where reality is examined with respect, not with fear. Facts replace opinions. Patterns start to appear clearly. Improvement becomes a scientific activity rather than a cycle of accusation and defence. Before asking which TQM tool to implement, a serious leader must ask a harder question. Can my people tell me the truth without fear. If the honest answer is no, then the first step is not technical. It is cultural. Protect those who raise issues. Admit your own mistakes in front of your team. Reward the discovery of problems instead of only rewarding the absence of visible problems. Quality is not only about reducing variation in processes. It is also about reducing fear in people. Once fear goes down, the real picture appears. And only then can quality truly begin. A culture invite quality not forces it. PS: Watch my podcast with 𝗕 𝗠𝘂𝘁𝗵𝘂𝗿𝗮𝗺𝗮𝗻 - https://lnkd.in/gfS2JeH3 TQMI #TQM #Quality #TataSteel #QualityManagement
-
Things I Don’t Write Down — But Do Every Week as a Quality Manager Not everything that matters fits on a checklist... Some of it lives in people, pressure and patterns. In meetings that go off script. In the space between what was said — and what was meant. These aren’t ´best practices´. You won’t find these in the quality books. No one will ask about it in the audit. But they're the reason the system works at all. This is what real Quality looks like. (5, 21 and 22 are the must for every Leader, no matter the role) 1. Notice the hesitation in someone’s voice and follow up — because that’s where the real risk lives 2. Ask “What changed since the last time this worked?” — and sit through the uncomfortable answers. 3. Translate ISO language into something a human can act on. 4. Rebuild trust someone else broke in the name of “just getting it done”. 5. Teach teams to think through the system — not just follow it blindly. 6. Let people vent — to understand what the system’s really doing to them. 7. Translate silence into signal. 8. Challenge teams to define “done” — before they start. 9. Carry the weight of a decision that wasn’t mine, because someone has to. 10. Offer a process owner the benefit of the doubt and a better way forward. 11. Step in when two departments are speaking two different languages and think they’re on the same page. 12. Say “Let’s go look at it together”, instead of replying with a policy. 13. Watch how people actually use the process — not how they say they do. 14. Ask “Who’s missing from this conversation?” when the plan feels too easy. 15. Make someone feel seen — not corrected — after a mistake. 16. Create alignment between people who don’t even agree on the problem 17. Choose honesty over comfort — again. 18. Take the hit when Quality gets blamed — so the team doesn’t spiral into shame. 19. Keep going when nobody says thank you 20. Protect my team from reactive leadership behavior during a crisis. 21. Accept that some things won’t get fixed this week. But make sure they aren’t forgotten. 22. Keep the system human. Even when it would be easier not to. 23. Absorb chaos and return structure 24. Show up. Fully. Repeatedly. These are the things I do, but never say out loud. 𝗧𝗵𝗲𝘆’𝗿𝗲 𝘁𝗵𝗲 𝗿𝗲𝗮𝘀𝗼𝗻 𝗜 𝗴𝗲𝘁 𝗿𝗲𝘀𝘂𝗹𝘁𝘀. 𝗧𝗵𝗲𝘆’𝗿𝗲 𝗵𝗼𝘄 𝗜’𝘃𝗲 𝗯𝘂𝗶𝗹𝘁 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝘁𝗵𝗮𝘁 𝘄𝗼𝗿𝗸 — 𝗮𝗻𝗱 𝘁𝗲𝗮𝗺𝘀 𝘁𝗵𝗮𝘁 𝗰𝗮𝗿𝗲. If you’re still thinking Quality is about control, you’ve missed the whole point. Quality is presence. Quality is clarity. Quality is how I, You or anyone shows up. Now tell me... In which point do you recognize yourself? And what would you add as number 25? #QualityMindset #BeQuality #ThinkQuality
-
An incomplete QMS is the best QMS for a medical startup. How can that be? Well, after working with many, many medical startups, I’ve learned that there’s a right way and a wrong way (actually multiple wrong ways) to set up a new quality management system (QMS) for a medical startup. Here’s one wrong way. Years ago I was working with a Silicon Valley startup that had purchased an entire QMS from a quality consulting firm. Simple solution, right? Unfortunately, this QMS was so large and complex (>80 SOPs and 100’s of forms and templates) that they also had to bring in multiple consultants from the firm just to operate the QMS. None of the startup’s employees understood what all the new procedures meant. This caused confusion and delays and the frustrated employees ended up largely ignoring the QMS. Instead of quickly achieving compliance, the company ended up with a big mess that was difficult and expensive to clean up. For a fast-moving, early-stage medical startup, the challenge is really about how to achieve compliance without bringing everything to a crawl. Here are some tips to address that challenge: 🔹 Instead of trying to implement a full QMS, take a staged approach to implementation. Focus initially on design controls, risk management, doc control, and supplier management. Then develop and release additional quality system procedures as they’re needed by the phase of product development and as the company grows. For example, the startup doesn’t need a Complaint Handling SOP while the product is still in development; it would only be a distraction. That’s the advantage of an “incomplete QMS.” 🔹 Make sure all the employees, especially those who are new to the medical device industry, understand the full framework and concepts behind the new quality system you’re building (the “why” behind all the new rules). Hint: it’s not just about compliance. 🔹 Focus on processes first, with minimal documentation. Use slimmed down draft SOPs that are easily modified to optimize processes. Then, as the organization becomes comfortable with following the processes, release full SOPs with increased controls and documentation (forms, templates, etc.). This encourages everyone to view the quality system as something dynamic that can be refined over time to best suit the needs of the company and not simply a static set of rules. Purchasing eQMS software is helpful at the right stage of the startup but you still want to focus on processes first. Good software tools will reinforce good processes but can’t compensate for bad processes (or no processes). Taking the time to gradually create a good QMS–one that emphasizes good processes over elaborate documentation–is one of the secrets to building a successful medical startup. It’s also something that you have complete control over at your startup (unlike tricky technical challenges, fundraising, marketing, etc.). Do you have any tips for starting a QMS at a medical startup?
-
ISO 9001 isn’t built on clauses. It’s built on principles. 🎯 The Quality Management Principles (QMPs) may not be requirements themselves, but they’re the thinking model behind the entire standard. Miss the principles → you end up doing paperwork. Understand them → you build a system that actually works. Here’s the backbone 👇 🔹 Customer Focus Quality starts and ends with the customer experience - not internal convenience. 🔹 Leadership Direction, alignment, and culture don’t happen by accident. Leaders set the tone for quality. 🔹 Engagement of People Systems don’t deliver results. People do. Empowered teams = reliable performance. 🔹 Process Approach Work is connected. When processes flow together, outcomes become predictable. 🔹 Improvement Standing still is falling behind. Strong systems are designed to evolve. 🔹 Evidence-Based Decisions Opinions are loud. Data is honest. Trends reveal what gut feelings can’t. 🔹 Relationship Management Suppliers and partners aren’t outsiders - they’re extensions of your system. 📌 These principles show up throughout the standard - especially in leadership, performance evaluation, and continual improvement requirements. And looking ahead, modern quality systems are leaning even more into: ✨ Building a strong quality culture 💡 Deeper leadership accountability 💻 Smarter use of digital tools and knowledge 📊 Better decisions through real data Bottom line: ISO 9001 isn’t a checklist to satisfy auditors. It’s a framework built on principles that make organizations more consistent, more resilient, and more trusted. 🚀 When you lead with the principles, compliance becomes a byproduct - not the goal.
-
“What QMS structure should we build now… so we’re not rebuilding it in two years?” That’s the question a founder asked me last month, right after landing their Series A and preparing to expand into two new markets. I’ve heard variations of it from at least six companies in the past quarter alone, which tells me this isn’t just a tactical choice anymore, it’s strategic. As companies grow in new markets, new manufacturing partners, and new product variations, the question of centralized vs. decentralized QMS shows up sooner or later. And there’s no one-size-fits-all answer. Here’s what I've seen work (and backfire) across the board: 🛡️ Centralized QMS ✔ Great for small-to-mid-size teams or companies expanding under a single quality umbrella. ✔ Consistency, audit readiness, and precise document control. ❌ Can be slow, inflexible, and frustrating for local teams who need speed and nuance. 🌍 Decentralized QMS ✔ Gives full autonomy to each site, which works for large multinationals or those with distinct product families. ❌ The flip side is duplication, inconsistent compliance, and fragmented oversight. 🔗 Hybrid QMS (the model I increasingly recommend) ✔ Combines corporate-level SOPs with region-specific adaptations. ✔ Allows for shared ownership, but ensures traceability and alignment during audits. ✔ Particularly helpful when simultaneously scaling across the U.S., EU, and APAC. I often help clients transition from decentralized to hybrid as their operations mature, or from centralized to hybrid as they expand globally and need more localized agility. In my experience, the question isn't just “Which model should we use?” It’s: “What level of control, flexibility, and clarity do we need today and 18 months from now?” #QualityManagementSystem #MedTech #RegulatoryCompliance #ScalableSystems #GlobalExpansion #Elexes #MedicalDevices
-
A fundamental concept in quality is that everything is a process. This includes suppliers, inputs, processes, outputs, and customers. While this might seem like common knowledge, many organizations still struggle with implementing these concepts effectively. In my experience of over thirty years in the field of quality, I have observed that the failure to clearly define and document processes can lead to significant challenges. One of the primary issues is the lack of clear ownership. Business process owners often exist in name only, without a well-defined role. This lack of definition can result in processes that are either undocumented or heavily reliant on individual expertise. This reliance on specific individuals can be risky, as it leads to the degradation of processes over time, especially when organizational knowledge is lost due to employee attrition. Another critical issue is the failure to measure the outputs of processes. When outputs are not tracked, organizations often experience waste as a byproduct. Waste can take many forms, including time, resources, and money, all of which can significantly impact the efficiency and effectiveness of an organization. To address these challenges, it's essential to ask the right questions, such as: Who owns the process and its output? What is the standard for the process? How do we know the process is working and effective? These questions help ensure that there is accountability, clarity, and a standard against which performance can be measured. In the pursuit of becoming lean, driving improvement, or maintaining the fundamentals of a management system, it is crucial not to overlook the basics. To achieve excellence, it is vital to make expectations clear, ensure performance is visible, and be intolerant of waste. Problems should be resolved at their root, ensuring that processes are effective and efficient. By focusing on these fundamentals, organizations can significantly enhance their management systems and drive sustainable improvements.
Explore categories
- Hospitality & Tourism
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Healthcare
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Career
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development