The Value Imperative How CIOs Must Justify Every Technology Dollar

Nancy Avila, CIO of Analog Devices, opens her recent interview with McKinsey senior partner Gayatri Shenai with a statement that should make every technology leader pause: "If you're not driving value for shareholders, employees, or the customer, then you're just adding costs for the company." This unvarnished assessment captures a fundamental shift in how organizations evaluate their technology leadership. The era of technology for technology's sake has definitively ended.

The interview, part of McKinsey's Women in Tech series, reveals a leadership philosophy built on a deceptively simple premise: every technology decision must connect explicitly to business value. Yet beneath this straightforward principle lies a sophisticated approach to technology leadership that challenges conventional wisdom about the CIO role, organizational structure, and the relationship between business strategy and technical architecture.

The Trust Deficit Between Business and Technology

Avila identifies trust as the foundational element enabling technology leaders to extend their influence beyond traditional IT boundaries. This focus on trust acknowledges an uncomfortable reality: many business executives remain fundamentally skeptical of technology investments. Years of failed implementations, cost overruns, and unclear returns have created institutional wariness toward IT spending.

The prescription Avila offers centers on transparency. Rather than obscuring technology decisions in technical jargon, she advocates making explicit connections between infrastructure investments and business outcomes. When requesting funding for cybersecurity infrastructure, for instance, she frames the discussion around business risk protection rather than IT asset security. This reframing transforms what might appear as technical overhead into strategic business protection.

Research from Gartner's 2024 CIO Agenda Survey supports this evolving dynamic, finding that 63% of CIOs now participate in business strategy beyond IT matters. However, this expanded mandate creates new challenges. As MIT Sloan Management Review documented in their 2024 study on digital infrastructure, CIOs must balance operational excellence with strategic innovation while justifying expenditures that may not generate immediate returns.

The transparency approach carries risks that Avila does not fully address. Complete visibility into technology costs and architectural decisions can invite micromanagement from business leaders lacking technical depth. When every infrastructure investment requires explicit business justification, organizations may underinvest in foundational capabilities that enable future innovation but lack immediate ROI. The challenge becomes distinguishing between wasteful spending and necessary technical debt reduction or platform modernization.

Portfolio Management as Business Alignment

Avila positions strategic portfolio management as the mechanism for aligning technology investments with business priorities. She describes implementing a retrospective review process at Analog Devices that revealed misalignment between actual technology work and strategic priorities. The team discovered they were executing numerous small maintenance tasks rather than making strategic investments in customer engagement.

This finding led to a fundamental reprioritization. Working directly with the Chief Customer Officer, Avila's team redesigned their portfolio to focus on products that improved customer interaction rather than incremental CRM enhancements. Similarly, when reviewing their ERP platform, customer-focused analysis shifted priorities from general stabilization toward capabilities like pricing, invoicing, and forecasting that directly impacted customer experience.

The portfolio management approach Avila describes mirrors practices long established in product management and investment banking. By treating technology initiatives as investment portfolios requiring active management and regular rebalancing, CIOs adopt the financial discipline expected of other major corporate expenditures. This framing helps business leaders understand technology spending through familiar frameworks.

Yet portfolio management methodologies, while valuable, carry inherent limitations. They tend to favor quantifiable, short-term returns over difficult-to-measure, long-term capabilities. As Harvard Business Review noted in their 2023 analysis "The New CIO Paradox," excessive focus on immediate business value can prevent the exploratory work that leads to breakthrough innovations. Netflix's eventual dominance in streaming, for instance, required years of infrastructure investment that would have struggled to justify itself through traditional portfolio management lenses.

The tension between operational efficiency and strategic exploration represents a fundamental challenge Avila's framework does not fully resolve. How should CIOs allocate resources between projects with clear business cases and speculative investments that might enable future competitive advantage? The portfolio management discipline Avila advocates provides necessary rigor but may inadvertently bias organizations toward incremental improvement over transformational change.

Breaking Down Functional Silos Through Technology

Avila argues that modern technology implementation requires organizations to abandon functional silos in favor of process-oriented thinking. Traditional organizational structures separated finance, operations, and customer service, allowing each function to optimize locally. However, delivering seamless customer experiences or implementing automation requires data and systems to flow across functional boundaries.

This insight positions the CIO as an organizational architect, not merely a technology provider. When functions operate independently, they optimize for local efficiency at the expense of enterprise effectiveness. The CIO, with visibility across the entire technology landscape, can identify these inefficiencies and advocate for process redesign.

Avila provides a concrete example: automating customer service requires accessing supply chain systems to provide accurate information. Without cross-functional integration, customer service representatives lack the real-time visibility needed to resolve inquiries effectively. Technology integration becomes the catalyst forcing necessary organizational change.

This argument for cross-functional integration through technology echoes Peter Drucker's observations about information-based organizations. Drucker predicted that information technology would flatten organizational hierarchies and require new coordination mechanisms. What Avila describes represents this prediction's practical implementation: technology architecture drives organizational architecture.

However, using technology as the lever for organizational change raises questions about appropriate sequencing. Should organizational redesign precede technology implementation, or should technology capabilities drive organizational evolution? Avila implies the latter, suggesting that CIOs can use platform requirements to justify breaking down silos. This approach may encounter resistance from functional leaders protective of their autonomy.

The case of General Electric's attempted digital transformation under former CEO Jeff Immelt illustrates these challenges. GE invested billions in building Predix, a platform for industrial IoT applications, while simultaneously trying to transform GE from a manufacturing conglomerate into a "digital industrial company." The initiative struggled partly because organizational structures, incentives, and culture did not align with the technological vision. Technology alone could not overcome organizational inertia.

Infrastructure as Strategic Capability

Avila challenges the conventional distinction between strategic technology initiatives and operational "keep the lights on" work. She argues that infrastructure represents strategic capability, not merely operational necessity. Modern data-driven solutions and AI capabilities require robust network infrastructure, cloud capacity, and data architecture. These capabilities enable business innovation but are often categorized as pure cost centers.

This reframing addresses a persistent challenge in technology budgeting. CFOs and business leaders naturally gravitate toward customer-facing applications with clear revenue implications while viewing infrastructure as overhead to be minimized. Avila contends this perspective undermines long-term competitiveness by creating technical debt and limiting future flexibility.

She illustrates this principle through Analog Devices' data strategy evolution. Rather than building a massive centralized data environment, the company adopted a data mesh architecture based on composable, flexible components. This architectural choice enables faster deployment of AI and data intelligence use cases by distributing data ownership and reducing bottlenecks.

MIT Sloan Management Review's 2024 research on digital infrastructure provides empirical support for Avila's position. Companies treating infrastructure as strategic rather than operational achieved 23% higher digital maturity scores and demonstrated greater ability to adapt to market changes. The research suggests infrastructure flexibility correlates with business agility, validating the strategic importance Avila ascribes to these investments.

Capital One's cloud migration under former CIO Rob Alexander offers another compelling example. Alexander led one of the first major financial services migrations to public cloud, a multi-year initiative requiring significant upfront investment. Critics questioned the business case for such massive infrastructure spending. However, the cloud infrastructure ultimately enabled Capital One to accelerate product development, improve operational resilience, and reduce long-term costs. The strategic infrastructure investment created capabilities that competitors struggled to match.

Yet Avila's argument that infrastructure is strategic does not eliminate the need for financial discipline. Not all infrastructure investments generate equivalent value. The challenge lies in distinguishing between necessary strategic infrastructure and gold-plating. How should organizations evaluate competing infrastructure architectures? When does infrastructure investment cross from strategic enabler to unnecessary complexity?

Target's technology modernization following their 2013 data breach illustrates both the necessity and challenge of infrastructure investment. The breach exposed fundamental infrastructure weaknesses requiring comprehensive remediation. Target invested heavily in cybersecurity infrastructure, network segmentation, and monitoring capabilities. These investments were clearly necessary but generated no direct revenue. The business case rested entirely on risk mitigation and enabling future capabilities. How should organizations value such investments relative to revenue-generating initiatives?

Governing Innovation Without Stifling Experimentation

Avila describes acting as a "gatekeeper" for emerging technologies, particularly generative AI tools and agents. She distinguishes between "I want a gen AI tool" and "this tool generates value," emphasizing the importance of tangible use cases and technology maturity. Her team experiments with new capabilities but accelerates adoption only after validating enterprise readiness and business value.

This governance approach attempts to balance innovation with control. Organizations face intense pressure to adopt artificial intelligence and other emerging technologies, driven by competitive fear and vendor marketing. Without disciplined evaluation, companies risk accumulating a sprawl of disconnected tools lacking governance or integration.

Avila's framework emphasizes experimentation followed by scaled deployment. Her team tested AI agent capabilities from a vendor, validated the technology's enterprise maturity, and then accelerated their roadmap. This staged approach reduces risk while maintaining innovation momentum.

However, the gatekeeper role creates tension with Avila's earlier emphasis on business partnership. If IT acts as gatekeeper, determining which innovations receive investment, does this undermine the collaborative portfolio management process she advocates? How should organizations balance IT governance with business unit autonomy? These questions become particularly acute with accessible technologies like generative AI, where business users can adopt tools independently.

The history of shadow IT suggests that overly restrictive governance drives business units to circumvent IT entirely. Salesforce, Slack, and numerous other enterprise technologies achieved initial adoption through departmental purchases outside IT oversight. While this created governance challenges, it also drove innovation that centralized IT departments might have blocked.

Avila's approach implies a mature, trust-based relationship between IT and business leadership. In such environments, IT gatekeeping serves a valuable coordination function, preventing duplication and ensuring coherent architecture. However, in organizations lacking this trust foundation, the same gatekeeping might be perceived as obstruction, driving underground adoption.

The Loneliness of Technology Leadership

Avila makes a revealing admission about the CIO role: "CIO can be a very lonely role, because most execs don't understand what we do." This observation highlights a persistent challenge in technology leadership. Despite expanded business responsibilities and strategic influence, many CIOs remain isolated within executive teams.

This isolation stems partly from the technical complexity of technology decisions. While business executives understand financial trade-offs or marketing strategies through shared frameworks, technology architecture discussions often occur in specialized language that excludes non-technical leaders. Even when CIOs frame discussions in business terms, the underlying technical considerations remain opaque to many executives.

The isolation also reflects organizational dynamics. CIOs often report to CFOs, positioning them as service providers rather than strategic peers. This reporting structure, while increasingly questioned, persists at many organizations. Even when CIOs report directly to CEOs, they may lack operational responsibility for business outcomes, limiting their credibility in strategy discussions.

Avila's recommendation to build peer networks acknowledges that CIOs cannot rely solely on internal relationships for support and validation. External peer groups provide benchmarking, emotional support, and knowledge sharing that helps CIOs navigate their unique challenges.

The loneliness Avila describes suggests limits to the business partnership model she advocates. Even exemplary CIOs practicing transparency and value articulation may struggle to achieve full integration into business leadership. This reality should temper expectations about how fully technology leadership can merge with business strategy.

Practical Implications for Technology Leaders

Avila's approach offers several practical lessons for technology leaders navigating the business value imperative:

• First, establish explicit connections between every significant technology investment and business outcomes. This requires moving beyond generic statements about "enabling the business" to specific metrics tied to revenue, cost reduction, risk mitigation, or customer satisfaction. Infrastructure investments should be framed in terms of capabilities enabled, not technical specifications.
• Second, implement rigorous portfolio management processes that classify technology initiatives by business objective rather than technical category. This classification forces regular dialogue with business leaders about strategic priorities and creates shared accountability for outcomes. The portfolio should be reviewed and rebalanced regularly as business conditions change.
• Third, use transparency strategically to build credibility. Rather than hiding technology complexity, explain architectural decisions in business terms that highlight trade-offs and alternatives. This educational approach helps business leaders develop technology literacy while demonstrating IT's business acumen.
• Fourth, position infrastructure and platform investments as strategic capabilities rather than operational costs. This requires educating business leaders about how foundational technologies enable future innovation. Use specific examples of business capabilities that require particular infrastructure investments.
• Fifth, develop governance frameworks for emerging technologies that balance experimentation with control. Create clear criteria for moving from pilot to scaled deployment based on business value, technical maturity, and integration requirements. Communicate these criteria broadly to set appropriate expectations.
• Sixth, invest in building peer relationships with other technology leaders facing similar challenges. These relationships provide perspective, support, and practical knowledge that helps navigate the inherent tensions in technology leadership.

Unresolved Tensions and Limitations

While Avila's framework provides valuable guidance, several tensions remain unresolved:

The emphasis on explicit business value justification may undermine investments in exploratory innovation or technical debt reduction. Not all valuable technology work generates immediate, measurable business outcomes. Organizations need mechanisms for funding foundational work that enables future capabilities without requiring precise ROI calculations.

The portfolio management discipline Avila advocates works best for defined initiatives with clear outcomes. It handles uncertainty less well. Breakthrough innovations often emerge from experimentation without predetermined business cases. How should organizations balance portfolio discipline with exploratory work?

The business partnership model assumes aligned incentives between technology and business leaders. In practice, functional leaders often optimize for local outcomes at the enterprise's expense. Technology integration may threaten existing power structures or require uncomfortable organizational changes. How should CIOs navigate situations where business partnership conflicts with enterprise optimization?

The infrastructure-as-strategy argument, while conceptually sound, provides limited guidance for prioritizing among competing infrastructure investments. Multiple architectural approaches might all be "strategic." Organizations need frameworks for evaluating trade-offs between different strategic infrastructures, considering factors beyond pure business value.

The gatekeeper role for emerging technologies creates potential conflict with business autonomy and innovation speed. While governance prevents chaos, excessive control stifles experimentation. The appropriate balance depends on organizational culture, risk tolerance, and competitive dynamics in ways that resist universal prescription.

Conclusion

Nancy Avila's approach to technology leadership reflects broader evolution in how organizations understand the relationship between technology and business value. The days when IT could operate as a semi-autonomous technical function have irrevocably ended. Technology has become too central to business operations, too expensive, and too complex to remain isolated from business strategy.

The value imperative Avila articulates responds to this reality by demanding explicit connections between technology investments and business outcomes. This discipline forces healthy conversations about priorities, trade-offs, and architectural decisions. It elevates technology discussions from technical specifications to business strategy.

However, the approach also carries risks. Excessive emphasis on immediate, measurable value can undermine the exploratory work that enables breakthrough innovation. The business partnership model works best in organizations with mature, trust-based relationships between technology and business leaders. In organizations lacking this foundation, the same principles might feel constraining rather than liberating.

The most valuable aspect of Avila's framework may be less the specific practices she advocates than the mindset she embodies. Technology leaders must think as business leaders first, technologists second. They must translate technical decisions into business language while educating business colleagues about technology trade-offs. They must balance operational excellence with strategic innovation, governance with experimentation, and transparency with appropriate complexity management.

This expanded mandate makes technology leadership more challenging but also more impactful. CIOs willing to embrace the value imperative, build transparent relationships with business leaders, and position technology as strategic capability will find expanded influence and impact. Those clinging to traditional technical roles will find themselves increasingly marginalized.

The fundamental question facing technology leaders is not whether to embrace the value imperative but how to implement it while preserving the capacity for innovation, managing technical complexity appropriately, and maintaining the infrastructure foundations that enable future capabilities. Nancy Avila's experience provides valuable guidance for navigating these challenges, even as the specific practices must be adapted to each organization's unique circumstances.

The technology leadership role will continue evolving as technology itself evolves. Today's challenges around cloud architecture, data mesh platforms, and AI governance will give way to new challenges around quantum computing, advanced AI, and technologies not yet imagined. Throughout these changes, the core principle Avila articulates will remain relevant: technology exists to create business value. Leaders who lose sight of this fundamental truth will struggle regardless of their technical sophistication. Those who embrace it, as Avila demonstrates, can transform both their organizations and their profession.