I think you let them off too easily by just assuming they're dumb. This a bad decision by people who definitely should have known better.
I think you let them off too easily by just assuming they're dumb. This a bad decision by people who definitely should have known better.
In the old days when the relevant business application was written, hosted and supported in house there was a clear chain of responsibility I could pick up the phone and I'd have a direct line to the person who "owned" the application.
Nowadays if there is a problem it's pick up the phone talk to helpdesk get assigned a ticket number and get the buck passed between different teams, The database team will blame the server team, server team will blame the networking team, networking team will reply to ticket with 'looks ok no problem on my end' and the ticket will get closed without resolution.
From what I can tell there are a bunch of incentives in the support contract around how quickly support can close out tickets, so rather than trying to fix the problem support try to do everything they can to farm the ticket off to someone else so it won't impact their metrics. The whole thing feels maddening and has to be rather inefficient.
I assure you that you're wrong. The SaaS I work for replaces a suite of independently re-invented Excel files used in conjunction with other SaaS. NHS trusts are our main customers, I can only assume the NHS is full of excel spreadsheets.
(Technically speaking PHE is not part of the NHS, it has more in common with the civil service in some ways.)