Change for good involves identifying and addressing issues within teams to create a more positive and productive work environment.

Strategies for improvement include using a “WTF List” to identify problematic practices, categorizing issues as technical or people challenges, and advocating for change through influence and cultural shift.

The Testing Peers

The Testing Peers - panel discussions about testing. Usually Chris Armstrong, Simon Prior, Russell Craxford and David Maynard, with occasional special guests. Show notes on the website have an episode description and resource links.

• https://testingpeers.com/
• https://www.youtube.com/playlist?list=PLgToaFvlUC7mruBdL9eQDS3WFcpg9ooeI

Episode Details

• Show Notes: N/A
• Published: 2026-02-10T10:00:00Z
• Duration: 2797
• Author: Testing Peers

Overview

The episode explores the concept of “change for good” through a discussion that begins with a relaxed potluck setting, where participants reflect on their personal choices and gradually shift to examining workplace team dynamics. The conversation delves into the obstacles of creating positive change in professional environments, offering strategies like developing a “WTF list” to pinpoint confusing or inefficient processes. It also distinguishes between technical challengesthose that can be solved with specific skillsand adaptive challenges, which require changes in behavior or mindset, emphasizing the importance of addressing both types effectively.

The dialogue highlights the significance of improving team dysfunction by focusing on psychological and psychosocial safety, encouraging individuals to take initiative instead of passively accepting unchangeable policies. It specifically addresses the role of QA/testers, discussing how they can reframe their contributions in a more positive light and overcome internalized stigma. The episode also touches on the power of small wins in driving larger change, the necessity of clear communication and advocacy, and the emotional toll of leading change efforts. It underscores the value of understanding one’s organizational context and culture when suggesting new ideas, and concludes with a call to actively influence positive change and find allies within the workplace to support such efforts.

What If

• What if you started a WTF list for your solo software projects today?

  • Concrete move: Document 35 frustrating or unclear processes in your workflow (e.g., manual deployments, inconsistent testing rituals). Categorize them as technical or adaptive challenges.
  • Why now: Solo operators often overlook inefficiencies due to limited perspective; a WTF list provides structure to prioritize quick wins and avoid burnout.
  • Expected upside: Identifying 12 low-hanging fruit (e.g., automating a repetitive task) could save 5+ hours weekly and improve reliability.

• What if you automated one repetitive task in your development cycle this week?

  • Concrete move: Use scripting or tools (e.g., GitHub Actions, CLI) to automate a manual process like creating a PR from a Jira ticket or running regression tests.
  • Why now: Solo developers face time constraints; automation reduces manual effort and minimizes errors, freeing capacity for higher-value work.
  • Expected upside: Immediate efficiency gains (e.g., cutting 12 hours per day) and a foundation for scalable process improvements.

• What if you framed a recent bug fix as a “change for good” in your next project update?

  • Concrete move: Write a brief post-mortem or README explaining how a specific bug fix (e.g., preventing data corruption) aligns with broader goals like user trust or system reliability.
  • Why now: Solo operators often work in silos; framing changes as part of a larger narrative helps justify efforts and builds momentum for future improvements.
  • Expected upside: Reinforces a culture of proactive problem-solving and may encourage stakeholders to prioritize long-term quality over short-term fixes.

Takeaway

• Create a “WTF List” to identify process inefficiencies: Document specific frustrations or confusing practices in your workflow (e.g., manual tasks, unclear policies) and prioritize low-hanging fruit for incremental improvements. Share these with stakeholders to drive small, tangible changes.
• Frame proposed changes with context and historical awareness: Before suggesting process or cultural shifts, research the background of existing practices to avoid resistance. Highlight how your proposal addresses past pain points or aligns with long-term goals.
• Advocate for QA/testers by amplifying their value: Actively communicate how early bug detection and testing improve software quality and reduce production risks. Use concrete examples (e.g., “This bug would have cost X hours to fix post-release”) to shift perceptions of QA roles.
• Manage up effectively by aligning with leadership priorities: Identify your “WTF List” and seek allies within the organization to address issues. Frame feedback in terms of how it supports leadership goals (e.g., efficiency, customer satisfaction) rather than focusing solely on friction.
• Automate repetitive tasks to reduce manual effort: Identify time-consuming, error-prone workflows (e.g., PR creation from Jira tickets) and implement automation tools. This improves dependability and frees up your time for higher-value work.