Re:How to spot symptoms of burnout on your engineering team
by Brightwise on Friday April 14, 2017 @02:18PM
(#14116058)
If we want to approach a topic "How to detect/avoid B/o" in a scientific manner, we should begin with a definition of what that condition is and what it is caused by.
It's been some years since I investigated on that topic, but I remember there are basically two paradigms:
A) Blame the guy/dev/employee
B) Blame the company/environment/manager
Depending on your point of view, you may want to settle somewhere in between these two extremes. I find "The truth about burnout" by Maslach/Leiter in my bookshelf, who where the first ones doing a proper scientific analysis. They pretty much end up with paradigm B. As a dev, I liked that.
It's been some years since I investigated on that topic, but I remember there are basically two paradigms:
A) Blame the guy/dev/employee B) Blame the company/environment/manager
Depending on your point of view, you may want to settle somewhere in between these two extremes. I find "The truth about burnout" by Maslach/Leiter in my bookshelf, who where the first ones doing a proper scientific analysis. They pretty much end up with paradigm B. As a dev, I liked that.