As a UXer, it's our job to spread the "doctrine" that UX should be something that should be on everyone's mind as oppose to it being something that dealt with solely by the UXer.
As a product designer for a complex application, I found myself frequently running into this situation where new staff will bring up usability issues to me. We would discuss it and I agree with them that this is something that ought to be addressed. However, because the software is old, there are a lot of UX issues. Majority (90%) of these items never get fixed because there's more critical issues that need to be dealt with first.
Over time, the staff may start to feel that because nothing comes out of these chats, their input isn't valued. So they stop thinking about UX and no longer come to chat.
This is especially problematic because some staff like Support are in constant contact with users whereas we on Product only occasionally talk to users during testing and the occasional persona interviews. So the minority of the issues they hear about that are of the "product killer" category we, Product, might not even be aware of until they bring it up.
Question: What approach can we take to let people know that because of resource constraints, only large usability issue will be worked on, while still encouraging everyone to talk to us about UX?