Modern software work needs testers who lead with curiosity and craft. The role moves from gatekeeper to partner in delivery. Good testers ask sharp questions, share knowledge, and help teams break silos. They push for outcomes, not vanity KPIs. They step in early when delivery slips and help reshape habits and structure. Tools, including AI, speed analysis and coverage, but judgment stays with people. Quality includes accessibility and emotional fit, not just green checks. The message is simple. Build teams that talk, learn, and act on evidence. Keep technology in service of human needs. That mindset keeps products honest and teams resilient.
In this episode, I talk with Laveena Ramchandani about thought leadership in testing and the changing role of testers. Laveena sees testers as engineers who lead by example, ask smart questions, and break silos. She coaches teams to share knowledge, speak up, and aim for team goals, not vanity KPIs. We touch hard calls too, like stepping in or reshaping a team when delivery slips. On AI, we agree to use the tools, then add human sense and the feel of quality, like accessibility and emotion. Testing stays very human.
"When you have to make hard decisions for the right decisions, do it. Do not feel bad, you're doing the right thing." - Laveena Ramchandani
Laveena Ramchandani is a seasoned Test Manager at easyJet with over a decade of hands-on experience in quality assurance, data science testing and digital transformation. She holds a degree in Business Computing from Queen Mary University of London and has built her career bridging the technical and business worlds. As a passionate advocate for inclusive and accessible digital products, Laveena has spoken internationally on topics such as accessibility, AI and data science in testing and scalable automation. She’s also a blogger, trainer and community leader who enjoys demystifying complex testing science and helping new testers find their voice. When she’s not testing code or delivering workshops, you’ll find her diving into the latest data models, tooling, or exploring how teams can build high-quality products that truly meet user needs.
Testing is far more than a job title or a list of responsibilities. As Laveena Ramchandani explained, testers are engineers—they write code, solve problems, and crucially, influence team processes and mindsets. Often, testers become the “single source of truth,” connecting people and information across silos.
It’s not about being a bystander who just checks boxes. Laveena Ramchandani described the importance of being hands-on, supporting colleagues, and leading by example. When testers actively engage, challenge old processes, and ask “why?” they give stakeholders the data and insights that drive better decisions—ultimately influencing the direction of projects and company culture.
True thought leadership isn’t just about having a title. Both Richie and Laveena stressed the value of leading collaboratively. That means working side-by-side, coaching teammates, and encouraging ownership rather than simply managing tasks from above.
Testers should set examples that inspire others: tackle challenges openly, show persistence in solving problems, and tailor communication styles to connect with both introverts and extroverts. Sometimes, the best way to help the team step up is by guiding them to ask their own questions and discover solutions, instead of feeding them all the answers.
A recurring theme in the conversation was the problem of silos—when people or teams hoard information or shield their expertise. Laveena called for openness: “Quality should matter to all of us…why keep data to yourself?” When information and processes are shared, teams deliver faster and learn together.
Of course, opening up isn’t always easy. Some stakeholders may shut doors or dismiss testers’ questions. That’s where persistence and creativity come in: offer the benefits for the whole team and use “smart” communication to win buy-in. Even if every answer isn’t attainable, progress is made through shared vision and collective action.
Not everyone feels comfortable asking tough questions or taking initiative, especially those newer to the field or more introverted. So how do leaders help testers to level up?
Richie asked what happens when testers say, “I can’t do that.” Laveena recounted how, in those instances, self-reflection and tough decisions are needed: Is the blocker a skills gap, or something deeper? Sometimes, as a leader, she’d roll up her sleeves and test herself to set an example. Other times, reshaping the team or seeking new talent may be necessary. The key is fostering an environment where testers feel supported to grow, experiment, and find their own leadership styles.
Finally, the hot topic: AI. With automation and AI-powered tools on the rise, both speakers agreed that the tester’s job is evolving but far from obsolete. Using internal AI tools to generate test cases and streamline work is smart, but testers' judgment remains crucial. No machine can replicate the subtlety of human “feeling” when it comes to accessibility, user experience, or understanding emotional responses to applications.
AI might change how work is done, but strategic, out-of-the-box thinking will always be in high demand. Testers provide critical perspective; as Laveena said, “Developers cannot be testing their own job…that causes a massive bias.” Testers ask questions that others might not have considered.
Software testers are more than gatekeepers—they’re connectors, collaborators, and agents of change. Whether navigating team dynamics, breaking down silos, or integrating new technologies, testers who embrace thought leadership help their organizations build not just better software, but better cultures.