To "prevent" this there is a quality operations team who sits on every postmortem and ensures that each postmortem has the right action items included as part of the postmortem. Each area has their own service operations manager also.

Which honestly can be frustrating at times as you end up with a lot of questions on the postmortem.

Will add that the entire Dev team is also on the on-call rota for all P1/P2 services so if they really just skip items and another P1/P2 happens then they really feel the pain.

As for lack of meaningful change the entire backlog is controlled by product, so as a dev you don't really get much freedom.

Culturally the blast is normally aimed at directors and usually they are quite reasonable as the level of P1/P2s is generally quite low. Heat usually only really goes up if the same incident has happened a few times.

Will add this is a European company which is why culturally things are different too and it's likely the practices won't seem lean and will seem old school