My advice: have a maturity standard for services. Ensure they meet a certain standard before they are handed off to the SRE team. Until the service meets maturity standards to qualify for full SRE support, the team that engineered the service is frontline support. If the service maturity regresses, primary support reverts.
This shares the burden of the interrupt work. It's still interrupt work, and it still slows down someone's velocity, but because it punishes the service designers for their poor design decisions, those get better over time and the overall quantity of bugs goes down, not up.
Here is our yardstick: https://gitlab.com/dreamer-labs/tsc/service-maturity-model
This shares the burden of the interrupt work. It's still interrupt work, and it still slows down someone's velocity, but because it punishes the service designers for their poor design decisions, those get better over time and the overall quantity of bugs goes down, not up.