If you accept that technologists, by nature, gravitate to the best--and not necessarily the easiest--solutions (a process often called "
creeping elegance"), it is incumbent on project management to balance risk/cost with levels of complexity/performance.
* Two, set the transfer criteria's development process gate and enforce it brutally, avoiding
creeping elegance. People always want to make things better while they're in the development process, and what happens is your time to market is late--and most of your margin is in that first phase of getting to market, so delaying erodes that.
Without vigilance, newly available technologies and market pressures will encourage the product team to enhance the concept continually, resulting in "
creeping elegance." This destroys development schedules, because the team now finds itself aiming at a moving target.