[di456]

> But in my org, I know I won't get anything for reporting it

Are you empowered to fix it instead of just reporting it? How much effort to fix it? Sometimes the effort to do the fix is smaller than the work of selling the problem and jockeying for priority in the issue reporting process. Especially if going through those processes won't lead to anything meaningful getting done besides extra bureaucratic work.

Or if you have skip-level meetings with your manager's manager, get their opinion. Or even finance's opinion. It may be unclear how to reallocate that savings to other projects or budgets. Or if people are penalized for unplanned savings by having to over-explain it, there may be misaligned incentives that someone higher up might want to improve. For example if 10, 100, or however many other employees each find 50k savings that turns into real money quickly.

[to11mtm]

> Are you empowered to fix it instead of just reporting it? How much effort to fix it? Sometimes the effort to do the fix is smaller than the work of selling the problem and jockeying for priority in the issue reporting process. Especially if going through those processes won't lead to anything meaningful getting done besides extra bureaucratic work.

This has always been a warning sign for me; I've had cases where I was admonished for spotting a 1-line, very obvious bug (that either -would- happen, or was an as-yet-unfiled/unprioritized support request/ticket.) Never mind I'm already in that part of the code base and fixing/testing it would be trivial; The bug -must- be tracked separately, which means it must be prioritized and wait for proper resources to again be allocated before work can be done. These work places tend to be pretty toxic in other ways FWIW.