I think this is incredibly important at most levels of the organization. Pushing for 100% capacity utilization (e.g. no downtime or slack) doesn't leave any roo

I think this is incredibly important at most levels of the organization. Pushing for 100% capacity utilization (e.g. no downtime or slack) doesn't leave any room for garbage collection (and other optimizations) to occur in people's minds. Often the "Eureka" moment can't be found if you're exhausted after working full-tilt all day. I also find that individual contributors, particularly in a software context, need more downtime than you think. Sure, you can solve just about any problem quickly if you rush, but you're introducing bugs (subtle or overt) that will have to be cleaned up later. I'm not saying that programmers should sit in their office chair all day staring out the window, but some amount of it is a good thing.