SOBRE ESTE EPISÓDIO
📘 Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English 👉 Get it for free
"If you have a good understanding, solving the problem is actually easy. The hard part is understanding it." - Ben Linders
In this episode, I talk to Ben Linders about what really drives team autonomy and effective software development. We get into team culture, the importance of psychological safety, and why diversity matters - not just as a feel-good topic, but as a genuine catalyst for change. Ben shares practical tips from his workshops, discussing how teams can move from being stuck to taking meaningful action. We discuss, how to avoid that sticky notes from retrospectives gather dust and how to make results visible, keeping actions manageable, and introducing a little bit of fun through gamification.
Ben Linders runs a one-person business in Agile, Lean, Quality, and Continuous Improvement. Ben is a well-known speaker and author; he is much respected for sharing his experiences and helping others share theirs. His books and games have been translated into more than 12 languages and are used by professionals in teams and organizations all around the world. As a trainer, facilitator, coach, and advisor, he helps organizations with effectively deploying software development and management practices. He focuses on continuous improvement, collaboration and communication, and professional development, to deliver business value to customers.
Highlights:
- Psychological safety is destroyed faster than it is built: a single blame remark can undo weeks of trust, so facilitators must interrupt blaming the moment it appears.
- If a team cannot generate at least three distinct solutions to a problem, the problem is not yet understood well enough, and exploration must continue.
- Diversity in a team is a prerequisite for collaborative problem solving, because each person holds only part of the picture, and different views produce a richer, more accurate shared understanding.
- Making retrospective actions visible on the daily task board, assigned to a person and framed as a testable experiment, is what separates actions that get done from sticky notes that stay untouched.
