It’s great for some things, but it also gives the devs more time (and moral authority) to think about the flaws in other parts of the organization. It seemed like there was just as much complaining and stressing about things, it was just different things.
I suspect this is why the “good enough” culture of thick-skinned, slightly masochistic people who put up with the same busy work is the de facto standard.
Part of what drew me to software was that you “figure out” how something works, you write a bit of software to manage that task, and move on to the next problem. I amazes me how many people who are capable of automating simple tasks are content to simply repeat them instead.
You would effectively have to have people dedicated simply to this task, with massive managerial powers checking all management decisions and keep reminding all folks to stick to them (I can't imagine any other way). Its not only about things on paper like benefits and working hours, but overall company culture, agility to change and corner cases. If you manage that, kudos to you, but you are rather an exception.
I've seen it first hand - an amazing, startup-like company, growing super fast, and culture suffered.
(and I'm putting my money where my mouth is: here at TalkJS.com we're VC funded and on a steep growth curve, and we also have sane working hours and good benefits etc etc)