A support-escalation manager pages the on-call Developer at 9pm asking them to move a specific bug fix to the very top of the Product Backlog immediately, without contacting the Product Owner, because a customer is upset on social media. The Developer complies overnight. What should happen the next morning?

Even a genuinely urgent situation doesn't change who is accountable for the Product Backlog's order — it changes how quickly that person needs to be looped in. Letting the overnight change simply stand treats an ad hoc, after-hours decision as equivalent to the Product Owner's considered judgment, which it isn't; the social-media pressure might be exactly right to prioritize, or it might be one loud customer while a quieter but more serious certification issue sits ignored, and only the Product Owner has the full picture to tell the difference. Permanently handing backlog authority to the Scrum Master during incidents misreads that role too — the Scrum Master supports the Product Owner and helps the organization understand Scrum, but doesn't inherit backlog accountability just because an incident happened outside business hours. Making the support-escalation manager a second Product Owner for urgent cases recreates the committee problem: Scrum keeps this to one accountable person specifically so there isn't a parallel authority that can override the backlog under pressure. The healthy pattern is fast escalation to the Product Owner, with the Developers' overnight action treated as provisional until confirmed. A concrete check: did the Product Owner see and explicitly ratify the change the next day, or is it just quietly staying where the Developer put it?