I've seen countless failures like this. I was able to stop a couple before they collided with harsh reality. It never got me any friends in upper management, but saved a couple companies.
If your success had made a big story, it would have become a case study. It becomes intellectually insulting to them.
It directly means they are not capable of doing their jobs properly.
One fact every one need to realize, It's great to be young. But age is not static. Those who are young today have a very narrow window of 9-10 years. Beyond that we are all the same.
The Asian locales had no old system to fall back on, so when Plan A didn't ship and I revealed my (fully localized) Plan B, they adopted it immediately. If I hadn't done my Plan B, the Asians would have had to go back to product registration by postcard.
My experience indicated that they were planning to use too many "new things" simultaneously. If any one beta-level technology failed, the whole project would fail. My Plan B was to essentially solve the main problem it was meant to solve with a minimal core built with tools we knew would work. Put that online on time, then incrementally upgrade features using the new technologies.
Since my group would need some of the services of this software project, I went off and built part of Plan B myself (the part covering what our group would need) as a secret side project using old fuddy-duddy technologies that worked but weren't new, exciting, and unknown. When the 90-day project wasn't ready on Day 90, I put my own online. It worked perfectly. This VP and her minions were angry about it. "It demonstrated a lack of faith in her team."
Two YEARS later, their 90-day Plan A finally shipped. She and the CIO never forgave me, though. I, the old guy, had used 80/20 to deliver the core of what was needed on the day they said it was needed, and I did it alone. Still, they remained convinced that "young, hungry" engineers were more likely to "be on board" with projects like the one they designed, and that was what mattered.