Pod Insights The Agile Daily Standup - AgileDad End Team Disruption NOW! About this episode End Team Disruption NOW! How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 A lot of people ask me, "What is the key to building better products?" And some people are surprised when I tell them what the key actually is. A lot of people think that building better products revolves around doing things a certain way or saying certain things.
0:33 Speaker 00 But it doesn't. Building a better product revolves around limiting WIP and eliminating disruptions. Now, many people don't understand how team disruption impacts delivery. But what I can tell you is disruption is the killer, right? It kills everything that we're trying to do. When a team is disrupted, the cost of interruption is so high. So how do we overcome this? How do we sort through and get teams to work with balance and without interruption? I think the key here is to allow them to understand, them being the organization, to understand that the team needs that centralized time to focus on what they're trying to get
1:14 Speaker 00 done and apply Little's Law to do more by doing less. Getting things done that they started, stop starting new stuff and start finishing the stuff that you've begun. And I think more organizations forget about that. Each time someone is disrupted or pulled off task, it costs the organization tons of effort, time, and money. I feel like the teams that operate the best are the ones that have zero interruptions. And one way to do this is a concept that I affectionately call Team John. And that's by rotating one person off of each team to help assist with running the interruptions and taking care of whatever comes in and determining, help triage and determine
1:57 Speaker 00 whether something is an immediate need that needs to be taken care of or whether it's something that requires a discussion with the product owner to be queued up in a future sprint. And I feel like that is the key in essence to doing this. And if you rotate people through that Team John position, it's going to give each person a two-week period where they may have less to work on because they're not focused on things that are in a current backlog. It's going to help them really regain their focus and regain their energy. So they can address immediate concerns that come in, but also so that they're prepared to jump in in the next sprint and tackle some of the bigger, more critical issues. I just think it's important for us to not let the core team get disrupted by doing this conceptually.
2:39 Speaker 00 We are in turn giving someone a chance to get a head start on work going forward. And by allowing the team to stay focused and not be interrupted, they actually finish more work than they would if you allowed them to function as normal with the interruptions. So what I'm trying to say is a team, a high performing team of five with constant interruptions versus a low performing team of five with no interruptions, the low performing team is likely going to get more work done or the same amount of work done, which is incredible because the interruptions are really more catastrophic than what you make them out to be. I think that if you can stop focusing so much on interruptions and focus on what you could
3:23 Speaker 00 do to build products and services that disrupt your market and become disruptive instead of interruptive, I think that's going to help you really capitalize on what you're trying to do and help you be the best at achieving your goals when it comes to building better products and services. So find key ways, critical ways to stop the team from getting interrupted, focus on providing better value, help people to really engage. And if you do those things, that's going to help you be successful with your agile implementation. That's going to do it for this short episode. I hope you enjoyed it. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous The Customer is Mostly Wrong? - Could It Be True? Next Three Ways To Refocus In Your Daily Scrum - Standup Page updated November 7, 2026 · transcript and summary are machine-generated