Texas Quality Assurance – Quality Management Simplified

In the latest mini-episode of Caleb's Corner, we dove into a crucial topic every quality professional faces: When do you keep tweaking your system, and when is it time for a total overhaul? This fundamental concept, often described as Iterative Design vs. Radical Redesign, isn’t just for software developers; it's highly applicable across all areas of Quality Management Systems (QMS). The Heart of Iterative Design As the Quality Software Manager at Texas Quality Assurance (TQA), much of my work revolves around our TQA Cloud platform, which helps clients manage everything from calibration and maintenance to employee training and document control. In developing the next version of our app—which will offer a smoother, more integrated experience—I face constant decisions on whether to improve existing features incrementally or scrap and rebuild entire modules. Iterative Design is the practice of making small, controlled adjustments to improve a system continuously. This approach: * Allows for measurable, incremental improvements * Provides lower risk since changes are smaller and easier to reverse * Helps maintain system stability while adapting to new requirements * Encourages continuous improvement, a core principle of ISO 9001 and other quality standards In many cases, iterative design is the safest and most effective way to evolve a QMS software platform or any quality management process. The Necessity of Radical Redesign However, there are times when no amount of tweaking will get you where you need to be. This is where Radical Redesign becomes necessary. Sometimes, your approach is fundamentally flawed for the goals you're trying to achieve. Signs it's time for a full rebuild include: * Legacy systems that cannot integrate with modern tools * Process flows that no longer reflect your organization's actual operations * Compliance gaps that cannot be closed with minor adjustments * User frustration due to convoluted or outdated interfaces In these cases, starting fresh allows you to rethink your processes, design for today's needs, and set a stronger foundation for future growth. Balancing the Two in Quality Management In the world of quality management consulting, we frequently help clients evaluate their systems through this very lens. Whether we're advising on ISO 9001 compliance, API Q1 certification, or customizing TQA Cloud for a new client, the same question applies: Is this a tweak or a rebuild? By regularly assessing your QMS and leveraging both iterative design and radical redesign when appropriate, you can ensure your systems are not only compliant but also practical, scalable, and truly supportive of your business objectives. Let Texas Quality Assurance Help You Decide Struggling to determine whether your quality system needs a few small adjustments or a complete redesign?

Understanding the Climate Change Amendment in ISO 9001 In Episode 216 of #QualityMatters, we explore the climate change amendment, a concise yet impactful update to ISO 9001 that compels organizations to identify and address climate-related risks within their quality management systems. This climate change amendment—just two lines of text—requires companies to determine whether climate change is an issue and to integrate relevant controls into their existing processes. Why ISO 9001 Amendment Matters Now ISO 9001 has long embraced risk-based thinking, but until recently, “environmental” considerations focused on product conformity and resource usage. The new ISO 9001 amendment explicitly brings climate risk into scope, aligning quality management with global sustainability goals. By articulating climate change as an “interested party” requirement, the amendment extends the standard’s reach into environmental stewardship without creating a separate ISO document. Exact Wording of the Two-Line Update The amendment reads: * The organization shall determine whether climate change is an issue that can affect its quality management system. * Where such issues are identified, the organization shall plan and implement actions to address these climate-related risks and opportunities. Though minimal, this language integrates seamlessly into Clauses 4 and 6 of ISO 9001:2015, reinforcing the risk-based framework and ensuring that climate considerations become an embedded part of continual improvement. Practical Interpretation: Determining Climate-Related Risks “Determine whether climate change is an issue” may sound broad, but organizations can ground this in real-world examples. For instance: * Manufacturers assess supply-chain vulnerabilities due to extreme weather events. * Service providers evaluate energy-use efficiency and carbon footprint in daily operations. * Agricultural operations might switch from diesel-based to biofuel-based equipment or adopt no-till practices to reduce greenhouse gas emissions. By mapping these risks in a dedicated section of the risk register, companies demonstrate compliance with the climate change amendment and strengthen overall process resilience. IAF Guidance: What Auditors Need to Know Shortly after publication, the International Accreditation Forum (IAF guidance) issued a complementary document outlining how auditors should verify compliance: * Evidence gathering: Auditors must review documented risk assessments and climate-related action plans. * Scope expansion: Interviews with process owners should probe climate mitigation measures alongside traditional quality controls. * Audit time allocation: Expect an additional 30–60 minutes to cover climate topics thoroughly. This IAF guidance ensures consistent treatment across c...

Quality Matters Episode 215: What’s the Real Cost of Poor Quality? In this episode of the #QualityMatters podcast, Kyle and Caleb dive deep into a topic that touches every business, from manufacturing to customer service—the true cost of poor quality. But this isn't your typical lecture on scrap and rework. The guys bring stories, perspectives, and real-world relevance to the table—from customer loyalty and personal tech decisions, to school choice and workforce skills, to the vital role of culture in shaping quality outcomes. When Customer Experience Drives a Brand Switch Caleb kicks off the episode with a personal story that many of us can relate to: a frustrating experience with a major cell phone manufacturer that ultimately led him to switch to Apple. This wasn’t just about technical specs or flashy features—it was about how quality (or the lack of it) is perceived by customers. When something breaks or a system doesn’t work as promised, customers don’t just lose patience—they lose trust. "It wasn’t the cost of the broken phone. It was the cost of lost time and support that pushed me to change brands." – Caleb This example underscores a key theme: poor quality isn't always measured in dollars—it’s often paid for in loyalty, reputation, and long-term business. Kyle's Thoughts on Education, Trades & the Future of Quality Shifting gears, Kyle reflects on education choices for his sons—particularly the value of vocational training and skilled trades. In a world that’s heavily focused on four-year degrees, Kyle advocates for alternative education paths that equip young people with tangible skills—and the ability to contribute meaningfully in quality-centric roles from day one. "We’ve got to stop thinking a good education only happens in a classroom. It happens in a shop, at a lathe, with a wrench in your hand." This discussion challenges us to rethink how we prepare the next generation for quality-focused careers, and how education directly impacts organizational quality from the ground up. Scrap, Rework & the Obvious Costs Of course, no episode about poor quality would be complete without touching on the more visible costs—scrap, rework, waste, and lost production time. The hosts break down how these issues creep into operations and why they are symptoms, not the root cause. Caleb reminds us that you can’t fix culture with corrective actions alone, and that lasting change must address both processes and people. Culture: The Real Root of Quality What ties all these topics together? Culture. The heart of the episode rests in the idea that quality begins with people, and the culture that leaders build around them. A culture that values continuous improvement, feedback, and pride in workmanship is the only true long-term solution to preventing quality failures—whether they happen on the shop floor or in customer support.

In this episode of #QualityMatters, Kyle and Caleb switch things up with a more hands-on approach to problem-solving. Instead of tackling world-scale issues, they focus on real-world examples of how people are navigating challenges in quality management. It’s all about learning from others, taking inspiration, and finding practical solutions that can be applied today. #QualityManagement, #ProblemSolving, #QMS, #QualitySolutions, #QualityMatters, #RealWorldQuality, #QualityPodcast, #QualityImprovement, #ProcessManagement, #LeadershipInQuality Kyle and Caleb explore how others have successfully addressed obstacles in quality management, offering insights into effective processes, tools, and strategies that make a difference on the ground level. Their conversational approach makes complex problem-solving feel accessible and relevant, with actionable tips you can apply immediately. If you're looking for fresh perspectives on quality management or need inspiration to tackle your own challenges, this episode is packed with practical advice and a fun, relatable discussion that makes the process feel less daunting.

The Autopen controversy isn’t just a political debate—it raises real concerns about document control, compliance, and security that affect businesses just as much as governments. In this episode, Kyle Chambers and Caleb Adcock examined the risks of automated signatures, using the presidential pardon debate as a case study to highlight issues in business document approval processes. Here’s what we discussed and the key lessons businesses should take away from it. 1. A Signature is More Than Just a Mark—It’s Accountability One of the biggest concerns with Autopen is that it allows a document to be signed without the direct action of the signatory. That raises a simple but important question: Who is truly responsible for a document signed this way? Key Lesson: If a signature is applied automatically, there must be clear accountability for who approved it and under what circumstances. Otherwise, there’s room for disputes, denials, and legal challenges. Best Practice: Organizations should require that signatures, even automated ones, are tied to direct authorization—whether that’s physical verification, two-step approval, or documented oversight. 2. If You Automate Approvals, You Introduce Risk One of the major discussion points in the episode was how the use of Autopen in presidential pardons raised concerns about document authenticity. If a signature can be applied without the person’s involvement, how do we know it was actually approved by them? This problem isn’t just political—it happens in business whenever document approvals are automated without sufficient controls. Key Lesson: Automation must not replace oversight. If approval processes are automated, businesses need safeguards to ensure documents aren’t signed without review or authorization. Best Practice: If using automated or digital signatures, businesses should require: * Approval logs that track who authorized the signature. * Access restrictions to prevent unauthorized signing. * Regular audits to verify compliance with document control policies. 3. Legal Challenges Can Arise If Signatures Aren’t Clearly Verified The podcast examined how the Autopen issue led to legal challenges over presidential pardons, with some arguing that they weren’t legally valid because they weren’t signed manually. The same issue applies in business: if a company can’t prove a document was signed with proper authorization, that document could be challenged in legal or regulatory settings. Key Lesson: If signatures lack clear authentication and approval tracking, they could be legally contested, leading to compliance failures, contract disputes, or regulatory penalties. Best Practice: Businesses should ensure that document approval policies align with legal standards—especially in regulated industries.