best-lamby

pro-mask furry commie

  • they/baa

late 20 something transgender who loves to kill racists & ableists & terfs

free palestine
🇵🇸🍉
stop the genocide

if ur niceys follow me


DeviousVacuum
@DeviousVacuum

I've spent my career working at startups, and now that I've started this new job as an engineering manager, I've realized that most of my team and my fellow managers have a serious martyrdom problem. They're excited about what they do, so they keep working through meals, while sick, constantly letting management push down more and more tasks on them. They say they love their jobs but then are confused why they feel so stressed and otherwise have symptoms of burnout.

Now my fellow anti-capitalists, you know what I'm talking about here. They are being exploited in a way that, if they read an article about Amazon workers doing the same things, instead of their healthcare startup, they would be upset about. Where Amazon would be doing it on purpose, the execs at this startup are stressed out but largely well-meaning despite being capitalists. Instead of not caring whether their employees are sick, they simply could never imagine doing something like skipping a doctor appointment to work. It's not like their employees are telling them that they are skipping doctor appointments, so how could they guess that it's happening? They give their employees plenty of PTO hours, but nobody ever takes them!

Our behavioral goals in this situation are to 1) only work the number of hours that you are paid for, 2) take required breaks and regular sick/PTO, and 3) clearly communicate boundaries about how much work you can get done in a certain amount of time. So I've been getting my materials ready to go over with my direct reports, and I thought I would share my big list of reasons here, because different strategies work for different people.


t0v
@t0v
This page's posts are visible only to users who are logged in.

You must log in to comment.

in reply to @DeviousVacuum's post:

We’re implementing a new AMS at work, which is great! We really need it and it will make things easier to have something purpose built instead of kinda kludged together like we have now. I’m worried that this is going to mean we’re all just burning the candle at both ends out of dedication.

I had to fight to get JIRA implemented at my very first job, as a junior employee with a ton of perks who'd been there much longer than me, because even though I'd never experienced it I just felt like I was always being given too much and changing context too often and becoming the go-to guy for too many things, and that at least a work-tracking system would give me something to point to when I was being asked.

And ultimately we did get it, but it was too late for me. I left the company and was burned out enough that I didn't even start looking for another job for half a year. But that job had JIRA and cloud infrastructure and code reviews (and git, my God) and people who understood why all those things existed, and it kind of almost felt like my career didn't really start until I worked there.

I never really felt able to advocate for myself in the first office because it was absolutely just a Get Shit Done kind of place with people always staying late to just handle one more thing, so saying I had too much to do was met with "well you'll just need to put up with it"