Hello friends, and welcome to another episode of the Testing Peers podcast.

In this episode, Chris, Dan, David, and Russell come together for a wide-ranging conversation about flow, what it really means, and why it matters far beyond speed or delivery metrics. The discussion starts with some light New Year banter before quickly moving into systems thinking, value, and the often unseen friction that slows organisations down.

The group explore flow as something that exists across people, processes, and systems, not just CI/CD pipelines. Using plumbing analogies, real-world examples, and a healthy dose of scepticism about simplistic metrics, they unpack why optimising individual components rarely improves outcomes if the wider system is ignored.

A recurring theme is the idea that quality is about the removal of unnecessary friction, and that debt shows up in many forms, not just code. Documentation, onboarding, learning mechanisms, and organisational processes all contribute to how effectively value moves through a system.

The conversation also touches on how difficult flow is to measure meaningfully. While metrics like DORA can tell part of the story, they often focus on speed rather than outcomes, impact, or sustainability. The hosts discuss the importance of qualitative signals, trending over time, and understanding what good actually looks like in a given context.

A significant part of the episode focuses on the human side of flow, including onboarding, learning, feedback loops, and psychological safety. The group reflect on how better onboarding and clearer purpose can help people contribute sooner, feel more connected to their work, and understand the impact of what they do.

From a testing perspective, the discussion highlights how testers already have many of the skills needed to assess flow at an organisational level. Curiosity, critical thinking, risk awareness, and communication all play a role in identifying friction, asking difficult questions, and helping teams improve. At the same time, the hosts are careful not to position testers as uniquely gifted, recognising that good systems thinking comes from diverse roles working together.

The episode closes with reflections on trust, credibility, and the role of testers as trusted advisors. Being listened to is not about job titles or tools, but about doing the work, understanding the system, and backing up insights with evidence and experience.

Links and references

• DORA metrics: https://dora.dev/guides/dora-metrics/
• The Phoenix Project: https://itrevolution.com/product/the-phoenix-project/
• Theory of Constraints: https://www.leanproduction.com/theory-of-constraints/
• Stu Crocker on quality as the removal of unnecessary friction
• Post Office Horizon IT Scandal: https://clarotesting.wordpress.com/the-post-office-horizon-it-scandal/

#PeersCon26 Tickets for the event are live for just

£30.
And as always, we are looking for sponsors to make this event the success it has been for the last 2 years, get in touch if interested

Twitter (https://twitter.com/testingpeers)
LinkedIn (https://www.linkedin.com/company/testing-peers)
Instagram (https://www.instagram.com/testingpeers/)
Facebook (https://www.facebook.com/TestingPeers)

Support the show