Timeline for How can I deal with a colleague who edits previous email details to paint colleagues in a negative light?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2021 at 9:51 | comment | added | Grimm The Opiner | I love the idea of approaching this with (apparent) maximum good faith to the sender, and leaving it to the uninvolved 3rd party tech types to point out the actual story. | |
| Aug 9, 2021 at 9:25 | comment | added | ProgrammingLlama | And if the sender did actually send the e-mail but you just didn't get it, then maybe IT will find out why and fix it, and then you haven't accused your Canadian colleague of something they didn't do. | |
| Aug 9, 2021 at 9:24 | comment | added | ProgrammingLlama | @KamiKaze I also thought to involve IT for the simple reason: feign naivety. As the complainant you aren't trying to get anyone into trouble. You're simply asking IT why important e-mails from your Canadian colleague aren't reaching you, and you're simply CCing the relevant managers to ensure IT looks into it properly. Then when It turns around and alerts you to the fact that you simply weren't included in the email, you can ask them to double check (still CC-ing managers) as the subsequent e-mail shows you were in the To list. Thereby not overtly ruffling feathers. | |
| Aug 9, 2021 at 9:08 | comment | added | Kami Kaze | Why add a third pary? The original sender has the original data, so he can clear this up. | |
| Aug 8, 2021 at 7:37 | comment | added | GoodSp33d | This is such a good response ! | |
| Aug 7, 2021 at 12:59 | comment | added | Daniel R. Collins | @Moo: Fascinating. I truly wish we had people like you on staff any place I'd ever worked at. OP at least needs to consider whether this is reasonable at their workplace -- any place I've worked, I would almost surely expect an incoherent reply, and doubtful that they even understood the words used in this answer (nor such things as "HTML" or "attached file"). | |
| Aug 7, 2021 at 6:11 | comment | added | Kevin | Yes, make it IT's problem. Don't start a fight over who forged this or who forwarded that. If someone is unreasonable enough to forge a To header, arguing with them is unlikely to accomplish much of anything. | |
| Aug 7, 2021 at 2:58 | comment | added | Joshua | This is what we want. I recall when I was called to the CEO's office for ignoring a direct order in an email for 5 hours. The conversation lasted about 30 seconds because I had received the CEO's email only five minutes before I was called into the office and was just beginning to react to it and said as much. It won't go as quickly here but this should be the path. I would expect to defeat the complaint even if it was sent to the team but not in my inbox, and so should you. This is more easily verified than the email stuck five hours on the server. | |
| Aug 7, 2021 at 2:37 | comment | added | user34687 | @DanielR.Collins I did it a lot in my days running IT infrastructure - audit trails are wonderful things to pull out in disputes. On one occasion I even went to the effort of pulling archived backups to prove something happened on a given date. | |
| Aug 6, 2021 at 20:16 | comment | added | Daniel R. Collins | Have you ever had IT clearly and competently resolve an issue like this? (I haven't.) | |
| Aug 6, 2021 at 13:51 | comment | added | Solar Mike | Getting IT to show the original provenance is the best path to take. 3rd party confirmation as long as it is not in the Canadian managers pocket... | |
| Aug 6, 2021 at 13:16 | history | answered | sf02 | CC BY-SA 4.0 |