this post was submitted on 05 Apr 2024
1063 points (97.5% liked)

Not The Onion

12254 readers
789 users here now

Welcome

We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!

The Rules

Posts must be:

  1. Links to news stories from...
  2. ...credible sources, with...
  3. ...their original headlines, that...
  4. ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”

Comments must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.

And that’s basically it!

founded 1 year ago
MODERATORS
 

(water is wet and fire is hot).

(page 5) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 7 months ago

Don't feel as if you are alone. People in other countries are quitting the rat race too.

[–] [email protected] 16 points 7 months ago (2 children)

At least I learned something from this article. Highfalutin is a word in the English language.

[–] [email protected] 6 points 7 months ago

I've heard it but never seen it written down haha

load more comments (1 replies)
[–] [email protected] 79 points 7 months ago (24 children)

This just puts a huge spotlight on the thing I hate the most about my line of work. I'm sure it's not just my line of work with this problem, but there's plenty of examples of workplaces that do not have this problem.

My career is in IT support. Whether doing systems administration or networking or something else related, it's my lifeblood.

Almost every job I've ever had in this field works on the basis of tickets. A concept which, isn't in and of itself a problem, nor is it unusual. Similar systems exist in many careers; they're similar to a chit in the restaurant industry, which contains an order, which is passed to the kitchen for the cooks/chefs to complete. Same thing. And there's examples of this same idea across many careers, called all kinds of things from a requisition, to a work order, they're all variations on the same idea.

The trouble begins with how tickets are worked and completed. In other industries, you pick up a task, whether a chit or work order, you finish the task, and you mark it as complete, but in IT, it's very different in one key way. We have to not only justify and report everything we do, but also mark down exactly how long it took. It's this last point that's the problem. I am under continual scrutiny, every minute of every day to justify what I've done, and when I did it. In every job I've had, my ability to fill every second of my day with records of what I've done and how long it took to do is praised, or the lack of that ability can create some significant issues with maintaining my employment status.

There are good reasons to keep these records, to have a record of changes, and coordinate with coworkers, in the event they need to continue work I've started, or vice versa, and to note when something changed so that if issues arise, those actions can be examined as a potential cause. But this requirement has become weaponized by every employer to keep a stranglehold on productivity. If you take too long on a task that they think should have taken less time, you're suddenly found in a meeting where you have to explain why you were so inefficient. If you excel and you're able to complete your tasks quickly, that faster pace becomes the new standard, and anyone who isn't capable of keeping up gets reprimanded for dragging their heels and wasting time.

The goal posts continually move. I can't so much as take an extended shit without someone taking notice.

Meanwhile, so many jobs are simply focused on being present and looking busy. Before I went into IT, I worked at a grocery store, and short of clearly and obviously standing around doing literally nothing, no manager even took notice of you. If you were doing something, literally anything that looks even remotely productive, you were left alone. Which isn't to mention all the down time, when there isn't anything to do, and you just go and adjust the products on the shelf needlessly because it made you look busy. That same concept can be applied to a lot of different jobs, but with IT, it's not sufficient to simply look busy. Your time must be put into a ticket.

It's oppressive and the way of things in IT.

[–] [email protected] 9 points 7 months ago (4 children)

The problem is your boss. I work with tickets and just have a maximum for the average amount of time to be under for the quarter. It's very relaxing.

You need to explain to your boss that different tasks take different amounts of time. Explain that you may be able to do things faster at the risk of larger issues taking up more time later. Then when they tell you to work faster, reiterate that it will cause bigger issues.

Literally give them what they want: fast solutions at the expense of quality. Then don't worry about it when things eventually break.

load more comments (4 replies)
[–] [email protected] 13 points 7 months ago (8 children)

Mechanics at your local car dealer likely get paid on flat rate. That means they get paid a set amount of hours based on the time estimate for the job, regardless of how long it takes. Also, manufacturers set lower times for warranty repairs than you would get paid if the customer had to pay. Also, if there is no book time, you have to guess ahead of time. If the vehicle comes back, you have to work on it for free. You also get service writers and managers breathing down your neck while you're trying to troubleshoot and not understanding how long things take and also pressuring you to upsell unnecessary services and repairs. Anyway, I don't work on cars anymore.

load more comments (8 replies)
[–] [email protected] 12 points 7 months ago (1 children)

Opposite scenario in my dept. The boss wants to improve our time tracking so he can justify asking for more staff.

"Yes the rest of the org needs 500 new starters a week but you guys can manage, right?"

load more comments (1 replies)
load more comments (21 replies)
load more comments
view more: ‹ prev next ›