Timeline for My boss doesn't want me to say I performed tasks I'm not qualified to
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2023 at 23:15 | comment | added | Flater | @PiotrGolacki I'm not trying to burn OP down for making a mistake. I'm addressing the root of their question to point out that OP did in fact make a mistake and overstep, as opposed to OP's current interpretation of their boss asking for an unreasonable and unjustified action (i.e. OP allegedly not being allowed to talk about the project they worked on). I cannot judge whether the company had suggested OP to not mention this, whether they implicitly expected that to be obvious, or whether OP potentially ignored an early suggestion - which is why I'm not focusing on that part. | |
| Apr 4, 2023 at 20:08 | comment | added | Piotr Golacki | Aren't you going too hard, they're just an intern. Anyone with little professional experience could make this mistake. If anything that's the management's fault not to brief an intern before the meeting. Usually managers or senor staff would do majority of talking | |
| Apr 4, 2023 at 1:52 | history | edited | Flater | CC BY-SA 4.0 |
added 369 characters in body
|
| Apr 3, 2023 at 4:09 | comment | added | Flater | @Amelian: Your second comment suggests that you don't see any difference between an internal discussion and an external one. There is a massive difference in terms of how you are expected to speak and what is considered okay to divulge. I suspect this is why you're not understanding why there's pushback now that you've brought this up with people external to the company. I don't think you intended any harm or were willfully reckless, but you said the wrong thing in the wrong forum. Just to be clear, what you said was not incorrect, but it was wrong to bring it up in that environment. | |
| Apr 3, 2023 at 2:23 | comment | added | keshlam | Bringing it up in an external meeting, without first clearing that with management, will always be taken as putting the company in a bad light. Context matters. Keep internal disagreements internal. | |
| Apr 3, 2023 at 2:10 | comment | added | Amelian | I stated those kind of arguments with my teamwork before and they had no problem with that. NOW they seem to be a problem, and that's what is worrying me. | |
| Apr 3, 2023 at 2:10 | comment | added | Amelian | Thank you very much for your long answer. I just want to say that, of course, I took my precautions to not put anyone in a bad light, but it wasn't enough. During the meeting I made sure to state the good things about the project, highlighting the good metrics I got and even doing a live presentation with a random input from internet. I wanted to make clear that, with the opinion of a professional, the theory taken into account could be extended and tuned, making the model (which, at this stage, proves to be good) more reliable and useful. | |
| Apr 3, 2023 at 2:03 | history | edited | Flater | CC BY-SA 4.0 |
added 54 characters in body
|
| Apr 2, 2023 at 23:58 | history | edited | Flater | CC BY-SA 4.0 |
added 130 characters in body
|
| Apr 2, 2023 at 23:42 | history | answered | Flater | CC BY-SA 4.0 |