Sign up to save your podcasts
Or
Share It depends - Ask MoTaverse Anything - Ep 128
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
It depends - Ask MoTaverse Anything - Ep 128
In episode 128 of This Week in Quality (Friday 20 March 2026), Ben Dowen and Simon Tomes catch up on conference learnings, community experiments, and a fresh way to share knowledge across the MoTaverse. Ben opens with reflections from Testing Peers Conference, including a practical workshop takeaway on Playwright agents, and Simon nudges him toward turning those learnings into a MoTaverse Moment.
The conversation then pivots to the new Ask MoTaverse Anything initiative, an AMA format powered by Moments. The hosts spotlight Cassandra Lung’s AMA prompt, “Quality beyond correctness,” and use it as a springboard to discuss what correctness even means, why “it depends” is often the most honest answer, and how questions themselves are a valuable form of contribution. They highlight the benefits of separating each answer into its own Moment, creating reusable “learning blocks” that build credibility, show up on profiles, and are easier to find later.
A key thread emerges around communicating impact. They call out Emily O’Connor’s question on persuading engineers and product owners to prioritize work beyond acceptance criteria, and Cassandra’s answer that focuses on real-world consequences, empathy, and user impact stories, including using impact framing both to advocate for fixes and to justify not doing low-value work.
Community voices join in too. Preeti Gupta shares a real-life example of quality beyond correctness, showing how the same bug can be “correctly” described in technical terms yet still fail to land with non-technical stakeholders, and why clearer impact-focused communication changes prioritization and understanding. Gary Hawkes follows with a burst of “MoTawhelmed” energy, describing how recent conversations and conference notes have sparked a backlog of baby-step improvements, plus his motivation for starting an AMA on leadership and what he’s learned by finding his own leadership style over time.
The episode wraps with a quick plug for Software Testing Live returning next week, and a final nudge to contribute to the Observatory, MoT’s bookmarking feature, now expanded with broader tech categories to help the MoTaverse evolve into a wider quality-led tech community.
View all episodes
By Ministry of TestingIn episode 128 of This Week in Quality (Friday 20 March 2026), Ben Dowen and Simon Tomes catch up on conference learnings, community experiments, and a fresh way to share knowledge across the MoTaverse. Ben opens with reflections from Testing Peers Conference, including a practical workshop takeaway on Playwright agents, and Simon nudges him toward turning those learnings into a MoTaverse Moment.
The conversation then pivots to the new Ask MoTaverse Anything initiative, an AMA format powered by Moments. The hosts spotlight Cassandra Lung’s AMA prompt, “Quality beyond correctness,” and use it as a springboard to discuss what correctness even means, why “it depends” is often the most honest answer, and how questions themselves are a valuable form of contribution. They highlight the benefits of separating each answer into its own Moment, creating reusable “learning blocks” that build credibility, show up on profiles, and are easier to find later.
A key thread emerges around communicating impact. They call out Emily O’Connor’s question on persuading engineers and product owners to prioritize work beyond acceptance criteria, and Cassandra’s answer that focuses on real-world consequences, empathy, and user impact stories, including using impact framing both to advocate for fixes and to justify not doing low-value work.
Community voices join in too. Preeti Gupta shares a real-life example of quality beyond correctness, showing how the same bug can be “correctly” described in technical terms yet still fail to land with non-technical stakeholders, and why clearer impact-focused communication changes prioritization and understanding. Gary Hawkes follows with a burst of “MoTawhelmed” energy, describing how recent conversations and conference notes have sparked a backlog of baby-step improvements, plus his motivation for starting an AMA on leadership and what he’s learned by finding his own leadership style over time.
The episode wraps with a quick plug for Software Testing Live returning next week, and a final nudge to contribute to the Observatory, MoT’s bookmarking feature, now expanded with broader tech categories to help the MoTaverse evolve into a wider quality-led tech community.