Flow, and creating the environment that allows devs to achieve it, is a major theme of Peopleware. Probably the central theme. So while it's always good to draw

Flow, and creating the environment that allows devs to achieve it, is a major theme of Peopleware. Probably the central theme. So while it's always good to draw attention to the problem, the problem and its solutions are not breaking news. As for a model for getting both management and devs on the same page for solving the problem, I always like the example presented by Paul O'Neill's safety-first campaign at Alcoa: http://www.post-gazette.com/business/businessnews/2012/05/13/Habitual-excellence-The-workplace-according-to-Paul-O-Neill/stories/201205130249 http://www.post-gazette.com/business/businessnews/2012/05/13... Tackle these seemingly middling but pervasive issues, both sides will see benefits and the whole company culture will probably transform for the better. Of course, if you have the type of management that would read that article and meditate on its deep implications for their software development operation, then you probably aren't dealing with these types of issues in the first place.