Capitolo 1
When Technology Leadership Meets Business Reality
Ever wondered why the most critical executive role in today's digital economy remains so misunderstood? Martha Heller's "The CIO Paradox" illuminates the contradictory demands placed on Chief Information Officers who must simultaneously cut costs while driving innovation, maintain legacy systems while embracing emerging technologies, and act as both technical specialists and business strategists. This book has become required reading in executive MBA programs worldwide, with technology leaders from companies like Google and Amazon citing it as transformative for their careers. Beyond the boardroom, the book's insights have shaped how organizations structure their technology leadership, influencing everything from executive compensation to reporting structures across industries. What makes this exploration so compelling is how it reveals the universal tensions between technology's promise and business reality that affect everyone in our increasingly digital world.
Capitolo 2
Navigating Impossible Expectations in the CIO Role
The fundamental CIO paradox manifests in countless contradictions: you're hired to be strategic but spend most of your time on operational issues; you're expected to cut costs while simultaneously driving innovation; you must maintain legacy systems while embracing emerging technologies. These opposing forces create a position where CIOs are often "damned if they do and damned if they don't."
Werner Boeing, CIO of Roche Diagnostics, captures this perfectly: "We're in an 'And' philosophy now. You have to be cost effective and you have to be innovative." This represents a significant shift from IT's traditional focus on standardization and consolidation to a new expectation of driving business model innovation while maintaining operational excellence.
This paradox reveals a fundamental DNA mismatch in the CIO role. The skills needed to write code and configure networks differ dramatically from those required to envision and communicate future business models. Not all technology leaders possess what I call "the chameleon factor" - the ability to seamlessly shift between operational concerns and innovation leadership. Those lacking this adaptive gene should establish themselves as operational leaders instead, while innovation-minded CIOs trapped in resistant organizations might need to find environments more receptive to technology-driven change.
Successful CIOs develop powerful metaphors to communicate IT's multifaceted role. Boeing uses a Spanish crossroads with three lanes: trucks (foundational systems), taxis (flexible regional processes), and motorcycles (innovation pilots). This visualization helps executives understand how IT simultaneously maintains operations while creating space for experimentation.
Others like Geir Ramleth of Bechtel approach the paradox through simplification. His formula - Speed = Innovation x Simplicity - guided a transformation that reduced IT costs per work hour by 63% while improving service. Rather than creating separate innovation teams, Ramleth embeds innovation within operations through standardized global platforms, benchmarking against newer companies like Google rather than legacy enterprises.
Tom Farrah of Dr Pepper Snapple Group restructured his organization around directors who function as mini-CIOs accountable for both service delivery and innovation. This approach transformed his team's mentality from simply delivering projects to addressing business constraints that prevented selling more product.
The most successful CIOs recognize that innovation requires cultural transformation. Tom Conophy of InterContinental Hotels Group inherited an IT organization "striving for mediocrity" and transformed it by redefining its mission, changing the physical workspace with configurable tables and whiteboards, securing innovation funding, and creating "Tech Jams" for his technical team to focus on code and implementation details.
Capitolo 3
Balancing Operations and Strategy
For a 2010 research project, I asked nearly 400 CIOs to identify which paradoxes resonated most deeply with them. The statement "You were hired to be strategic but you spend most of your time on operational issues" consistently ranked in the top three, striking a particularly sensitive nerve among technology executives. This paradox is so vexing because CIOs often perceive themselves as overhead functions rather than P&L leaders, getting caught up in day-to-day operations instead of strategic thinking.
Ray Barnard transformed his CIO role at Fluor from overhead to strategic by actively driving revenue. He identified twenty potential customers where he had CIO or CFO relationships, created a sales strategy for each, and secured permission to pursue them. Within 18 months, he helped position several billion dollars' worth of deals unrelated to IT. Similarly, Boeing CIO Kim Hammonds leverages her technical knowledge with airline industry customers, educating them on mobile security solutions that Boeing has developed.
To shift from operations to strategy, CIOs must restructure their organizations. Ray Barnard recommends changing from allocation to recovery measurement: "As the business does well, I get specific recoveries that pay for what I'm doing." This approach forces IT to make investment decisions based on business performance, just like a P&L. Boeing's Hammonds dedicates 10% of her 8,000-person IT organization to revenue-generating work on specific customer contracts, separating these teams from operational work.
CIOs must also be realistic about balancing operations and strategy. Alcoa's former CIO Kevin Horner warns against expecting a 50/50 balance: "If you think that you are going to create a fifty-fifty balance between operations and strategy, then you are a fool." During the 2008 recession, Horner cut 30% of IT spend over 24 months, redirecting innovation funds to the bottom line - a strategic decision that supported the business during crisis.
Kumud Kalia, now CIO at Akamai Technologies, emphasizes that CIOs must earn credibility before making strategic contributions, especially when entering new industries: "You have to show that you really understand the business environment before you can expect people to give credence to your ideas." He immerses himself in company operations before attempting strategic discussions.
Ron Kifer's transformation at Applied Materials demonstrates how to balance operations and strategy during a turnaround. Inheriting a dysfunctional IT environment with 17 disconnected groups, poor business perception, and an impending SAP implementation, Kifer established clear preconditions before accepting the role: reporting to the CEO, peer status with executives, consolidated IT authority, and freedom to form his leadership team. His strategy focused on outsourcing contextual activities through a dual-vendor model while building core competencies in project, program, and portfolio management.
Operations management is the price of entry to the CIO position - without handling operational challenges, strategic opportunities never materialize. The key to solving this paradox is building operational excellence while avoiding constant firefighting by outsourcing non-differentiating functions, connecting IT to revenue generation, embedding IT representation in corporate strategy groups, and extending successful IT management models to other business functions.
Capitolo 4
Leading Across Borders and Boundaries
Global IT leadership compounds traditional CIO challenges with multiple countries, time zones, languages, and currencies. The fundamental challenge for global CIOs is balancing standardized global capabilities that enable scale with localized capabilities that provide market responsiveness. As John Dick, former CIO of Western Union (which moved $76 billion among 470,000 locations in over 200 countries), explains, truly global companies operate within and among thousands of local markets, each with different regulations, currencies, business practices, and customs.
Countries newer to technology innovation, unburdened by decades of legacy systems, can leverage relatively inexpensive modern technology to innovate in ways U.S. organizations cannot. Creating a two-way innovation flow requires global CIOs to overcome U.S.-centric thinking and recognize valuable ideas emerging from global markets. John Dick cites Argentina as an example, where Western Union developed a barcode-scanning system for cash bill payments that dramatically reduced transaction times from minutes to seconds. This innovation, born from local necessity, was subsequently deployed to other cash-based economies worldwide.
It's easy to focus succession planning on headquarters staff who are visible daily, neglecting global talent. When Dick joined Western Union, he initially centralized IT leadership in Denver to align with business headquarters. Later, he reversed course, distributing technology leadership across regions to create growth opportunities and build a more diverse senior team.
Customer expectations vary dramatically across markets - Americans demand instant service while customers in countries like India or the Philippines routinely wait 45 minutes for transactions, and Brazilians or French customers abandon transactions after 20 seconds. Systems that work in the U.S. often fail elsewhere, making local market understanding crucial for global IT success.
For Ramon Baez, CIO of Kimberly-Clark, communicating effectively with a global IT organization of 950 people across 175 countries presents a fundamental challenge: how to maintain presence and consistent messaging across vast distances and cultural differences. After trying written blogs that felt too corporate, Baez found success with video blogs. Using a simple flip camera, he records twelve spots at a time for CIO Connect, the IT intranet. His Thanksgiving video on "Feedback Is a Gift" drove unprecedented engagement and behavioral change among his leadership team.
Effective global communication requires personal connection. Baez includes stories about his grandson "Moonpie" in videos, creating common ground that makes him approachable. When visiting global sites, team members at all levels feel they already know him and have conversation starters beyond business topics.
Baez solved the impossible travel demands of global leadership through virtual town halls. After an initial successful in-person Q&A session in the UK, he established quarterly video conferences that let teams ask unfiltered questions. By inviting regional IT leaders to co-host and focusing on questions rather than presentations, these sessions create authentic connections without constant travel.
When Don Goldstein became global CIO at CBRE after its acquisition of Trammell Crow Company, he discovered that executive declarations of "going global" don't automatically create alignment. Regional IT leaders often maintain stronger loyalty to country managers they see daily than to distant global leadership, requiring careful navigation of these embedded relationships while building global capabilities.
Building a truly global IT organization requires patience. Goldstein warns that CIOs with short tenures may not see the transformation through. Despite pressure from global executives for immediate results, regional resistance requires careful management of expectations and strategic patience, moving quickly only when both IT and business leaders are genuinely aligned.
Capitolo 5
Balancing Legacy and Innovation
CIOs face an intensifying supply-demand paradox as consumer technologies flood the workplace. Where technology requests once came primarily from department heads seeking business systems, now everyone from the CEO wanting iPad access to administrative assistants wanting corporate email on personal devices creates unprecedented demand pressure without corresponding budget increases. The pace of change has accelerated dramatically-consumer technologies now gain widespread adoption outside the enterprise before entering it, creating overnight demand explosions rather than gradual adoption curves.
Convincing executives to invest in foundational infrastructure requires creative approaches. Tom Murphy of AmerisourceBergen faced this challenge with a 30-year-old mainframe environment while revenue climbed from $55B to $80B. Rather than endless talking, he created visual heat maps showing the 45 most critical applications failing monthly, making the abstract concrete. When inevitable outages occurred, his CEO finally understood the need for ERP investment. The burning platform became Murphy's ally-the outages that could have cost him his job instead helped executives cross the Rubicon toward infrastructure investment.
The consumerization era requires CIOs to shift from integration to orchestration. Ralph Loura of Clorox notes that while IT previously focused on integrating on-premise systems with complete control over all components, today's environment requires orchestrating third-party solutions without "owning everything in the middle." This demands rigorous architectural thinking with clear APIs and boundary sets to ensure end-to-end service delivery.
The healthcare industry exemplifies the futurist-archivist paradox at its most extreme. Scott Blanchette of Vanguard Health Systems describes how integrating lifetime health data with mobility and predictive analytics could transform healthcare delivery. This integration would enable preventive interventions before health crises occur and make healthcare "iPad simple" for patients. Despite the fragmented reality of current systems, Blanchette refuses to preserve legacy systems, following principles like: avoiding incumbent vendors, partnering with entrepreneurs, keeping data where it is rather than warehousing it, focusing on analytics capabilities, and embracing consumer devices over corporate-issued technology.
As technology becomes embedded in everything from business operations to product development, CIOs face the paradox of being accountable for IT performance while business executives increasingly make independent technology decisions. Boeing CIO Kim Hammonds addresses this by inserting herself into engineering organizations to ensure standards compliance while using data to demonstrate IT's value in security and cost-effectiveness.
Ralph Loura at Clorox employs "client managers" who develop account plans for business groups and work with "solution designers" - rare professionals with blended business and technical knowledge. These solution designers typically come from consulting backgrounds where they've gained broad exposure to various business processes and technologies.
While consumerization and mobility have made IT delivery easier for some CIOs, most face overwhelming business demands that legacy systems struggle to accommodate. Toyota Financial Services' CIO Daniel Priest notes that "sales and marketing teams' heads are swimming with ideas" while they're "living on a legacy servicing system." To address this paradox, CIOs must manage business intersections with the right people in connector roles, revisit architectural assumptions during major technology paradigm shifts, and develop compelling cases for unsexy but necessary legacy improvements.
Capitolo 6
Breaking Down the Business-IT Divide
The phrase "IT and the business" reveals a fundamental disconnect where IT is treated as separate from the organization, unlike other functions such as finance or HR. This separation stems from executive discomfort with technology they don't understand. As Doug Myers of Pepco Holdings notes, IT people have different language, specialized training, transferable skills, and unique job descriptions that naturally separate them from the business. This requires deliberate effort to bridge the gap - essentially "battling the natural order of things" which is a constant part of the CIO's job.
Successful CIOs reject the concept of "IT and the business" as separate entities. Leslie Jones, CIO of Motorola Solutions, transformed her organization by simplifying communication. When she became CIO, she replaced eight-page technical reports with one-page summaries of accomplishments, immediately earning praise from her CEO. Many CIOs struggle with communication because they feel underappreciated - as Geir Ramleth of Bechtel puts it, "Being a CIO is like being a goalie. No one knows your name until you let one in."
Jones eliminated separate IT town halls, recognizing them as counterproductive. "The IT-only meetings were set up to make IT feel good about itself, but you can't make IT feel good about itself if it's not deeply entrenched as a valued member of the business." Instead, she integrated IT staff into business-wide town halls to reinforce that IT is an integral part of the organization.
Language is one of a CIO's most powerful tools for integrating IT with the business. Doug Myers, who came to IT from business leadership roles, finds translating technical concepts into business language natural. He focuses not just on eliminating jargon but on finding terms that resonate - using "assurance" instead of "governance" and discussing "flexibility" rather than "architecture." Karla Viglasky at ITT Corporation uses manufacturing metaphors to explain complex data processes.
Beyond language changes, bridging the IT-business divide requires developing business acumen in your team, particularly those at connection points with business peers. Leslie Jones of Motorola Solutions restructured her IT organization to assign a single point of contact for each business line. Rather than having multiple functional IT groups independently reaching out to business partners, she designated one person per business unit who would serve as the sole interface regardless of the issue.
Colleen Wolf, CIO of Ventura Foods, assigns each IT leader a partner on the business side regardless of project involvement. Her infrastructure head partners with business operations, enterprise architecture with HR, and PMO with finance. This buddy system creates transparency, establishes regular dialogue, and helps IT leaders understand business functions by attending staff meetings and developing relationships outside their technical domains.
CIOs can build business acumen by either recruiting business people with IT aptitude or educating IT staff about the business. Leslie Jones worked with a local college to develop a multi-year program teaching customer-facing teams how to listen to and communicate effectively with business partners, adapting their communication style to different audiences.
The chapter concludes by examining why some CIOs have successfully broken the "IT and the Business" paradox while others haven't. Successful CIOs prioritize communication, language, training, and relationships as much as infrastructure. Despite challenges like resource constraints and security threats, they find ways to embed IT within the business. Key takeaways include: paying attention to language in all communications; improving staff's business knowledge by leveraging internal executives; and embedding IT people directly in business units through mini-CIO structures.
Capitolo 7
Sharing Accountability Without Losing Control
While CIOs can effectively develop IT strategy aligned with business goals and secure funding approval, many struggle with getting business partners to engage in execution. Despite claims that "there are no IT projects, only business projects," CIOs often end up solely accountable when projects fail. This creates the paradox: CIOs are accountable for project success, but business units must own it.
While governance structures are necessary for shared project accountability, they're insufficient alone. As Jeanne Ross of MIT notes, governance committees can become "obstacles to clear accountability" rather than enablers. Michelle Garvey of Warnaco warns that relying solely on steering committees is foolish. The key is having honest conversations about accountability before establishing formal structures.
Kumud Kalia of Akamai Technologies emphasizes addressing accountability early when starting as CIO, using the first hundred days to establish boundaries with executive peers. Before creating committees, have frank conversations about decision rights and responsibilities. Karla Viglasky of ITT Corporation recounts how she prevented being solely accountable for a payroll project by directly engaging the CFO and HR leader, using an analogy about car repair to illustrate why IT shouldn't solely own business projects.
Michelle Garvey emphasizes monitoring the "buzz" around major transformative projects by keeping an ear to the ground beyond formal communications. She maintains individual relationships with senior executives to learn about issues before formal meetings, noting "If you go into a formal meeting without already knowing about a problem, you are vulnerable and naive."
Large programs led entirely by IT almost certainly fail. As Leslie Jones of Motorola Solutions notes, "When you start thinking about the big programs, programs that drive real change, you have to be sure those are led by the business." This creates a paradox: CIOs need egos big enough to initiate transformative projects but small enough to let others take credit.
Not all business partners are interchangeable. Left alone, businesses often assign mediocre but reliable people to IT projects. Ralph Loura learned this at Clorox when a CRM project met all requirements but had only 2% adoption because the VP of sales operations designed a system that required salespeople to spend hours on detailed forecasting - something they had no interest in doing.
Once you have the right business leader for a project, ensure their success by handling the project management details while keeping them as the public face. "Whenever anybody sends a note out to the general population, whenever anybody talks about the program, that leader should be up there as your spokesperson," says Jones. "You may be pulling the wires behind the scenes, but the program has to look like it's totally business led."
CIOs must accept the paradox of driving projects from the backseat while letting the business take credit for successes. This requires setting aside ego despite achieving significant technological feats without receiving due recognition - an inherent part of the CIO role.
The "accountability without ownership" paradox is perhaps the most fundamental CIO challenge. When CIOs are fired, it's often because they couldn't solve this conundrum. Success requires building credibility so strong that when IT is blamed, the business experiences "cognitive dissonance" - as Michelle Garvey explains, "If everyone knows our reputation for delivery, we will get the benefit of the doubt." CIOs must assess their credibility record and ensure business leaders are genuinely engaged in IT initiatives rather than letting the CIO become the de facto product sponsor.
Capitolo 8
Building the Perfect IT Team
The Recruiting Paradox explores how CIOs struggle to find talent that bridges technical expertise with business acumen. Despite being process improvement experts, CIOs often fail to optimize their own recruiting processes. The talent shortage has intensified in the 2010s with emerging technologies like cloud and mobility creating demand for specialists that barely exist in the market.
Recruiting success begins with proper planning and requirements definition. Many CIOs sabotage their searches by creating unrealistic job descriptions that don't align with actual career paths. CIOs often define roles based on organizational needs rather than realistic career paths, creating "purple squirrel" positions impossible to fill. Examples include enterprise architects reporting to PMOs (which good architects avoid) or roles requiring both high-level strategic thinking and hands-on technical implementation-combinations rarely found in the same person.
CIOs frequently underestimate recruiting timelines, expecting to fill specialized positions in weeks when the process realistically takes months. The recruitment cycle-from initial contact through interviews, offers, resignations, and start dates-requires careful planning. Despite being strategic planning experts, CIOs paradoxically fail to apply this skill to their recruiting needs, often launching searches only when facing emergencies.
Despite being incredibly busy, CIOs must invest time upfront with recruiters to discuss role requirements beyond the position description. Sharing insights about priorities, selling points, and team culture helps recruiters find better matches. Delays in approving search documents only extend vacancies.
The interview stage is where recruiting processes often lose momentum, despite seeming straightforward. CIOs who become unavailable during critical recruitment periods risk losing candidates. One CIO's five-week international trip without designating a proxy decision-maker resulted in losing strong candidates who developed negative impressions of the company.
Despite preaching "keep it simple" for IT processes, CIOs often complicate interviews by involving too many stakeholders in initial rounds. This extends timelines unnecessarily when candidates might be eliminated quickly. Better practice: conduct first-round screenings with just the CIO and HR before involving broader teams with finalists.
Candidates often report inconsistent messaging about roles across interview teams or uninspiring presentations of opportunities. Some even experience unprofessional behavior like interviewers falling asleep. CIOs must ensure interview committees align on role requirements and remember they're not just evaluating candidates but also selling the opportunity.
Despite initial urgency to fill positions, companies often introduce delays during critical decision points-waiting for feedback from busy team members or navigating approval processes. These delays frequently result in losing candidates to competing offers. CIOs must set strict deadlines for interview feedback and expedite offer processes.
Recruiters build trust with candidates and understand their compensation expectations and motivations. Some companies mistakenly exclude recruiters from offer discussions, creating misalignment between candidate expectations and actual offers. While CIOs should personally extend offers to build relationships, they should involve recruiters in formulating those offers.
With the ongoing talent crisis, recruitment must become a core competency for IT leaders. The author emphasizes that attention to detail and proper process management are essential when working with search partners.
Capitolo 9
Finding the Perfect Enterprise Architect
Enterprise architecture searches present a unique challenge due to the paradoxical nature of the role. The ideal candidate must possess expertise across the entire technology stack, manage matrixed teams of entrenched technologists, understand business deeply, and communicate complex concepts like service-oriented architecture to non-technical executives. This creates what I call "The Enterprise Architecture Paradox": finding someone who combines technology genius, business strategy acumen, management skill, and expert communication ability.
The Enterprise Architecture Paradox manifests in several competing tensions. The theoretical ideal of efficiency through standardization conflicts with the need for flexibility to address diverse business needs. As Lynden Tennison of Union Pacific explains, while IT leaders want commonality and deep expertise in a limited toolset, different business units have contradictory requirements - marketing needs innovation while finance demands tight controls.
Tom Feichtinger, VP of enterprise architecture at Waste Management, observes that architects often waste time cataloging current systems rather than focusing on future direction. He shares how a consultant's question - "Why capture your entire as-is state when you won't use 90% of it for years?" - changed his perspective. Using GM's satellite networks as an example, he demonstrates how documenting soon-to-be-obsolete systems wastes valuable time that could be spent on forward-looking planning.
Enterprise architects must balance conceptual models with practical implementation needs. Tennison warns that architects who create esoteric models risk becoming disconnected from those building actual solutions. Feichtinger recalls how at GM, some architects would disappear for weeks to work on theoretical taxonomies and processes while others focused on ensuring project success.
Another paradox emerges when architects are pulled from strategic work to address tactical needs. Feichtinger describes how CIOs under cost-cutting pressure would redirect enterprise architects to find operational savings, pulling talented staff away from important strategic initiatives. While this might yield immediate results like finding $10 million in savings, it prevents developing crucial long-term strategies for technologies like mobile computing.
Many enterprise architecture functions fail because companies never see their business value, creating a vicious cycle where architecture gets a bad reputation. However, successful enterprise architecture organizations do exist, and they follow specific approaches to manage the inherent paradoxes of the function and deliver clear business value.
CIOs who successfully manage enterprise architecture keep their teams focused on the future by setting specific goals. Feichtinger explains that vague questions like "What do you think about portals?" lead architects to inventory current technology rather than develop strategy. Instead, specific directives like "Define our strategy for customer-facing websites" point architects toward future-focused work rather than cataloging the present state.
A common complaint about enterprise architecture groups is their reputation as "standards police" who slow projects and create resentment. Feichtinger describes inheriting a team that graded projects on compliance and held back development until standards were met - even for leading-edge technologies where no standards existed. At Waste Management, they instead got ahead of innovation projects, evaluating new technologies and developing standards proactively so they were ready when development teams needed them.
Finding great enterprise architects is challenging as they're in high demand and cautious about opportunities. Candidates question whether companies truly support enterprise architecture or if they'll lose resources shortly after starting. While external hiring is sometimes necessary, organizations are better positioned when they can develop enterprise architecture talent internally.
Lynden Tennison of Union Pacific has successfully grown enterprise architecture talent internally since becoming CIO in 2005. He warns against the common mistake of promoting the best technologists to architecture roles, noting that enterprise architects need versatility across multiple technologies rather than deep expertise in one area. This creates another paradox: needing to hire talent now to prepare for an unpredictable future.
The enterprise architecture function embodies much of the CIO Paradox, requiring leaders to be both technical and strategic, practical and innovative, brilliant yet humble. With cloud computing, data management, and mobility transforming technology stacks, the challenge is greater than ever.
Capitolo 10
Charting the CIO's Future
The CIO role has been scrutinized more than perhaps any other executive position since its emergence in the early 1980s. This constant examination may stem from technology's rapid evolution - while principles of sales, marketing, and finance remain relatively stable, technology platforms shift approximately every eighteen months. The CIO's responsibilities are particularly difficult to define compared to other executive functions, as technology paradigms continuously evolve (from software-as-a-service to platform-as-a-service).
CIOs have evolved from driving basic process automation to implementing communication systems, ERP, and outsourcing - each phase requiring new skills in technology, project management, change leadership, business processes, and vendor management. The next frontier appears to be business model innovation. Insurance company CIOs are developing pedometer apps for customers while retail CIOs enable consumers to design custom products. Peter High, author of "World-Class IT," describes this evolution as "CIO squared" - combining information and innovation officer roles.
CIOs' program management and change leadership capabilities make them natural champions for continuous improvement across enterprises. As more IT functions move to outsourcing and cloud solutions, CIOs can shift focus from hands-on operations to making business processes faster, better, and cheaper throughout the organization. Ron Kifer, former CIO of Applied Materials, envisions future CIOs broadening their influence beyond IT to take responsibility for quality and continuous improvement, becoming "modelers of change behavior" both within and outside IT.
In the Chief Intelligence Officer role, CIOs focus on transforming data into actionable business intelligence, regardless of technology involvement. Wayne Shurts at SUPERVALU developed a solution for improving produce sales using simple "sticky tape" rather than complex technology. Many CIOs have evolved beyond the "technology hammer" mindset to become information stewards who help businesses make faster, better decisions than competitors.
For companies where business units make independent technology investments or where technology remains primarily operational, CIOs will evolve into contract management executives overseeing various software and service providers. Lynden Tennison of Union Pacific suggests this role will be most common in companies where CEOs don't view technology as highly strategic. Doreen Wright predicts large companies will eventually have almost no in-house IT, with CIOs focusing on vendor negotiations while expanding their oversight to other shared functions like legal, procurement and HR.
After years of CIOs focusing primarily on business alignment rather than technology itself, many are now flexing their technologist muscles again. Conversations with CIOs have shifted back toward technical topics like architecture, mobile security, and form factors. As Lynden Tennison explains, this "technical CIO" brings leading-edge technical competence that helps differentiate the business, staying deeply connected to the technical community and evolution of tools and standards.
Tom Conophy envisions future CIOs leading small teams of "big foreheaded people" - forward-thinking domain experts who oversee major contracts with cloud providers while acting as conductors ensuring solution integrity. Barbra Cooper similarly sees the CIO evolving into a "chief architect" who anticipates how technology will transform the business while masterfully integrating all moving parts.
With every company becoming a technology company regardless of industry, CIOs face three potential paths: managing back-office systems, embracing software development backgrounds to architect technology platforms that run through all products, or running technology product businesses. In the Chief Engineering Officer role, a technical background becomes an asset rather than a liability compared to business experience.
Technology innovation creates demand for new executive skills, with companies still determining optimal organizational placement. The emerging "products" focus across industries from retail to healthcare is reshaping the CIO role. In some companies, CIOs lead product development strategies; in others, they provide infrastructure support to business-led product teams. Regardless of how the "products issue" evolves, executives who understand technology and its business impact will remain essential.
