Yesterday, I was testing engineering rules written by Miss MBA. Five team members had reviewed the document a few weeks ago and suggested changes which were incorporated into the final draft. While testing the engineering rules I noticed that a period was missing at the end of a sentence and “upto” was used instead of “up to”. Miss MBA had a meltdown and wanted to know why these items were not found during the review. She blamed me even though four other people reviewed the document and the developer didn’t bring up the issue when the code was written. I pointed out that the focus should be on the fact that the issues were found before the code was released to production. Miss MBA didn’t like this. She continued to blame me in a series of emails. Thankfully, I stopped myself before I asked her if she knew how to check spelling and grammar when she authors a document. No other team members responded to her emails. It was as if they were all ducking for cover. I was left alone to incur her wrath.
Miss MBA shouldn’t be blaming me for her inadequate writing skills. Also, four other associates reviewed the document. Why was she putting the focus on me? Why was she so upset about two simple corrections that will only take seconds to correct in the code. Clearly, there must be something else bothering her and she’s taking it out on me.
Today, two of the other associates who reviewed the document contacted me to express their support. They thought Miss MBA was out of line. They don’t understand why Miss MBA blamed me when she wrote the document. I took the high road and told my peers it was my turn to take one for team. It’s best to move on and put it behind us.
The Corporate Slave 