Timeline for How do you explain to your boss they're wrong without making them feel threatened?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2016 at 18:46 | history | edited | Codeman | CC BY-SA 3.0 |
added 2 characters in body
|
| Jun 5, 2013 at 23:45 | comment | added | Codeman | @KeithS yes, but an easy way to reduce the risk of this is to get one or more other machines to fail to replicate the issue. If the manager is an asshole who refuses to accept responsibility, you can't do a lot about that. This is the best solution to a tough communication problem. | |
| Jun 5, 2013 at 21:39 | comment | added | KeithS | The problem with this is that you look like you're falling into the "works on my machine" trap. He sees the incorrect behavior in the software, so it's very easy to think that it's obviously a problem with the software that must be fixed; your inability to reliably reproduce it thus just means you didn't try hard enough. I see it all the time with "end users" in management positions that, at some point in their career, had Visual Studio installed on their work computer and therefore "used to be developers". | |
| Jun 5, 2013 at 18:48 | history | made wiki | Post Made Community Wiki by Sarel Botha | ||
| Jun 4, 2013 at 23:32 | vote | accept | DistantEcho | ||
| Jun 4, 2013 at 20:25 | comment | added | Codeman | @Niphra perhaps you could ask the boss to show you himself if you're unable to do it? The trick is to put as much responsibility for showing the bug in his hands, without accusing him of being wrong. | |
| Jun 4, 2013 at 20:18 | comment | added | DistantEcho | This sounds like a reasonable approach, and I actually opened the conversation with something like that, but "I was unable to replicate" started the whole argument. | |
| Jun 4, 2013 at 18:31 | history | answered | Codeman | CC BY-SA 3.0 |