Is PM not consulted for changes like this? I feel like this is something that a competent PM would ask eng to pause on while they determined actual user impact and lines up messaging.
In the scenario I described above (again, it's a guess, I don't know what actually happened), it's possible that the PM was bypassed because the engineers for a reason they thought was good. For example:
* they didn't even think about involving a PM because that's something you have never done,
* the people who wrote/reviewed the change assumed the conversation already happened,
* they were pressured to move fast to mitigate an imminent or existing problem (performance, scalability, ...),
* the PM who should have made this call "left" the company and didn't (get a chance to) hand-off their responsibilities.
I guess what I mean with these comments is that sometimes there are misses like this. Maybe it's a sign of a systematic failure and that internal processes should be improved, but I don't think it means that the company is fundamentally unable to handle these changes correctly or can't make the right technical or product decisions.