There is definitely a corporate problem (or many) here. At least the manager deciding that "this needs to be looked into right now" above edw's opinion, and the

There is definitely a corporate problem (or many) here. At least the manager deciding that "this needs to be looked into right now" above edw's opinion, and the idea that the whole conf call + webconf dance was a better move than filing a ticket. > Why is a developer sitting on that particular conference call? Doesn't the company have a QA department, or an internal support department that documents the issue and provides steps to replicate? Exactly. How should one fight that these steps be taken, when your manager is trying to skip them? The thought process that I expect led to this situation were similar to "I could file a ticket, which will take me 5 minutes, or if I just show it to someone, it'll only take me 3 [not voiced: if nothing goes wrong.] That's working smarter!" Similarily, how do you convey to people the true cost of asking for something like this, instead of them treating everybody else's time and effort as externalities. Yes, there are signs of a sick culture. Culture is fluid though, so how does one push it back towards health? Preferrably without getting classed as difficult/rude/not-a-team-player and then having any argument you bring ignored.