Become a Thought Leader - Laveena Ramchandani

🚨 Are we actually testing too much sometimes? Just because we run a lot of tests doesn’t mean we’ll find a lot of bugs. Here’s how we can solve this: Free Online Workshop

"When you have to make hard decisions for the right decisions, do it." - Laveena Ramchandani

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.

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.

Highlights:

• Testers must become thought leaders by questioning outdated processes, not just executing daily tasks.
• AI cannot replace the human feeling of quality—overwhelm, accessibility, emotional design need human testers.
• Breaking silos is critical; hoarding information blocks team delivery and sabotages collective quality ownership.
• Developers testing their own code creates bias; testers think outside the box developers rarely do.
• Coach testers with open questions about their career path, not by copying strategies from other teams.