Guest Lavina Ramshandani, a seasoned test manager, shares expertise on thought leadership, collaboration, and effective communication in the software testing field. She emphasizes the importance of testers influencing team culture, driving innovation, and shaping the future of the industry through collaborative work and open communication.

Software Testing Unleashed

Software Testing Unleashed - hosted by Richard Seidl. Different guest per episode. The official Show notes contain a comprehensive overview of the episode. Released as audio and video.

• https://www.richard-seidl.com/en/testing-unleashed
• https://www.youtube.com/playlist?list=PL48Mbm-L0hjB1OdwYi9h7jrq9t352-Zk_

Episode Details

• Show Notes: https://www.richard-seidl.com/en/blog/thought-leadership-testing
• Published: 2026-01-22T05:00:00Z
• Duration: 1100
• Author: Richard Seidl | Software Development & Testing Expert

Overview

The podcast explores the shifting responsibilities of testers in modern software development, stressing the need for them to take on more proactive and influential roles. It underscores the importance of thought leadership, collaboration with engineering teams, and effective communication as key tools for driving positive change and ensuring quality is prioritized from the start of a project. Testers are encouraged to step beyond traditional testing duties and engage more deeply in development processes, questioning outdated practices and promoting quality-aware approaches.

The discussion also covers the role of AI in testing, acknowledging its potential to streamline repetitive tasks but emphasizing the irreplaceable role of human judgment in evaluating user experience, emotional intelligence, and subjective quality factors. Furthermore, it highlights the benefits of diverse team roles, the value of coaching and career growth, and the need to dismantle organizational silos to foster better collaboration and more successful outcomes. The episode aims to guide and inspire testers to expand their influence and adapt to the evolving field of software testing.

What If

• What if you started a monthly test leadership blog to influence your engineering team’s culture?

  • Concrete move: Write and publish 3 short blog posts explaining how testing drives innovation, using the Vestas example as a case study.
  • Why now: The podcast emphasizes thought leadership as a tool for change without authority, and your team may still be siloed or resistant to collaboration.
  • Expected upside: Building credibility as a testing advocate could encourage peers to adopt your ideas, improving team dynamics and reducing rework costs.

• What if you embedded yourself as a “testing co-owner” in a feature development sprint?

  • Concrete move: Volunteer to work alongside developers during a sprint, writing tests in real-time and discussing edge cases with the team.
  • Why now: Lavina stresses the need for testers to be “hands-on” and not outsiders. Solo operators often lack this role, but this approach aligns with the podcast’s emphasis on collaboration.
  • Expected upside: Youll gain deeper technical alignment with developers, reduce misunderstandings, and create a shared ownership of quality that cuts bugs early.

• What if you piloted an AI-assisted test automation tool for one project, then manually explored its emotional usability?

  • Concrete move: Use AI to generate 50 automated test cases for a feature, then spend 2 hours manually testing user flows for emotional cues like frustration or delight.
  • Why now: The episode highlights that AI cant replace human judgment in “loved” vs. “overwhelming” experiences, which is critical for user retention in solo-developer products.
  • Expected upside: Youll balance efficiency gained from AI with insights that ensure your product feels human, reducing post-launch churn and increasing feedback-driven iterations.

Takeaway

• Start with incremental learning: Acknowledge that partial understanding is acceptable and begin taking small, timed steps toward mastering new skills or processes, even if progress feels slow or incomplete.
• Leverage AI tools for testing but prioritize human judgment: Use internal AI tools to automate repetitive tasks like test case creation, but always apply your own judgment and common sense to ensure subjective aspects (e.g., user experience, accessibility) are not overlooked.
• Foster collaboration by breaking down silos: Actively share information and encourage open communication with stakeholders or external collaboratorsthis improves team dynamics and ensures quality, even in solo projects.
• Ask probing questions to drive team (or personal) improvement: When facing pushback from stakeholders or team members, frame requests as opportunities for collective growth and ask reflective questions like, How can we improve this together?
• Invest in quality assurance practices: Prioritize testing processes, including edge case exploration and bias mitigation, even if your team size is small. Allocate time to ensure software quality aligns with user experience and business goals.