I see that, as usually happens, the politics of website redesigns have prevented the simple, user-centric fix of "go back to the old site which worked fine." Li

I see that, as usually happens, the politics of website redesigns have prevented the simple, user-centric fix of "go back to the old site which worked fine." Like any other deployment, redesigns should have a rollback plan. If you installed a major system update and suddenly production throughput drops in half, you'd roll back to the old version. If you deploy a new design and your traffic falls in half.. why is there so much resistance to just rolling back to the old version? I understand in cases where it's a big switchover and basically a redesign riding the coattails of a huge middleware/backend rewrite. I don't understand in a case like this when it wouldn't break major back office processes to just put the old site back.