All this doesn't answer the question of why the major portal to Amtrak's entire income, their website, is allowed to fall into such disarray over such a long period of time. No ticket sales = no Amtrak.
Most of the time it works for most things, with a bunch of weird glitches. Some examples I've noticed recently:
- Unable to mix accommodation types on different trains on the "simplified" booking engine. No error message thrown, the "add" button just doesn't respond.
- Train status doesn't work for endpoint cities when using train number and city.
- Strange navigation choices, companion coupon added in "advanced search" not "discount"
- unable to enter companion coupon under Multi-city
There are doubtless other weirdnesses.
All of these have workarounds, but you have to poke around to find them (different accommodation types work fine in the Multi-City interface, train status for endpoints can be obtained by entering both stations, etc).
But all of it points to a combination of sloppy programming, insufficient QA, and poor UX design. Combined they indicate an IT shop in turmoil.
1. They lost what was probably drastically under-documented "tribal knowledge" of their antique core system, Arrow, due to early retirements, some probably forced or strongly encouraged. No modern dev worth their salt would want to touch it with a 10 foot pole. They could train up some non-devs internally on it, probably a years long process, but they lost that opportunity when they let/forced most of that knowledge out the door.
2. They decided to "simplify" the UX and make it more airline like, breaking edge functionality in the process (like mixed accommodations).
3. Some of the UX design decisions are mind boggling, like the coupon codes. It is clear that whoever was doing the design/Agile iterations did not understand actual use by a large subset of Amtrak customers.
They are in a world of hurt and would not even be able to effectively outsource to more competent entities because they pretty much appear to be incoherent. The only real solution would be hiring a competent and somewhat ruthless management team that is:
1. Laser-focused on customer experience for Amtrak's actual customers. This requires them understanding what that actually is.
2. Uninterested in current IT buzzwords and fads. This is virtually impossible as most upper IT management got where they are by riding buzzwords and fads.