Timeline for What if a boss requires supervision?
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2017 at 11:13 | vote | accept | Pilling Fine | ||
| Jun 30, 2016 at 15:24 | comment | added | kat0r | @AmyBlankenship It does help a lot when you live in a jurisdiction where HR/your boss has to justify your dismissal in front of a judge. Not so much in the US. | |
| S Jun 28, 2016 at 22:38 | history | suggested | Pilling Fine | CC BY-SA 3.0 |
Changed You're to Your as requested by a commenter
|
| Jun 28, 2016 at 22:37 | comment | added | Pilling Fine | @blankip Also just by this, "spending company time documenting vs completing project work", for any future jobs I take I will make documentation a prerequisite to my work and taking that job. I have since realized that any manager that does not request me to do this is likely going to instructively change their decisions (without explanation), misrepresent you, and overwork you. The last company I worked in before this, documenting was more important than work, and it is the leading / dominating company in three major web applications in my country. | |
| Jun 28, 2016 at 21:47 | comment | added | gnasher729 | But then if you make moronic decisions that means you both stupid and you are not listening to what people tell you, so it's unlikely you would find out what they are doing. | |
| Jun 28, 2016 at 21:23 | review | Suggested edits | |||
| S Jun 28, 2016 at 22:38 | |||||
| Jun 28, 2016 at 17:38 | comment | added | blankip | I will mention this. If I was running a project - and I run many - and I found out that someone was documenting me because they thought I make moron decisions or to cover their ass - and spending company time documenting vs completing project work - this person might as well start interviewing elsewhere. I probably won't fire them as long as they are competent but they will also never see a promotion. | |
| Jun 28, 2016 at 16:31 | comment | added | brian_o | The examples of workplaces where where documentation turns out to be "useful" sound like miserable places to work. | |
| Jun 28, 2016 at 15:47 | comment | added | Pimgd | "You're major concern" -> Your major concern | |
| Jun 28, 2016 at 15:27 | comment | added | Pilling Fine | @AmyBlankenship It especially works when whoever you have to dispute is at the same level with you, but may be more trusted because of experience and time in the organisation. When the person is at a higher level than you, it might work when the rest of the organisation is skeptical of the manager (you may not know already), but will not publicly tell it, but when you bring your well documented case, they know when its the manager's history playing up and let you off the hook, possibly advising you how to deal with the manager. Again, it's not about putting the manager in the fire. | |
| Jun 28, 2016 at 15:21 | comment | added | Amy Blankenship | Having a record of suing previous employers isn't great for your career. And it wouldn't apply in this situation anyway. | |
| Jun 28, 2016 at 15:20 | comment | added | Kilisi | @AmyBlankenship when big clients are involved it makes all the difference, and in the situation Richard pointed out. In my case it was a big client, they would have lost half their business in one shot. | |
| Jun 28, 2016 at 15:14 | comment | added | Old_Lamplighter | @AmyBlankenship oh, it does wonders when HR turns bone-white when they see you've got the makings of a lawsuit. | |
| Jun 28, 2016 at 15:12 | comment | added | Amy Blankenship | I've never had a situation where anyone cared what the facts were :). They had already decided, and that was that. | |
| Jun 28, 2016 at 15:08 | comment | added | Kilisi | @AmyBlankenship You can be arbitrarily marched out for any reason whatsoever, documentation is useful when there is a dispute over facts, and yes, it has worked for me more than once, mostly in terms of disputes with clients, but in one case it got me paid off very well and given a chance to resign with an excellent reference rather than be sacked. They couldn't sack the manager because he was family. | |
| Jun 28, 2016 at 14:57 | comment | added | Amy Blankenship | Is there ever a situation where having the documentation does squat? When you get called in to HR and they are ready to walk you out of the building, does it ever save anyone's job to have proof you were asked to do all the things you got blamed for? | |
| Jun 28, 2016 at 14:56 | comment | added | Pilling Fine | @blankip Thanks for the first point about not being too "intent" on documenting for spite, i believe that's what you mean. However, in what way did you see problems, perhaps you can elaborate these in an answer? | |
| Jun 28, 2016 at 14:54 | comment | added | Pilling Fine | @RichardU, thank you for the bit about documenting good work too. | |
| Jun 28, 2016 at 13:57 | comment | added | blankip | Of course document but don't do so in a way that makes it seem like you are trying to take him down with evidence. I saw really no "issues" with the management in the question, and more with the OP. Your last paragraph I completely agree with, especially for this guy. | |
| Jun 28, 2016 at 13:17 | comment | added | Old_Lamplighter | @PillingFine Always look out for #1, and be careful not to step in #2. I might add, also document when things go right, or when you catch something BEFORE it becomes a problem, otherwise they will never know. I got on one of my reports for NOT doing that. "Oh, it was no big deal, I fixed it before the systems even hiccupped". I told him to go back and add that to his report or nobody would ever know he saved the company from a mess. document the good, the bad, the ugly the significant and the insignificant. | |
| Jun 28, 2016 at 12:58 | comment | added | Pilling Fine | Thank you! This is good advice, and i don't want to be the "escalator", it is a huge burden indeed over the life of your career at a workplace. Always comes to bite you when people perceive you to do a bad job yourself later on. Thank you for reminding me "my role", i should remember this. Every time i think of successfully delivering projects even as a team member, i try to participate as a team partner who raises problems we may face as a team even if i may not be responsible for the problem later. I will remember this, to document where i might have felt otherwise, but still execute my duty | |
| Jun 28, 2016 at 12:08 | comment | added | Old_Lamplighter | +1 Document, document, and then document some more. You are also correct about not wanting to get the reputation as an "escalator". That never goes away. | |
| Jun 28, 2016 at 11:50 | history | answered | Kilisi | CC BY-SA 3.0 |