The podcast highlights the need to move beyond automation and scripted testing, stressing critical thinking, user-centricity, and organizational culture in software testing. It advocates redefining testers as customer-focused problem-solvers, emphasizing adaptability, unlearning outdated practices, and prioritizing real-world impact over technical fixation.

How To Test This?

interview episodes where Mamadou N’diaye talks with with software testing experts

• https://podcasters.spotify.com/pod/show/spidey1944
• https://www.youtube.com/@HowToTestThis
• https://www.linkedin.com/in/mamadou-ndiaye-consultant/

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/spidey1944/episodes/How-to-Test-With-A-Customer-First-Mindset-with-Pradeep-Soundararajan-e3kfpc8
• Published: 2026-06-08T04:36:25Z
• Duration: 00:53:38
• Author: Mamadou N’diaye

Overview

The podcast explores the evolving philosophy and challenges of software testing, emphasizing the need for critical thinking, adaptability, and a customer-centric approach. Pradeep Sundararajan, a seasoned tester and consultant, discusses the industry’s long-standing issues, including the over-reliance on automation, scripted testing, and technical jargon at the expense of deeper analysis. He critiques the misconception that testing is merely about test cases or automation, arguing instead for a focus on understanding user needs and fostering a culture of quality. Sundararajan advocates for testing with composure, drawing from context-driven methodologies and the teachings of figures like James Bach and Michael Bolton, while highlighting the emotional and psychological challenges faced by testers, such as frustration and overthinking. He also addresses the growing trend of tool obsession, warning that fixation on AI or automation can overshadow the core goal of solving real-world problems for users.

The discussion delves into the role of storytelling and unconventional analogies in making testing concepts accessible, with examples like blending spiritual philosophies (e.g., Buddhism, Yin-Yang) and real-life scenarios (e.g., parenting, politics) to explain testing principles. Sundararajan emphasizes the importance of unlearning outdated practices for experienced professionals and starting fresh for beginners, recommending foundational resources like Rapid Software Testing and works by Ken Kenner and Jerry Weinberg. He also critiques the industrys neglect of organizational culture as a root cause of software issues, arguing that systemic cultural misalignment often contributes more to bugs than technical practices alone. Looking ahead, he envisions a future where testers shift from “bug finders” to advocates for customer care, with AI likely automating routine tasks while deep critical thinking becomes more valuable. The conversation ultimately calls for systemic change to redefine testings role in prioritizing end-user value over technical debates or tool-driven approaches.

What If

• What if you unlearn outdated testing practices to adapt to AI-driven changes in the industry?

  • Move: Actively seek feedback from non-technical stakeholders to challenge assumptions and identify obsolete methodologies.
  • Why Now? The industry is shifting toward AI automation, and clinging to manual, script-heavy approaches will render you irrelevant.
  • Expected Upside: Become a critical thinker who can bridge gaps between AI tools and human insight, positioning yourself as a “critical thinking tester” in demand.

• What if you prioritize manual testing for edge cases over scripting, despite the industrys automation obsession?

  • Move: Allocate 30% of your testing time to exploratory manual testing, focusing on user workflows and ambiguous scenarios.
  • Why Now? Automation struggles with context-rich, unpredictable problems, and customers prioritize real-world usability over pass/fail metrics.
  • Expected Upside: Deliver higher-quality, user-centric products that stand out in a market flooded with automated but shallow testing.

• What if you build a customer feedback loop into your testing process to align with real user needs?

  • Move: Create a lightweight tool (e.g., a Slack bot) to collect feedback from end-users after every release and integrate it into your test planning.
  • Why Now? The industrys focus on technical jargon has alienated testers from customer value; this bridges the gap.
  • Expected Upside: Build trust with clients by proving your testing directly addresses their users pain points, increasing retention and referrals.

Takeaway

• Prioritize customer-centric testing practices by aligning your testing strategies with real-world user needs, ensuring software directly addresses customer problems rather than focusing solely on technical metrics or automation.

• Avoid the misconception that testing equals automation; emphasize critical thinking and manual testing where appropriate, as overreliance on tools can overlook deeper issues and reduce the value of human insight.

• Invest in foundational learning by studying resources like Rapid Software Testing (James Bach/Michael Bolton), Ken Kenners work, and books like Aristotle in Testing, which blend critical thinking with practical testing principles.

• Commit to unlearning outdated practices (e.g., script-driven methods or tool obsession) to adapt to AI-driven changes, prioritizing mental flexibility over rigid adherence to past methodologies.

• Volunteer at testing conferences to network and gain exposure, but extract one clear, actionable insight per event to avoid information overload and focus on practical, long-term growth.