Stephen Platten shares his transition from RAF avionics engineer to software testing, emphasizing military discipline, Stoic philosophy, and structured problem-solving in quality engineering. He highlights pivotal career moments, challenges in testing evolving technologies, and the importance of collaboration, communication, and pragmatic leadership in fostering resilience and innovation.

Quality Talks

Quality Talks is Stu Day and Chris Henderson and different guest each episode. Released as audio and video. The official Show notes have summary, key points and time stamped chapters.

• https://qualitytalks.co.uk/podcast
• https://www.youtube.com/@QualityTalksPodcast
• https://anchor.fm/s/f6e76df4/podcast/rss

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/qualitytalkspodcast/episodes/From-The-Royal-Air-Force-to-Leading-Quality-with-Stephen-Platten-e3hil6o
• Published: 2026-04-08T05:00:00Z
• Duration: 01:21:01
• Author: Quality Talks Podcast

Overview

The podcast episode features Stephen Platten, known as “The Stoic Tester,” who transitioned from a career as an avionics engineer in the Royal Air Force (RAF) to software testing. His journey highlights the influence of military discipline and structured training on his approach to quality engineering, including meticulous attention to detail and systematic testing. Stephens work spans roles in defense contracting, civilian testing, and his current role as a Principal Consultant at Inspired Testing, where he advocates for MOT (Mobile Testing) accreditation. The discussion explores his career shift from engineering to testing, emphasizing the realization that his passion lay in validation and problem-solving rather than design. He shares insights from a pivotal project at BAE Systems, where identifying a technical issue led to a career-defining moment, and how military experiences shaped his focus on process adherence, evidence-based decision-making, and pragmatic leadership.

Key themes include Stephens application of Stoic philosophy to testing, emphasizing control over responses to uncontrollable external factors and prioritizing actionable improvements over perfection. He addresses challenges in testing, such as managing infinite variables and adapting to AIs rapid evolution, while advocating for a balanced, pragmatic approach to technology integration. The episode also highlights his views on communities of practice, urging collaboration across testing and development teams to foster innovation. Stephen stresses the importance of concise communication, mentorship, and servant leadership, drawing parallels between military discipline and the need for structured yet flexible workflows. His reflections on burnout prevention, the value of personal accountability, and the role of testers as guardians of quality underscore his belief in resilience and continuous learning within the testing profession.

What If

• What if you applied military discipline to your daily testing routines but with modern software development flexibility?
  Move: Adopt structured testing protocols (e.g., daily standups, artifact reviews) inspired by RAF routines, but pair them with Agile adaptability (e.g., iterative feedback loops).
  Why now: The text highlights how rigid processes in military training (like bed-making) fostered precision, which translates to disciplined testing practicescritical as solo developers often lack team oversight.
  Expected upside: Improved consistency in testing outcomes and reduced errors, while remaining agile to adapt to shifting project needs.

• What if you launched a micro-community of practice (CoP) tailored to your niche in software testing?
  Move: Start a small, targeted CoP (e.g., Slack group or LinkedIn forum) focused on a specific pain point (e.g., AI testing or legacy system modernization), prioritizing organic engagement over forced participation.
  Why now: The text emphasizes that communities grow through value-driven actions, not mandatesa solo developer can leverage shared challenges to build influence and resources without overcommitting.
  Expected upside: Access to peer support, collaborative problem-solving, and a platform to share your expertise, enhancing your professional network and credibility.

• What if you embraced Stoic testing principles to mitigate burnout from AI integration challenges?
  Move: Allocate time weekly to assess AI tools for testing (e.g., code generation, automation), but focus on controllables like incremental adoption and documentation of limitations.
  Why now: The text warns AI may accelerate errors and displacement, but Stoicism advocates focusing on actionable steps (e.g., learning AI tools) rather than fearing uncontrollable factors.
  Expected upside: Reduced anxiety around AIs impact, improved resilience, and a pragmatic edge in leveraging AI tools while maintaining quality control.

Takeaway

• Leverage transferable skills: Identify and apply military or engineering habits (e.g., attention to detail, structured problem-solving) to your software testing or development workflow to improve quality and efficiency.
• Implement structured exploratory testing: Use frameworks with “guardrails” (e.g., predefined test scenarios or goals) to balance creativity and direction during exploratory testing, ensuring thorough coverage without losing focus.
• Build communities of practice: Engage with peers by sharing knowledge through informal mentoring, lunch-and-learns, or collaborative projects, even if youre not a formal leaderthis fosters growth and reduces isolation in solo work.
• Adopt a Stoic mindset for control: Focus on actionable controllables (e.g., testing methods, resourcefulness) rather than external constraints (e.g., budget, tools) to reduce burnout and stay productive in uncertain environments.
• Prioritize outcomes over rigid processes: Shift from strict adherence to testing methodologies (e.g., ISTQB) to pragmatic solutions that ensure software “works” for its intended purpose, adapting workflows based on context and stakeholder needs.