Janet Gregory outlines strategies for embedding quality through observation, retrospectives, and her QPAM framework, stressing that cultureparticularly communication and collaborationtrumps technical processes. She advocates for shared accountability, decentralized leadership, and addressing systemic issues like unclear requirements to foster inclusive, sustainable quality practices.

The Engineering Quality Podcast

The Engineering Quality Podcast - hosted by Alessandra Moreira, Royalee Martin, and Veronika Pliusnina. Testing focused panel discussions.

• https://www.engineeringqualitypodcast.com/
• https://music.youtube.com/playlist?list=PLqUuvcBX10HyISlL5fhvGJosizW8PD9rV

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/engineering-quality/episodes/17-Quality-Isnt-A-Testing-Problem--Its-a-Culture-Problem-e3h1a9e
• Published: 2026-04-08T11:23:00Z
• Duration: 00:32:45
• Author: Engineering Quality

Overview

The podcast features Janet Gregory, an agile testing expert, discussing strategies for fostering a quality-focused culture in software development. She highlights the importance of observation, process retrospectives, and pattern recognition as tools to assess organizational practices, emphasizing that cultureparticularly communication and collaborationoverwhelms technical processes. Her QPAM (Quality Practice Assessment Model) offers a structured framework for evaluating quality, while she critiques misconceptions like the notion that testers hinder progress or that quick fixes can resolve systemic issues. Janet stresses the need to address root causes such as unclear requirements and poor communication, advocating for inclusive practices that align teams around shared goals.

Challenges in developer-tester dynamics, including adversarial mindsets and siloed work, are addressed as barriers to effective collaboration. Janet underscores the value of proactive communication, early cross-functional engagement, and shared accountability for quality. She also explores psychological and social factors, noting that human collaboration is key to reducing assumptions and fostering trust. Key takeaways include the necessity of leadership in defining quality, ensuring all roles align on expectations, and promoting diverse perspectives to refine quality standards. Strategies for improvement involve decentralized leadership, empowering testers to own quality, and prioritizing continuous feedback over rigid hierarchies.

Janet emphasizes that testing leadership must focus on cultivating collective responsibility for quality, rather than relying on dedicated roles. She advocates for leaders to model desired behaviors, listen actively, and foster environments where all team membersregardless of rolecontribute to quality outcomes. The discussion also touches on the importance of defining quality collaboratively, mitigating career stagnation for testers through advocacy, and ensuring feedback mechanisms support growth. Ultimately, cultural and structural shifts toward inclusivity, transparency, and shared purpose are framed as foundational to sustainable quality improvements.

What If

• What if you implemented a QPAM self-assessment for your solo workflow?
  Concrete move: Use Janet Gregory’s QPAM model to evaluate your personal quality practices (e.g., how you document tests, communicate with stakeholders, or handle code reviews).
  Why_now: Cultural alignment and self-awareness are foundational for quality, even in solo operations. The pandemic-era QPAM framework is designed to adapt to individual contexts.
  Expected_upside: Surface hidden inefficiencies or gaps in your process, enabling targeted improvements in reliability and reducing rework.

• What if you created a “developer-tester” collaboration ritual for your solo projects?
  Concrete move: Adopt Janet’s playful incentive (e.g., a small reward) to force yourself to review test cases before writing code, mimicking cross-team communication.
  Why_now: Silos and ad hoc testing are pervasive, even for solo ops. Proactive collaboration reduces friction caused by misaligned goals (e.g., bugs slipping through).
  Expected_upside: Faster bug detection, better alignment with your own “tester” mindset, and more confidence in code quality.

• What if you hosted a stakeholder feedback loop for defining “quality” in your solo projects?
  Concrete move: Run a short interview or survey with customers/users to clarify what “quality” means for them, then align your testing/development priorities accordingly.
  Why_now: Janet highlights that shared quality definitions are critical, and solo developers often lack this. Misaligned expectations lead to rework or customer dissatisfaction.
  Expected_upside: Directly reduce post-launch issues by building a product that reflects user priorities, not just your assumptions.

Takeaway

• Integrate collaborative communication practices by scheduling regular check-ins with developers (if applicable) or stakeholders to discuss testing early in the development process, such as brainstorming test scenarios before coding begins.
• Define a shared quality standard for your project through workshops or documentation, even if solo, by engaging with end-users, customers, or clients to align on expectations and avoid misaligned goals.
• Adopt pattern recognition and retrospectives on your own workflows by documenting recurring issues in testing (e.g., unclear requirements) and iterating on strategies to address them, such as refining test cases iteratively.
• Break down silos by cross-training in testing principles, even as a solo developer, to ensure you understand both development and testing roles, reducing the need for external collaboration and improving self-sufficiency.
• Implement feedback loops by actively seeking customer or peer feedback on your work (e.g., through surveys or user testing) and using it to refine your processes, avoiding the “magic wand” mindset of quick fixes for recurring problems.