+1 the point of on call was to wake up the team who caused the problem in the first place, and presumably have the ability to fix it via code changes etc. This

+1 the point of on call was to wake up the team who caused the problem in the first place, and presumably have the ability to fix it via code changes etc. This is in contrast to the model where there's a team that fields issues and tries their best to fix them, but ultimately has to put fix-it tickets to the software owners. The on call rotations I've seen end up being a hybrid where you get the worst of both worlds. The team has enough responsibilities that no one person on the team knows how to handle everything and are so inundated with pages that it just becomes accepted that one person from the team every X weeks is going to be nothing but keeping the service from burning down.