Follow along as we read the lawsuit's details...
A phased approach, slowly changing over parts of the customer experience and getting feedback as they went.
Start with the simplest transactions, and for users not doing those, just send them to the (still live) old system.
1. I'm VERY interested to know how the front end code created (a) security and (b) performance problems. cc @slightlylate
2. "FED code" = the front end. That's a new one for me! (Please do not re-use this phrase, very potentially confusing.)
As a reminder, these are all claims made by Hertz in a lawsuit, and neither I nor anyone else not involved in the project can make any statements as to their validity.
But in a world where there are so many big failed IT projects, reading such lawsuits is useful.
1. Build (don't buy) digital capabilities if you can
2. If not, at least build a product ownership capability
3. Insist on phased delivery: really-deployed websites used by real end users
Govt just happens to be at scale and long-lived.
This does help us understand this better, though. It means there's something in the incentives or mental models of C-level leadership here that is at the root, rather than ignorance of options.
As a systems problem, it's quite interesting!