> a PM just needs to deploy the usual impossible UX trifecta: make it fast, make it easy, integrate all the different systems from other vendors. The problem h

> a PM just needs to deploy the usual impossible UX trifecta: make it fast, make it easy, integrate all the different systems from other vendors. The problem here is we're talking government software, or IT-as-a-cost-center software. So the buyer is looking at the cheapest bidder. They aren't getting a team like those who solved the UX trifecta in the past (looking at the iPhone team at Apple here). > Paper is fast. You can't make logins take 1 minute, they need to happen in milliseconds. You can't discard peoples progress when they move to a different workstation. Paper isn't fast, it's cached. Parsing, archiving and indexing of paper is extremely slow (when actually done). The slowness of input in a computer system might annoy the user but the system overall is way more efficient. Now auth taking more than a second or two is just lazy programming (bet it's not exactly Google caliber engineers working on the project). > the PM just has to say "no, this isn't acceptable", and find a team that can implement it well. The problem here is he'll have to 10x the budget.