DevOps - Idle Time

When we talk about DevOps, we often hear references to lead time and cycle time. In this post, I want to focus on idle time instead. In Gene Kim's The Phoenix Project, there's mention of an interesting graph that plots wait time as a function of how busy a resource is. It shows that wait time skyrockets when resources are more than 80 per cent busy. (Wait time = %Busy / %Idle) %Idle being 100 - %Busy.

It shows that we all need to cut some slack (10 to 20 %) when we pack our calendars – i.e., 10 – 20 per cent idle time is required to avoid long delays. It sounds like one more DevOps principle that is Counter intuitive and Contradictory.

Inspired by Morgan Housel's way of thinking, I see that the concept of ‘idle time’ is applicable to diverse fields as well. We can see the same logic in action in either evolution or in investing. Just like a specific cash position is needed to capture the opportunity when it arises, we need a specific idle time to reduce wait times.

?Our CEO, Bill McDermott, means the same when he suggests blocking time in our calendars for some creative thinking. Who knows what ‘Eureka' moment someone can come up with while idling?