Joining new teams in quality assurance requires balancing respect for existing workflows with opportunities for improvement, especially in hybrid methodologies. Effective change demands collaboration, adaptability, and understanding team dynamics, while overcoming imposter syndrome and leveraging questioning, neurodiversity awareness, and shared knowledge.

MOT This Week in Testing

MOT - This week in Testing - Varied hosts, group chat, often with community questions and involvement. Show notes have a full transcript.

• https://www.ministryoftesting.com/podcasts
• https://www.ministryoftesting.com

Episode Details

• Show Notes: https://www.ministryoftesting.com/podcasts/this-week-in-testing?wchannelid=czgwdadw2c&wmediaid=2z4anbaxv1
• Published: 2026-08-14T14:14:38Z
• Duration: 59:10
• Author: Unknown

Overview

The podcast discusses experiences and challenges related to joining new teams and adapting to established workflows, particularly within quality assurance roles. A key theme is the importance of respecting existing processes while identifying opportunities for improvement, especially when integrating into teams with varying levels of maturity in their methodologies. The discussion highlights how teams often use hybrid models combining Agile, Scrum, Kanban, or other frameworks, and emphasizes that successful change requires understanding team context rather than imposing one-size-fits-all solutions. Concepts like shift-left testing and co-ownership of quality are explored, with stress on collaboration, adaptability, and listening to team dynamics before driving change.

Another major focus is on the role of questioning, learning, and overcoming imposter syndrome in testing roles. The hosts reflect on how asking questions - often discouraged early in their careers - is essential to effective quality assurance. Over time, their inquiries have evolved from basic to more technical and analytical, supported by community validation and experience. The conversation also touches on how neurodiversity, such as ADHD, can influence communication styles and professional confidence, and how finding terminology for practices helps legitimize them. The value of shared knowledge through glossaries, community contributions, and open dialogue is emphasized as a way to align understanding, broaden perspectives, and support continuous learning across teams.

What If

• What if you documented one misunderstood testing term used in your project this week?

  • Move: Pick a term (e.g., “regression testing” or “flow testing”) your team uses inconsistently, define it in your own words, and share it in a public note (e.g., GitHub README, internal wiki, or a blog/Moments post).
  • Why Now?: Ambiguous terminology slows down collaboration and creates blind spots - clarifying now prevents misalignment in testing efforts, especially as AI tools amplify reliance on consistent prompts and definitions.
  • Expected Upside: Reduces miscommunication in tickets and PRs, establishes you as a clarity leader, and creates reusable documentation that onboards future team members faster.

• What if you posted a 5-minute “QA Moment” reflecting on a past bug you missed?

  • Move: Write a concise public reflection (on Moments or LinkedIn) about a real bug you didn’t catch, what assumptions you made, and how you’d approach it differently - with a focus on human-AI collaboration (e.g., “Would an AI have missed this too?”).
  • Why Now?: AI is reshaping QA workflows - sharing human error stories builds trust, surfaces blind spots, and positions you as thoughtful and adaptive in the shift-left landscape.
  • Expected Upside: Strengthens your personal brand as a reflective practitioner, invites valuable feedback from peers, and improves your own pattern recognition for future testing.

• What if you tested your product like a new hire for one afternoon?

  • Move: Spend 90 minutes interacting with your product without insider knowledge - no backend access, no context. Take notes on every assumption you have to make, then turn it into a public “first-user journey” report with 3 improvement suggestions.
  • Why Now?: Fresh perspectives reveal gaps in onboarding, UX, and quality co-ownership; doing this proactively mirrors the value new team members bring before process inertia sets in.
  • Expected Upside: Uncovers real usability issues stakeholders overlook, demonstrates user empathy, and generates actionable insights you can pitch as quick wins - boosting your influence as a solo operator.

Takeaway

• Review and contribute to shared glossaries or terminology databases to align team understanding and reduce ambiguity in communication.
• Record and publish short-form reflections on industry talks or tools using accessible platforms like “Moments” to build visibility and engage with communities.
• Proactively ask clarifying questions when joining a new project or team to map out processes, norms, and expectations without assuming knowledge.
• Share public feedback or appreciation for tools and services used, strengthening relationships with providers and influencing future development roadmaps.
• Watch recorded technical talks or workshops regularly and write quick, timed reflections to develop critical thinking and generate actionable insights.