I was recently asked to update some test results and found the documents which were basis for those tests removed from our production system (but luckily still tucked away in a test system which mirrored production a couple of months ago). I’ve recently had some issues with the system administrator who is asking for these updates and I am a bit concerned that I could be being set up as these were in a controlled documentation system so there is no way they should be able to disappear.

In my mind best case and most likely scenario is this is a one of a kind glitch of some sort however I would like to cover myself in case it is not.

Is it okay to go to my manager in a situation like this and say “It’s probably nothing but…” or does that put me in a bad light?

  • 12
    "In a controlled documentation system ..." - File a trouble ticket with the system admin about the missing files, cc your manager. Leave the emotional stuff out. The DMS didn't work like it was supposed to, so file a trouble ticket. – Wesley Long Mar 13 '15 at 17:10
  • 9
    If you simply state to your manager that the files disappeared and that you don't have a clue how they vanished is one thing. Stating that the files disappeared and elaborating on your finding by sharing your suspicions and your speculations without evidence to back them up - that's another thing. – Vietnhi Phuvan Mar 13 '15 at 17:40
  • 1
    Emailed the boss with everything that is concrete (existed as per still being in test system+screenshot including creation date earlier than mirroring date, do not exist now, will look into it). – Myles Mar 13 '15 at 18:30
  • 18
    I had a supervisor that wanted a contractor fired so she logged on the contractor ID and changed some data and then used that as evidence to fire the contractor. I pulled the backup and coincidentally every one of the records was correct on the backup and the change time on the production was after the contractor clocked out. It was fun to watch supervisor get fired when she thought she was going into a meeting to fire the contractor. – paparazzo Mar 13 '15 at 18:55
  • 6
    @Blam - I would have paid (and still would) good money for a video recording of that. – Wesley Long Mar 13 '15 at 21:22

Never attribute to malice that which is adequately explained by stupidity. - Hanlon's Razor

This saying is pretty useful for a couple of reasons in office politics.

First, unlike some other arenas, accusations in Office situations often make the accuser look worse than the accused. Perhaps especially if there is no data or proof and, let's face it, even if there were trusting the SysAdmin who is accused to find that proof for you is pretty unrealistic.

Additionally there's this feeling when you accuse someone of something that can be explained in other ways. It's pretty hard to pin down in words but it comes down to the idea that the person who accuses others of making them look bad is defensive for a reason. It's a weird kind of victim blaming now that I reflect on it. If I say that Myles "is trying to make me look bad by deleting my work!" the reality is that the first thought for a lot of folks is "What is Ananci doing wrong that someone would want to make her feel bad?"

About the only differences between an episode of Game of Thrones and typical office politics is the amount of nudity and the number of dead bodies at the end of the fiscal year. It doesn't have to be like this. But once you get to the point that you are suspicious that someone is explicitly doing things intentionally in order to damage your career - this is what it is.

All that aside what should you do about it?

Kill them with kindness and appropriate actions.

What does this really mean?

Don't ever acknowledge that you think Soandso is working against you. As far as you know, and you could only know so much not being their supervisor, they're doing their job to the best of their ability. If things are not done correctly then, surely, it was just a mistake or a process failure.

Your responsibility in this is to follow the best practice as laid down by your job. If you came across missing production documentation and you didn't suspect this Sysadmin of wrong doing, what would you do? Ideally you would open a ticket or in someway report the issue. It's not your job to speculate why or how it happened unless all the systems involved are under your control(or you are in a supervisory position). Why? Because you have no information about it beyond what you know (which is that the documentation is missing.)

Ultimately the best way to handle this sort of situation is to do your job and follow the expectations set by your company's processes. If you notice oddness, report it regardless of whether or not it is suspicious to you. Report dispassionately and only offer information that is pertinent and provable (for example how you discovered the missing data, the process you used to access it, the systems you accessed.)

  • 3
    "... is the amount of nudity and the number of dead bodies at the end of the fiscal year. " - You obviously don't work in television. (Or politics.) – Wesley Long Mar 13 '15 at 21:26
  • 2
    Perhaps I should amend that to 'found dead bodies' – Nahkki Mar 13 '15 at 21:27

Is it okay to go to my manager in a situation like this and say "It's probably nothing but..." or does that put me in a bad light?

Not only is it okay, but it's extremely important to do so immediately, particularly if you suspect something nefarious is going on.

Cover yourself right away by bringing this to your manager's attention. It's probably nothing, but if you feel "set up" you want to make sure you don't get the blame for whatever happened.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .