For more than 20 years, I have heard variations of the same debate: How technical should a CIO really be?

Should the CIO be a superb technologist, a former programmer, or an architect who can challenge every technical decision? Or should the CIO primarily be a business executive?

My experience has led me somewhere in the middle—but not to a 50/50 compromise. The most successful CIOs combine business acumen, technical astuteness, domain experience, strategic judgment, communication, leadership, charisma, executive presence, and political acuity. They understand technology deeply enough to lead it, but operate at the altitude of the enterprise.

Technical Astuteness Is Not Technical Supremacy

A CIO does not need to be the best programmer, cloud architect, database engineer, cybersecurity specialist, or infrastructure expert in the organization. The CIO needs technical astuteness rather than technical supremacy.

They need enough depth to understand architecture, cybersecurity, data, cloud, AI, infrastructure, resilience, integration, technical debt, and delivery risk. More importantly, they must understand the business implications.

When an architect says, “We need to modernize this platform,” the CIO should be asking: Why? What happens if we do nothing? What business risk are we carrying? What will the investment cost? What organizational capability will it unlock? What other priorities compete for the same capital?

That is very different from personally designing the architecture.

The CIO Has to Operate in Multiple Worlds

1. Business Acumen

The CIO must understand how the organization makes money, serves customers, manages costs, competes, controls risk, and executes strategy. Technology is increasingly part of the operating system of the business itself.

2. Technical Astuteness

The CIO needs enough technical credibility to challenge assumptions and ask intelligent questions without trying to replace the architects, engineers, developers, security specialists, and operations leaders who work for them. The goal is not to compete with technical specialists. It is to lead them.

3. Domain Knowledge

Technology decisions do not exist independently of regulation, customer expectations, operational processes, risk tolerance, legacy platforms, procurement models, and industry economics. Domain knowledge helps a CIO distinguish an interesting technology from a technology that actually matters.

4. Communication, Leadership and Executive Presence

A CIO must translate. An architect might say: “We are accumulating architectural debt in the integration layer.” The CIO may need to tell the board: “Our current architecture is increasing the cost and time required to launch new products. If we do not address it, competitors will increasingly be able to move faster than us.” Same problem. Different language.

The CIO also has to influence people they do not control, attract strong leaders, challenge peers, negotiate investment, explain failures, defend technology teams when appropriate, and hold those same teams accountable when necessary.

5. Political Acuity

Large organizations are political systems—not necessarily in the negative sense. Capital is finite. Priorities compete. Executives have different incentives. Business units protect their interests. Transformation creates winners and losers.

A CIO who cannot navigate those dynamics can have the right strategy, architecture, and people and still accomplish surprisingly little.

The CIO Is an Orchestrator

Think about an airline CEO. We do not ask whether the CEO is the finest pilot in the company. The CEO needs to understand aviation, safety, operations, economics, customer experience, and regulation. But their job is to orchestrate an enormously complicated system—not personally fly the aircraft.

The CIO increasingly occupies a similar position.

The CIO is not primarily the organization's chief technologist. The CIO is the executive responsible for converting technological capability into organizational capability.

AI Makes This Even More Important

AI is making technology more deeply embedded in business operations, decision-making, customer experience, workforce design, and competitive strategy. As technology becomes inseparable from the business, the CIO needs stronger business judgment, communication, governance, and organizational leadership.

The future CIO may therefore need to become more executive, not simply more technical.

Judgment Is the Integrating Capability

Business acumen. Technical astuteness. Domain knowledge. Strategic thinking. Communication. Leadership. Executive presence. Political acuity. All of those capabilities ultimately converge on one thing: judgment.

The CIO does not need to know how to build everything. They need to know what should be built, why it matters, what it will cost, what could go wrong, who should build it, and how to move the organization toward it.

Key Takeaways

  • A CIO needs technical astuteness, not technical supremacy.
  • Business acumen is fundamental because technology is embedded in the operating model.
  • Domain knowledge separates attractive technology from technology that creates meaningful value.
  • Communication and executive presence translate technical complexity into business decisions.
  • Political acuity matters because transformation competes for capital, attention, and support.
  • The CIO's ultimate job is to convert technological capability into organizational capability.
  • The capability tying everything together is judgment.