The podcast discusses the importance of addressing the root issues in communication and collaboration before focusing on technical improvements in the QA and testing industry. Megan Ael, QA lead at Crew Software, shares her insights on the challenges of automation-first approaches and the need to consider broader team practices and communication.

Quality Talks

Quality Talks is Stu Day and Chris Henderson and different guest each episode. Released as audio and video. The official Show notes have summary, key points and time stamped chapters.

• https://qualitytalks.co.uk/podcast
• https://www.youtube.com/@QualityTalksPodcast
• https://anchor.fm/s/f6e76df4/podcast/rss

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/qualitytalkspodcast/episodes/Conversations-Before-Code-Avoiding-the-Automation-First-Trap-with-Megan-Ozanne-e3df2no
• Published: 2026-01-14T06:00:00Z
• Duration: 00:41:06
• Author: Quality Talks Podcast

Overview

The episode addresses the “automation first trap,” a common pitfall where teams focus prematurely on implementing automation without first resolving underlying systemic challenges. It explains how issues such as unclear acceptance criteria, undefined workflows, and unreliable locators can severely limit the effectiveness of automation when they are not addressed upfront. Without proper alignment between QA, development, and product teams, automation efforts may fail to deliver the intended benefits, leading to wasted time and resources.

To avoid this trap, the discussion emphasizes the need for early, structured communication among team members to identify testability concerns and improve collaboration. Practical strategies include creating a Slack channel for sharing tickets in advance, documenting discussions within those tickets, and utilizing asynchronous communication to ensure inclusivity. These methods help foster an environment where all team members can contribute effectively, leading to better planning and more successful automation outcomes.

The episode also acknowledges the challenge of involving external stakeholders and leadership in the conversation, suggesting that empathy and respect for different perspectives are essential. It recommends using frameworks like the “Three Amigos” approach to bring together representatives from QA, development, and product management during planning sessions. Overall, the core message is that successful automation depends not just on technical solutions, but on meaningful collaboration and communication across the team.

What If

• What if you introduced a “Three Amigos”-style meeting for every user story before coding begins?
  Move: Schedule pre-sprint planning meetings with developers, product owners, and QA to define acceptance criteria and testability upfront.
  Why now: The text emphasizes that poor communication and delayed conversations lead to unclear requirements and testability issues, which hinder automation efficiency.
  Expected upside: Reduced story churn, faster test development, and alignment on priorities, enabling automation to be built in parallel with development.

• What if you created a dedicated Slack channel for sharing sprint tickets 2448 hours before planning meetings?
  Move: Set up a non-closed channel where tickets for the next sprint are shared in advance, allowing team members to review and contribute asynchronously.
  Why now: The text highlights that late conversations waste time and limit participation, especially for quieter team members.
  Expected upside: Increased contribution from all team members, more informed discussions during meetings, and faster resolution of testability issues before coding begins.

• What if you mandated that all acceptance criteria and test evidence be documented in tickets before code starts?
  Move: Require product owners to define clear acceptance criteria and QA to add test evidence directly to tickets, using the “capture conversation outputs” approach.
  Why now: The text stresses that vague requirements and lack of traceability lead to rework, poor automation, and longer cycles.
  Expected upside: Reduced ambiguity in testing, fewer bugs downstream, and a centralized repository for traceability, accelerating automation ROI.

Takeaway

• Implement structured communication channels for pre-sprint planning
  Use a shared Slack channel or similar tool to share tickets for the next sprint in advance, allowing you to review requirements, provide feedback, and prepare for discussions. This ensures collaborative input and reduces last-minute misunderstandings.

• Document key conversations and test scenarios directly in project management tickets
  Add test evidence, acceptance criteria, and discussion points to tickets to centralize information. This improves traceability, reduces rework, and keeps all stakeholders aligned on requirements and expectations.

• Adopt the “Three Amigos” approach by engaging with product owners and developers early
  Schedule regular check-ins with product and development teams before sprint planning to align on requirements, workflows, and testability. This proactive dialogue helps identify pain points early and ensures test automation efforts are aligned with goals.

• Assess your automation maturity using a simple framework
  Create a self-assessment model (like a “quality radar”) to evaluate your current practices in areas like communication, process, and support. Use this to identify gaps and prioritize improvements in alignment with broader team needs.

• Track and share stories of inefficiencies to build buy-in for process changes
  Use metrics like story churn, bug counts, or test suite delays to quantify negative consequences of poor practices. Pair this with real-world examples (e.g., repeated rework) to convince stakeholders of the need for better communication and collaboration.