Shiny New Toy Syndrome: Crippling your Web presence?

Is your Web presence hobbled by Shiny New Toy Syndrome?

Used to be that the CEO was most prone to Shiny New Toy Syndrome. (Actual quote from a major media boardroom: "ESPN's doing it... it must be working for them... why can't do that too?"). We tech types breathed a sigh of relief when Chief Technology Officers became commonplace, since the CTO is supposed to disabuse the CEO of the dancing sugarplums that usually surround Shiny New Toy.

Turns out CTOs are just as - if not more - susceptible to Shiny New Toy Syndrome (SNTS). Especially when pushed in a flashy new demo from an 800-pound-gorilla vendor. Why does this happen?

Vendor schmoozing aside, this happens because the company has not established requirements. Sure, the toy is shiny, but: Does it meet your requirements? Does it duplicate the functionality of an existing, better-developed tool? Will it create ROI, or will it add a maintenance burden that you didn't plan to meet? Or is this yet another instance of the technologist's worst nightmare: Wishful thinking?

Major American businesses, associations, and scientific projects are losing time, money, and opportunity to SNTS. We see it on far too many projects. The cure: The creation of objective requirements - based on a coherent Web strategy - that set a standard for selection and implementation of technologies.

Play is clearly more fun than work. But CTOs are paid big salaries to make responsible decisions that affect the livelihoods of hundreds of people - not to mention the company's brand.

Toys are for kids.