Have you considered using an EventBus or something like that? What you have outlined is similar to an Observable/Observer pattern, except your pattern outline requires the class originating the event to be responsible for knowing which classes have subscribed to which events and then responsible for notifying each subscriber. A much more flexible design that is easier to modify and maintain would be to simply send the event to the event bus and let those classes interested in that event become aware of it and take the desired action.
I've just learned EventBus so am kind of high on it, and what you describe seems to be a great application for it. The EventBus examples and tutorials available on the web aren't great, but this is the simplest one
I could find that was easily understandable and scalable to my own examples. I have written my own study from that tutorial that I can share with you on request.