I can't resist to point out that, in theory, there are at least two other options avoid wasting many resources via the failing new teams:

1. Get the original dev to explain his theories (keep employees longer or engage them as consultants) 2. Make and get a "diary" of the original devs theory building.

In this story, and in probably many places, the business environment however supports the explained outcome.