this post was submitted on 09 Mar 2024
395 points (96.5% liked)
memes
10393 readers
1823 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In my experience, it's usually badly cut processes that lead to this sort of thing. I would bet money that one team is responsible for the infrastructure to send out those messages with that title and another team generates the message texts.
And so, even though it would normally take just a minute to fix that title string, suddenly it requires cross-team communication, potentially even across different organization units or companies. If you don't know one of the engineers on the other team and can write to them directly, there's basically no chance to get a soft issue like that communicated.
Agreed, which is normally why UX teams tend to “float” at many enterprises because there are so many moving parts that they are just like “can we make this message better” and then a product manager has to figure out how many engineering teams need to get involved to change an email message lol