Jackson: Alright, Miles, we've covered so much ground here. I'm imagining our listeners are thinking, "This all sounds great, but where do I actually start?" If someone wants to improve testing in their organization—whether it's software testing, product testing, or any other kind—what's the practical playbook?
Miles: That's the key question, isn't it, Jackson? And I think the first step is always assessment. You need to understand your current state before you can chart a path forward. What are you testing now? How are you testing it? What problems are you trying to solve?
Jackson: So it's like doing a testing audit of your existing practices.
3:02 Miles: Exactly! And this assessment should cover both the technical and cultural dimensions we've been discussing. Are people afraid to report bugs? Do you have clear definitions of what quality means for your products? Are your current tests giving you confidence or just creating busywork?
Jackson: Once you've done that assessment, what's next?
Miles: I'd recommend starting with what I call "high-impact, low-risk" improvements. These are changes that can deliver quick wins without requiring massive organizational upheaval. For example, if you're doing mostly manual testing, you might start by automating just your most critical happy-path scenarios.
Jackson: So you're building momentum and demonstrating value before tackling the bigger challenges.
3:02 Miles: Exactly! And as you implement these initial improvements, you want to measure their impact. Are you catching bugs earlier? Are releases going more smoothly? Are people feeling more confident about changes? These early wins help build support for more ambitious improvements later.
Jackson: What would those more ambitious improvements look like?
Miles: Well, that depends on your context, but it might involve shifting testing earlier in your development process, implementing continuous testing practices, or expanding your definition of quality to include things like performance, security, and accessibility.
Jackson: And I imagine this is where the cultural elements become really important.
3:44 Miles: Absolutely. The technical changes are often the easy part. The hard part is helping people change how they think about quality and testing. This might involve training, changing incentive structures, or even adjusting hiring practices to bring in people with strong quality mindsets.
Jackson: What about organizations that are just starting out? Do they have an advantage because they can build good practices from the beginning?
Miles: They definitely have some advantages—no legacy practices to overcome, no existing technical debt in their test suites. But they also face the challenge of building testing practices while simultaneously building their product and team. The key is to start simple but with good foundations.
Jackson: What would those good foundations look like?
Miles: I'd focus on three core principles: test early and often, automate the repetitive stuff, and make quality everyone's responsibility. Even a small team can implement basic unit testing, set up simple CI pipelines, and establish the cultural norm that everyone cares about quality.
Jackson: And then they can build on those foundations as they grow.
3:02 Miles: Exactly! The specific practices will evolve, but those foundational principles will serve them well regardless of how their organization develops.
Jackson: What about teams that are dealing with legacy systems or established practices that aren't working well?
Miles: That's definitely more challenging, but not impossible. The key is often to start with new features or components while gradually improving testing around existing functionality. You might implement better testing practices for new code while slowly adding test coverage to critical legacy areas.
Jackson: So it's an incremental transformation rather than a big-bang replacement.
Miles: Right, and this is where having executive support becomes really important. Leadership needs to understand that improving testing practices is an investment that pays dividends over time, not just an expense. They need to give teams the time and resources to do it right.
Jackson: What would you say to leaders who are skeptical about investing in testing?
Miles: I'd focus on the business impact. Better testing practices lead to fewer production issues, faster feature delivery, and more confident decision-making. There's substantial research showing that organizations with strong quality practices outperform their peers on key business metrics.
Jackson: So it's not just about preventing bugs—it's about enabling business success.
3:02 Miles: Exactly! And for our listeners who want to get started, I'd recommend picking one area where testing could have immediate impact and running a small experiment. Maybe it's adding automated tests to your most critical user workflow, or implementing basic performance monitoring, or just starting to track and analyze your bug patterns.
Jackson: The key is to start somewhere and learn from the experience.
3:44 Miles: Absolutely. Testing excellence isn't a destination—it's an ongoing journey of continuous improvement. And every organization's journey will look a little different based on their unique context, constraints, and goals.