Manage Learn to apply best practices and optimize your operations.

Top CIOs reveal their biggest information technology issues


The rate of technology change

Source:  TechTarget

When SearchCIO asked Stephen Neff, CTO at Fidelity Investments, what obstacles hinder IT processes and innovation at his organization, he promptly answered, "velocity of change."

This issue isn't specific to Fidelity. The rapid rate of technology change significantly affects ongoing as well as pending strategic IT ventures across a wide range of organizations and industries. "Not only is there so much change in our world right now between what used to be called 'emerging technologies' (i.e., mobile, plus social and collaboration-type tools, 'big data,' analytics, cloud), but they are all hitting at the same time," Neff said. "The pace has actually increased, and they're all additive in the nature of our business."

At the 11th annual MIT Sloan CIO Symposium, Neff discussed the pace of change in IT during a panel titled "Working with the CEO and the Board." Panelists Mark Holst-Knudsen, president at ThomasNet; Narinder Singh, president at TopCoder; and Peter Weill, chairman of the MIT Center for Information Systems Research (CISR), joined Neff to discuss who on the business or IT side is responsible for creating the digital roadmap.

View All Photo Stories

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

How is the rapid rate of technology change affecting your organization?
While many of our core programs are well-established and, at least for the nonce, immutable, we're seeing a constant influx of new apps and an endless flow up updates. That means almost constant evaluation and testing. Fortunately, in our world of freelancers, it's been relatively easily to solicit feedback from scores of early adopters and testers. Not quite the same as testing in-house, but at least a bit of shortcut.

While there are many alternatives, we're always trying to lock on the standard used throughout the enterprise. Problem is, when it shifts, we're back to starting over....