I've just finished reading part 1 of an article, "Considering Ajax", by Chris Laffra from IBM and it made me consider what the role of engineering in business is outside of just development.
The underlying technology of AJAX has been around for a while, but what's interesting is the amount of buzz surrounding it now. The danger with this sort of buzz is both engineers and business people alike can get caught up in it and make decisions based on the hype, instead of what is the right solution to a clients problem.
As Chris puts it
When you make decisions, one strong cognitive bias is the bandwagon effect, a well-known psychological phenomenon.
Don't get me wrong, there are still plenty of good business reasons to do something even if it's a "bandwagon" idea, for example to get press interest or attract VC. But the real challenge is to overcome the "bandwagon" impulse of a new technology and identify what technical benefits are to be gained by using it.
As I see it, part of the role of engineering is to cut through the hype surrounding a technology, understand what the pros and cons are of it, identify how it can best be utilised to solve a problem and provide an unbiased recommendation of it's potential use in the business.
Of course, engineers aren't immune to hype either, so part of the role of the engineering manager is to remind everyone that the technology is just a tool and ask the questions "what are the real problems with using it?" and "how and where could we use it?".