11
Practical Applications & Listener Takeaways 21:09 Lena: Miles, as we start thinking about wrapping up our conversation, I want to make sure our listeners have some concrete things they can actually do. If someone's listening to this and thinking, "I want to bring more collaborative testing to my team," where should they start?
21:23 Miles: Great question, Lena. I'd say start with one small experiment rather than trying to transform everything at once. Maybe pick one upcoming feature and commit to writing acceptance criteria collaboratively before any coding starts.
21:36 Lena: So bring the whole team together-developers, testers, product owners-and really nail down what success looks like for that feature?
5:35 Miles: Exactly. Use concrete examples: "When a user does X, then Y should happen." These examples become your acceptance tests, and they clarify requirements in a way that prevents so many downstream problems.
21:55 Lena: What about teams that don't have dedicated testers? Because I know many smaller organizations are dealing with that reality.
22:01 Miles: That's actually more common than people think. The collaborative testing mindset still applies-developers can pair with each other to review test coverage, product owners can participate more actively in defining test scenarios, even customer service teams can contribute insights about common user issues.
22:16 Lena: So it's about leveraging whatever perspectives you have available rather than waiting for the perfect team structure?
12:37 Miles: Right. And honestly, sometimes teams without dedicated testers actually adopt collaborative practices faster because they don't have the traditional role boundaries to overcome.
22:30 Lena: What about the automation pyramid we discussed? How should teams approach building that foundation?
22:35 Miles: Start with unit tests for new code. Don't try to retrofit tests onto your entire legacy codebase immediately-that's overwhelming. But commit to writing unit tests for every new feature or bug fix. Over time, you'll build that solid foundation.
22:48 Lena: And for the middle layer-the API tests?
22:50 Miles: Those are often the biggest bang for your buck, especially for teams with web applications. You can test business logic without dealing with the complexity and fragility of UI tests. Tools like Postman or REST Assured make this pretty accessible.
23:02 Lena: What about getting organizational support? Because individual teams can only go so far without broader buy-in.
23:08 Miles: Focus on demonstrating value rather than just talking about principles. Track metrics that matter to leadership-defect rates, customer satisfaction, time to resolve production issues. When you can show concrete improvements, the business case makes itself.
23:21 Lena: And for our listeners who are in leadership positions, what should they be thinking about?
23:25 Miles: Invest in your people's skills. Collaborative testing requires capabilities that many team members might not have yet-automation skills, facilitation skills, business domain knowledge. Training and coaching are investments that pay dividends.
23:37 Lena: Also, be patient with the transition, right? Because changing how teams work takes time.
4:31 Miles: Absolutely. And create psychological safety for experimentation. Teams need to feel safe trying new approaches, making mistakes, and learning from them. If people are afraid of being blamed for problems, they won't take the risks necessary to improve.