As you may know, I recently was named the Research Director for our CIO team — a team of highly accomplished and experienced analysts at Forrester. One of our first tasks as a team was to define the current changes in the technology and business landscape and develop a cohesive view of what this means for the role of CIO. What will it mean to be a CIO in the “empowered” world? As you can imagine, this led to a healthy debate and many different perspectives on what the future CIO role would look like. Here are some highlights from our discussion so far.
What is changing for the CIO?
Technology plays an increasingly critical role in business success. In Forrester’s Forrsights Budgets And Priorities Tracker Survey, Q4 2010, 52% of the business decision-makers strongly agreed with the statement “Technology is fundamental element of our business model.” Many companies are starting to use technology as a business differentiator, and many businesses rely on technology to provide critical information for making strategic business decisions.
Empowered technologies make it easy to bypass IT. The empowered technologies — social, mobile, video, and cloud — are rapidly transforming the information landscape. Increasingly, these technologies are easy to acquire and bring into the corporate environment, and many can be sourced and managed outside of IT’s control — making it easy for the business and employees to bypass IT.
Greetings — thanks for taking the time to read my inaugural blog! Let me introduce myself by way of continuing a discussion that I started at Practicing EA and CIO.com on innovation and technology that I think strikes at the heart of our challenges as enterprise architects. It also provides a good context for my future research, which I discuss at the end.
Closing The Innovation Gap
In part 1 of this post, I claim that a gap opened while we were fighting the overly complex, expensive current state and trying to help our business partners innovate with new technology.
The gap – We cannot deliver new technology and innovation quickly or cheaply enough.
Shadow IT Is The Symptom, Not The Cause
The Symptom – We often blame Shadow IT and manual workarounds for increases in complexity, reduction in quality of service, and obscuring true technology costs. These are symptoms of the problem, not the problem itself.
The Cause – Business users know more about what they need and when they need it and are the most motivated to solve their problems now, not once the budget cycle gets around to funding a project. Central IT, where most EAs practice, is a knowledge store for designing enterprise-scale systems but is constrained in its ability to deliver.
Every year, people talk about the future of IT, which is shorthand for, "Some big changes may be in the works." In the last year, we've had to revise that sentence to read, "Some big changes are definitely in the works." Agile practices will be a critical tool for making this transition successfully, but not because of velocity. At least, that won't be the primary virtue of Agile that helps with the transition.
One of the Founding Fathers of Agile, Jim Highsmith, recently commented on his blog about an MIT study that surveyed one face of this mountain of change:
The implications of these changes in emphasis could be significant in terms of mindset and capabilities in and out of IT departments. From a focus on standardization, optimization, and cost control, the focus shifts to innovative uses of emerging technologies such as social media, cloud computing, and mobile devices; speed to market; flexibility to follow changing opportunities, and building new products and services.