S04 EP05 - James Lyndsay - Enjoying Testing Through Play
Categories: Podcasts , Quality Blether
Playful, exploratory testing fosters creativity and collaboration, while storytelling and team dynamics drive project success. Adaptability, mentorship, and critical judgment are key in evolving testing practices, especially with AI advancements.
Quality Blether
Quality Blether is the official podcast of the Scottish Testing Group. Episodes are guest interview based.
Episode Details
- Show Notes: https://scottishtesting.org/
- Published: 2026-10-16T19:30:26Z
- Duration: 51:20
- Author: Unknown
Overview
The podcast discusses the importance of play and exploratory approaches in software testing, emphasizing that testing is not just a technical task but a creative, human-centered activity. Exploratory testing is described as “purposeful play,” fostering curiosity, learning, and collaboration. The use of games, Lego, and interactive workshops helps teams overcome judgment barriers, enhances problem-solving, and makes testing more engaging. These playful methods are particularly effective in teaching and consulting, though organizations may resist them unless they recognize their value in improving innovation and team dynamics.
The discussion also highlights the critical role of people and interpersonal relationships in project success, noting that team dynamics and communication are often more impactful than tools or processes. Storytelling is presented as a powerful method for conveying risks and insights, especially when facilitating others to share their experiences. The podcast touches on the challenges of remote work, the undervaluation of exploratory testing in metrics-driven environments, and the need for broader skill sets in testing teams. Additionally, the rise of large language models (LLMs) is acknowledged as a transformative force in testing, requiring testers to adapt while maintaining critical judgment. Mentorship, continuous learning, and confidence in one’s findings - especially for junior testers - are emphasized as essential to effective testing practice.
What If
-
What if you turned your next client discovery call into a playful, Lego-inspired workshop to uncover hidden risks?
- Move: Design a 30-minute interactive session using simple physical or digital props (e.g., Miro with sticky notes, Lego blocks, or emoji-based risk cards) where the client maps their system and identifies potential failure points through guided play.
- Why Now?: Clients increasingly struggle to articulate real risks in complex systems (especially AI/LLMs), and traditional questionnaires fail to surface edge cases - playful engagement breaks cognitive barriers and reveals deeper insights.
- Expected Upside: Differentiate your consulting offer, increase perceived value, and uncover high-impact risks early - leading to higher conversion rates and larger contract scope.
-
What if you launched a weekly “Exploratory Sprint” on your own SaaS product or side project to simulate critical infrastructure testing?
- Move: Dedicate 90 minutes each week to unscripted, curiosity-driven testing of your software - using techniques like boundary pushing, data corruption, or role-playing user personas - then document one high-value insight or improvement.
- Why Now?: As LLMs and complex systems grow in your stack, unknown risks multiply; structured testing misses emergent behaviors, while exploratory sprints mimic real-world chaos and build sharper judgment.
- Expected Upside: Discover and fix critical bugs before users do, improve system resilience, and generate compelling case studies to attract clients or investors.
-
What if you replaced your next solo presentation or demo with a story-driven, peer-facilitated format to boost engagement and credibility?
- Move: Instead of presenting alone, structure your talk around 2 - 3 short, anonymized client stories (e.g., “How a hidden O-ring risk almost sank a fintech app”) and use prompts to invite audience reflection or sharing via chat or voice.
- Why Now?: Audiences tune out lectures but engage with stories; as a solo operator, your influence depends on perceived insight, not just content - storytelling builds trust and memorability.
- Expected Upside: Increase audience retention, generate word-of-mouth referrals, and position yourself as a thought leader - leading to more speaking invites, leads, or collaboration opportunities.
Takeaway
- Integrate playful, hands-on methods like games or physical tools (e.g., Lego) into your client workshops or testing sessions to improve engagement and uncover hidden system behaviors.
- Actively facilitate storytelling in client meetings by guiding stakeholders to share their own risk and failure experiences, making complex issues more relatable and actionable.
- Dedicate time blocks for structured exploratory testing in your development workflow, treating it as a core deliverable rather than an optional add-on.
- Build credibility with clients by combining strong content (clear problem-solution framing) with confident, memorable delivery - even in virtual presentations - using humor or props when appropriate.
- Invest in learning and applying systems thinking (e.g., through Jerry Weinberg’s books) to better understand and communicate how technical, human, and business factors interact in software projects.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.