Do you have a work stage in your process where things get “stuck”? While we typically look for a process problem, what if I told you it’s likely that your team behavior is the real culprit?

All teams will eventually experience challenges with how work moves through their system. These problems can often manifest as a “blocked” column creeping into your flow, or even the well-meaning “Waiting for Reporter Input” limbo.

These problematic stages are sucking the work in but nothing comes out. They begin to look and feel like black holes. Agile Black Holes are detrimental to your process and your team’s morale, but they are often hard to spot until they become supermassive giants. Unlike the celestial version, once you detect the Agile Black Hole in your process, you can understand the cause and escape.

Have you fallen into an Agile Black Hole? How can you prevent black holes from forming in your process? More often than not, the root cause of the black hole is not the process, but the culture of the team. You’ll need to dig to the root cause of the negative team behaviors to understand how to change the team culture and prevent the agile black hole. Join me and become equipped to avoid the madness of the Agile Black Hole. You’ll also see what Cerner did to address one of our “black holes” and what we’ve learned as a result.

This presentation is for anyone wanting to improve the team culture by understanding the cognitive, psychological, and UI design concepts for why work slows.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.