• BrowseMan@sh.itjust.works
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    2 days ago

    That’s only if people read the info in the actual email.

    “-Could you just explain what this meeting is about”

    “-Did you actually read the email summary”

    “-yes but it’d be better if you explain it again”

    No you didn’t…

    • wizardbeard@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      Oh my god. Spend time making shit clear and concise, send the email to the manager. No response. Multiple other teams already responded to the initial email and moving smoothly.

      Send a short follow up a week later with the rest of the team cc’d. Manager responds to the initial email, dropping the “hey fuckface, do your job” email from the chain.

      “Please schedule a meeting with my team to discuss.” (Literal words. Nothing the fuck else.)

      (Putting the dropped email and the full team back in) “According to calendars, your team is not available as a full group for two weeks. Given the tight deadline on this, if you or your team have any specific questions, I’d be happy to discuss over email.”

      Nothing for two weeks, in the meeting it’s clear that none of them even attempted to read any of it.

        • wizardbeard@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          2 days ago

          It gets better. Both in the “PTSD” and they got what’s coming to them sense. Some additional context: This was a switchover from one system to another.

          They agreed to a specific special solution that my team would set up for them, different from our standard switchover for everyone else. We just needed some incredibly basic info from them that any member of that team should have been able to provide in 30 seconds.

          They got the info to us two days before the deadline.

          So, some stuff happened and while we had everything switched over to the new system, we didn’t actually shut down the old system for a few more weeks past the deadline we had shared. Before we shut it down I did a final scan and notified any person/team that still appeared to be using it. These problem children were, because of course they would.

          Sent them the “Hey guys, you didn’t turn off your old shit pointing to the old system when you were supposed to. You’ll need to find an alternate solution now” email on a Monday. One member of their team puts in a ticket about something only tangentially related, but definitely caused by the old system shutdown, not working on Wednesday. It doesn’t reach me personally due to lack of any useful details, instead just sitting in my team’s generic queue.

          That Friday, 30 fucking minutes before we close for the week, I get a response from the next manager up the chain from the one that played games with this shit earlier. Clearly the shitty manager is trying to play politics now by bringing in his own manager, who hadn’t been in the chain. “Thanks for letting us know, we’ve been trying to troubleshoot this all week! How do we resolve this?”

          So, their team ignored my email. Still didn’t understand anything from any of the previous emails in the chain or else they wouldn’t have had anything to waste time failing to troubleshoot. You tried to send data to a system/server that no longer exists. Then this power play right before closing in what I think was an attempt to be able to blame me for being a week behind on something.

          “You would need to follow the instructions I’ve attached from my first email about this sent to [shitty manager] on [over a month ago]. Please let me know if you jave any questions!”

          Last I heard from them. Hooray!