I get the “notified teams, they did nothing” frustration, but I have seen how it can happen with low-maintenance features in departments with turnover. Team has one tech-minded person who sets up $feature, it fills a team need and gets embedded in business routines and just works, no one has any idea where it came from other than, for a while, $techieTeamMember had something to do with it. Techie person moves on in their career, other team has turnover and as a result team completely loses even vague tribal knowledge of where $feature comes from, or especially if it is embedded inside another user interface, what it is called. Now notifications of $feature breaking are completely meaningless to the team - they don’t associate any words in the email with the thing they use.
I get the “notified teams, they did nothing” frustration, but I have seen how it can happen with low-maintenance features in departments with turnover. Team has one tech-minded person who sets up $feature, it fills a team need and gets embedded in business routines and just works, no one has any idea where it came from other than, for a while, $techieTeamMember had something to do with it. Techie person moves on in their career, other team has turnover and as a result team completely loses even vague tribal knowledge of where $feature comes from, or especially if it is embedded inside another user interface, what it is called. Now notifications of $feature breaking are completely meaningless to the team - they don’t associate any words in the email with the thing they use.