That’s a “utilisation” view, and it’s a terrible model.
People who already have work to do are not responsive to new input.
By ensuring everyone is working all the time you also ensure nobody can respond to the unexpected.
The counterpoint to utilisation thinking is latency thinking (“how fast can our team respond to requests”).
An instance of utilisation thinking: “Our roads are not always full of traffic, how can we get more cars onto them?”. This is clearly absurd; why is “developers have work to do” a goal when “roads have cars on them” is not?
People who already have work to do are not responsive to new input.
By ensuring everyone is working all the time you also ensure nobody can respond to the unexpected.
The counterpoint to utilisation thinking is latency thinking (“how fast can our team respond to requests”).
An instance of utilisation thinking: “Our roads are not always full of traffic, how can we get more cars onto them?”. This is clearly absurd; why is “developers have work to do” a goal when “roads have cars on them” is not?