Re: not a customer
Customers should just be patient and not get agitated.
Day 1, I agree completely. Day 6, we're running headlong into the end of the month.
Missed direct debits is one thing (I'll have a few between now and Monday, and I'd be miffed if they failed), but the bank can generally explain the problem to the recipient, handle the penalties etc. But what if I (not banking with TSB) were unable to get paid by my employer (hypothetically banking with TSB), and I am the one stung with penalties? Will TSB reimburse me?
Yes, it's a complex task. It's a huge task. And it needs huge planning, and regular checkpoints with back-out plans already in place. It seems that somebody skimped on the planning, and they committed to a course of action that didn't have a back-out plan ready to go.
I'm not saying I'm perfect. I've committed to system changes without a fast back-out that ended up biting me before, but we had a workaround already on the back burner before it happened, and were able to keep users running on that for the couple of weeks it took the devs to sort the latency issues with us. But this is beyond amateur hour. It's a bank. Not a small bank. They claim to have over 5 million customers. That means that a small disruption is a big issue.
Biting the hand that feeds IT
