this post was submitted on 16 Apr 2024
494 points (95.6% liked)

Memes

45719 readers
855 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] XEAL@lemm.ee 47 points 7 months ago* (last edited 7 months ago) (4 children)

Fuck Slack, Google Chat and Workplace.

Companies abuse it's use instead of using emails and tickets, it's fucking chaos.

Yeah let's make people contact us through this public chat, all at once, I'm sure it won't be a fucking mess.

[–] pruneaue@infosec.pub 22 points 7 months ago (3 children)

You can write to me by chat but no ticket no help

[–] Kurokujo@lemm.ee 7 points 7 months ago

Yeah, channel management is super important. It's useful to have a full featured chat client that can integrate into other systems, but it's important to know what the limitations are. We use Slack for internal chat only (no customers) and it works pretty well for our use case but with all the integrations available it could easily get out of hand if we let more people manage it.

[–] XEAL@lemm.ee 4 points 7 months ago* (last edited 7 months ago) (1 children)

In a previous job I was before we were pretty clear about our channels, and WE (3 people) were the Service Desk.

But after that I worked in a specific area of the IT of a multinational DIY stores chain and what a fucking mess.

[–] pruneaue@infosec.pub 4 points 7 months ago

Yeah im at a fairly small company with a boss that cares about that kinda stuff more than me so its not very hard to enforce

[–] Honytawk@lemmy.zip 3 points 7 months ago

Ah, the digital Neighbor to: You can stand by my desk but no ticket no help

Not going to let people cut in line in front of the people who do follow the procedures correctly.

[–] Ghostalmedia@lemmy.world 10 points 7 months ago

IMHO, you need to know how to admin a good slack workplace. Properly setup workflows, bots and plugins can proactively funnel a lot of people toward the correct intake and resolution systems. You also need to train people on best practices, and revisit that training so bad habits don’t set in.

Training + automation are kind of required to make any communication platform effective.

[–] tty5@lemmy.world 7 points 7 months ago* (last edited 7 months ago) (1 children)

"I am very busy and have my work day planned to work efficiently, so I won't be handling your request immediately. This means things can slip through cracks if there is no ticked describing the task created - create one if what you are asking for is of any importance."

Followed by not doing anything that doesn't have a ticket and didn't come directly from people you report to.

Also I have notifications disabled and only check slack between tasks or if I take a breather from a task - on average 4-5 times a day. I also check email as the first and last thing in a workday only

[–] XEAL@lemm.ee 3 points 7 months ago (1 children)

Yeah... in this DIY company I complained to my manager why other deparments didn't create a ticket for requests/incidents for us.

The response was because tickets would cost money to the deparments! What the actual fuck?

[–] Passerby6497@lemmy.world 1 points 7 months ago (1 children)

The response was because tickets would cost money to the deparments! What the actual fuck?

1, that's their problem, as well as whatever actual problem they have if there isn't a ticket. No ticky, no worky; no ticket, no problem.

2, that's ok, I'll create a ticket for the work I choose to do for them so they get appropriately charged.

[–] XEAL@lemm.ee 1 points 7 months ago

Yeah that would've probably got me in trouble in the best case...

I'm glad I'm not in that shit ass project anymore.

[–] theneverfox@pawb.social 7 points 7 months ago

Uhm... Have you considered that slack has cat picture plugins?

And meme plugins, and 30 other plugins that look for keywords then spam gifs for what you assume can only be an in joke before your time?

Oh, and one of the plugins actually creates tickets from chat, but jira is down and the guy who maintains it is busy writing a panda facts plug-in. So now it just vomits out an error message so everyone avoids the words "ticket", "issue", and "status"