trying to find an example of this, it\'s possible that I am not going the right way around it, or that my mind has over simplified the concept of the observer pattern.
I
I subscribe to the idea that 1 class performs 1 core task. If it were me, I would build an observer interface, create multiple observer implementations, and manage all of those observers with some ObserverManager class.
Doing it this way will separate all of your business concerns, and will afford a finer level of granularity for testing.
Unless the "changes of many other operations" can be typified as the same kind of observable "change." At that point the the single observer makes sense.