506
this post was submitted on 07 Jun 2024
506 points (99.0% liked)
Technology
57455 readers
4913 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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
Internally people probably talked about how there were huge issues. Others probably said those issues are over stated and it's no big deal. They decided to release it and the press says there are issues. Then, the company decides there are issues. That simple.
Having been the guy in an org shouting not to do something only for it to come back to us this way, the finger-pointing that begins is nuts. Often the people who tried to stop the "feature" from rolling out are the first to get blamed for it being shit.
Classic CYA, make sure everything you said is in writing somewhere.
I have as well. I won't pretend I'm always right - I've thought some ideas that worked out incredibly were horrible. Also had the situation you describe happen. It's okay when you're working with reasonable people. Show them the slide deck, the email, the analysis, whatever... "Look you didn't approve this". "Here is an alternative ". That can work.
Just telling folks "I told you so" isn't usually a great form of communication.