Timeline for Writing a report that may compromise someone else's job
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2014 at 1:37 | vote | accept | ApplePie | ||
| Jul 31, 2014 at 13:37 | comment | added | Kevin | @aroth That actually makes a great answer! | |
| Jul 31, 2014 at 13:09 | answer | added | Roger | timeline score: -1 | |
| Jul 31, 2014 at 12:34 | comment | added | David K | Could you edit this with some fake names, or Colleague A, B, C? I'm having some confusion with who is generating, reviewing, and who's job would be at risk. | |
| Jul 31, 2014 at 9:57 | history | tweeted | twitter.com/#!/StackWorkplace/status/494783831061565440 | ||
| Jul 31, 2014 at 6:27 | comment | added | amar | Be objective a do your job your colleague might get fired and buy a lottery ticket and win millions ...thing is your are responcible for honest discharge of your duties .. | |
| Jul 31, 2014 at 3:29 | answer | added | Vietnhi Phuvan | timeline score: 10 | |
| Jul 31, 2014 at 1:13 | comment | added | aroth | It seems like the inverse hypothesis is equally possible. If these reports account for just a few days of the colleague's time each month, he must have other tasks he works on the rest of the time. By no longer having to run the reports himself, he'd have more time for his other tasks, which may cause his performance to improve. Especially if running the reports primarily involves tedious, repetitive, demoralizing manual drudgery. Have you considered asking the colleague if he'd be happier if he didn't have to run those reports any longer? | |
| Jul 31, 2014 at 0:54 | history | asked | ApplePie | CC BY-SA 3.0 |