3 ms·
Let's End Toxic Productivity
- deleted 2y ago[deleted]
- toomuchtodo 2y ago> Research by Atlassian found that 78% of respondents struggle to complete their work due to excessive meetings and a shocking 67% of people at the director level and above report having to work overtime due to meeting overload. Seventy-six percent of respondents feel drained after days packed with meetings, and 80% believe they’d be more productive with less meeting time. Parkinson's Law – "Work expands to fill the available time" If we don't ratchet back the work week through reduced total hours available ("4 day work week" colloquially), that time will be filled, regardless of value delivered. There is no mechanism or pressure relief to push back against unnecessary work. But, because of those whose identity is tied to their work (one example [1]), it is a challenge to institute this system improvement. > Leaders play a crucial role in either perpetuating or breaking the cycle of toxic productivity. Unfortunately, many leaders model the very behaviors that contribute to this unhealthy culture — sending emails late at night, forgoing time off, and glorifying overwork. You have to put leaders in positions of power who recognize this. [1] https://www.theguardian.com/wellness/2024/dec/18/boomer-men-ageing https://www.theguardian.com/wellness/2024/dec/18/boomer-men-...
- proc0 2y agoI think part of the problem is how companies fail to define boundaries for their roles, and it's probably on purpose to get the most productivity from an individual. There is no ceiling or max number of responsibilities, it is always more and more and never enough. Roles are ultimately defined to "add business value", but this is like writing a blank check. For engineering, I want to exchange code for money... as a full time position. But this does not exist as far as I know. Full time salaried basically means you own a slice of the business, and your responsibilities have more to do with business profit then exercising expertise in your technical field. As a result the expectations range from managing people to making presentations and coordinating meetings, all in the name of "engineering" except it's just running the business under the disguise of an engineering role. To me this is what has led to burnouts and dissatisfaction in my career, at times doubting it, but ultimately I concluded that I still like programming, I just don't like how the industry treats programmers.