This took off. Well I’ll throw in that a bug report is just a communication of a found problem to a developer, written or otherwise. If written bug reports have some special, magical element to them then that could be a process issue. If raising bugs through a tracker counts against my developers then I won’t raise them through the tracker, I’ll find another way. If the template doesn’t describe what I need it to I’ll use my own. If a developer doesn’t understand what I’m writing I’ll use videos, gifs, screenshots, audio recordings or whatever I need to to get myself across. Whatever I can do to get useful, responsible information into the right people’s hands. This is a negotiation with process, the amount of time and effort that it’s expected that I devote to nonsense versus my ability to do a great job. That is my personal responsibility to my clients and the company, despite my clients and the company.
If it’s not the process then it’s all about my relationship with my team, placing myself in service of their success and negotiating boundaries. Finding ways to be helpful to them, get them the right information, review my communications and find ways that suit them best. If I can’t get my found information into the hands of people who matter in a way that can help them make decisions then I’m wasting my time and theirs.
If I can’t make that work then it’s management’s time to manage because I have strict limits on the levels of bad work I’m willing to be forced to do. The levels of ego I have to manage in a team of experts, including mine, already maxes out my meter, and if they’re not interested in working with me to help them despite everything I try, offer, compromise and concede, then I’ve hit the walls of the scope of my interest in the problem and I defer to the experts in suits. Fix the teams or pay to run the silos without me, because the alternative is escalating every problem.
We need to take responsibility to offer the best to our teams, communicate effectively including listening to them, and building trust in our abilities and loyalties. We need to limit our responsibility when it comes to parenting or being a therapist for our team - I won’t take the food out of the mouths of line managers.
Edit: I also don’t understand the “is it a bug?” conversation. That’s pocket sand; a distraction, a deflection, a lie, whatever. It either is a problem to someone who matters or it isn’t. If it “technically” isn’t a bug then I’ll “technically” call it a value-disaster error defect problem issue. If we don’t want to fix it, that’s not my call; if it’s not actually a problem because I was mistaken then I’m happy to hear it; if you come at me with the 5th Edition Developers Handbook and try to rules lawyer my definitions, I can play that game better than you.