You should try it once more with communication. I don' know how big your IT is, or how many are responsible to customize at the release strategies. If there are too many then it may have to be reduced to a few. We have people in 3 continents who are doing customizing. Nevertheless, there are just 2 (+ 2 backups) who are assigned to the task of release strategy, and they email to each other when they are going to do some customizing. Everyone is aware that it must not be transported if one has not finished. So you may need to organize your work in a kind of releases, and not just do adhoc transports.
If you cannot take such decisions and organize yourself then include your boss. I would certainly not open up the release strategy customizing to end-users (experience based on the "consultants" who post here the strategy questions every day)
Anything that is done directly in Production is often missing in Dev and QA, which means you have no reliable test data and need to find a way to get it to there. Further you have to restrict the customizing and transports otherwise you overwrite customizing which is done directly in production with incomplete development data. All in all more to do than establishing a good communication and transport strategy.