"Employees who are loud quitting are taking actions that "directly harm the organization, undercutting its goals and opposing its leaders,“Gallup says.”

In this spirit, what have you do to sabotage or undermine your employer, and what radicalized you to take those steps?

I’ll start, I work in construction engineering and I was radicalized when the company owner made a last minute change to some of our materials to save a couple pennies on each unit, then asked me for an updated analysis right before we signed the contract.

When I gave him the analysis, surprise surprise, the change to cheaper materials had some negative downstream impacts. He called me up to yell at me, berating me and accused me of trying to intentionally sabotage his company. It didn’t matter that I had literally just run the numbers that came from his own choice and handed him the output, in his mind this was all my fault.

From that point on I figured if I’m going to be accused of sabotaging the company then I may as well do it for real.

  • LanternEverywhere@kbin.social
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    1 year ago

    “quiet quitting” isn’t a real thing, that’s a phrase companies use to try to coerce you to give them free labor. Quiet quitting just means “doing your job”. If they want you to do additional labor then they rightfully must pay you to do that extra work.

    • fuck_u_spez@lemmy.fmhy.ml
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      Realizing that workers do not get compensated based on merit.

      Yeah I’m also much happier writing quality open source code, I think I’m learning way more, have more fun coding and everything feels more “arty” (in terms of code quality/innovation) compared to what I’m doing in my day-to-day job, where the priority always seems to be to minimize costs, instead of promoting “advancing the state of the art” in whatever area that is (which often obviously takes quite a bit more time, but in the long run would just be better in most cases). (not even starting that a quality open source library helps probably way more people than the one “quality” library down the stack in the corporate app)