Engineering Quality explores redefining quality leadership through culture, collaboration, and systems thinking, emphasizing mentorship, diversity, and inclusive practices in software testing. The episode delves into quality coaching frameworks, challenges of influencing teams without formal authority, and the importance of community, communication, and shared responsibility in fostering sustainable quality improvements.

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/15-Quality-coaching-with-Anne-Marie-Charrett--Fiona-Charles-e3ftutb
• Published: 2026-03-04T15:42:58Z
• Duration: 00:40:28
• Author: Engineering Quality

Overview

The podcast examines the transformation of quality leadership in software development, moving from rigid, process-driven models to approaches centered on fostering collaboration, inclusive culture, and systems thinking. It emphasizes the role of mentorship, community involvement, and diverse career pathways in shaping effective testing practices, while highlighting how quality leadership extends beyond traditional testing roles to encompass shared responsibility across teams. The discussion explores the impact of quality coaches, who promote collective ownership of quality through education, facilitation, and cross-functional teamwork, contrasting this with more siloed, technical testing roles.

Key challenges addressed include leading quality initiatives without formal authority, such as overcoming resistance to change, aligning stakeholders, and implementing incremental behavioral shifts through workshops. The conversation also underscores the importance of tailoring communication strategies to different audiences, ensuring tangible outcomes for visibility, and creating environments where quality is a collaborative effort rather than a top-down directive. These insights reflect a broader shift toward embedding quality as an integral, team-driven aspect of software development.

What If

• What if you implemented a “quality coaching” framework to reframe your team’s focus from rigid checklists to collaborative problem-solving?

  • Concrete move: Start weekly “quality conversations” with your team, using prompts like “How might we improve this process?” or “Whats the users pain point here?” to shift from testing as a task to systems thinking.
  • Why now: The text emphasizes that quality leadership is about culture and collaboration, not just process. As a solo operator, this approach builds trust and ownership without relying on formal authority.
  • Expected upside: Teams will adopt a shared mindset for quality, reduce rework, and increase your influence as a thought leader in your product’s development lifecycle.

• What if you leveraged your network to create a “community of practice” for quality improvements, even as a solo developer?

  • Concrete move: Organize biweekly virtual “bug bashes” with peers or open-source collaborators, inviting input on edge cases and usability issues in your product. Document learnings in a shared space (e.g., Notion or GitHub).
  • Why now: The text highlights the importance of networks and shared knowledge in driving change. Small, regular contributions to a community can amplify your works visibility and impact.
  • Expected upside: Youll gain diverse perspectives, accelerate improvements in your product, and build relationships that could lead to co-mentoring or consulting opportunities.

• What if you prioritized “ownership of quality conversations” by integrating feedback loops directly into your development workflow?

  • Concrete move: Embed a “quality reflection” step in your personal sprint reviews, asking: “What did we learn about user needs this week?” and “How might we test this differently next time?” Share these reflections with your team.
  • Why now: The text stresses that quality is a shared responsibility, and solo operators can model this by making quality ownership a visible, repeatable habit.
  • Expected upside: This practice builds muscle memory for continuous improvement, reduces blind spots in your work, and frames your contributions as strategic (not just reactive), boosting your visibility to leadership.

Takeaway

• Implement quality coaching principles by fostering collaboration within your team (or yourself) through activities like bug bashes, shared testing responsibilities, and regular cross-functional workshops to ensure quality is a collective priority.
• Document contributions tangibly using tools like Jira tickets, code reviews, or shared documentation to demonstrate your works impact and align with organizational goals, especially in roles without direct deliverables.
• Engage with the software testing community via forums, online groups, or mentorship programs to build alliances, share knowledge, and stay updated on evolving practices, even as a solo operator.
• Prioritize practical testing skills and systems thinking over rigid checklists by integrating automation, exploratory testing, and user-centric validation into your workflows to ensure products meet real-world needs.
• Set clear, achievable quality goals with measurable outcomes (e.g., reduced bugs, improved user feedback) and communicate them effectively to stakeholders to secure buy-in and align your efforts with broader organizational priorities.