Beyond the Technology Checkbox — Why Technology Governance Deserves a More Nuanced Place in Board Skills Matrices

By Raviprasad Bangalore | Senior Vice President & Head of Technology, Comviva (Tech Mahindra) | India's Top 10 AI Trailblazers — ET India


The Checkbox Problem

Ask most nomination committees how they assess technology governance capability on a board, and the answer follows a familiar pattern. The skills matrix has a column labelled "Technology" or "Digital." One or two directors have a tick in that column. The committee is satisfied that technology is covered.

That tick is doing an enormous amount of work — and in most cases, it is not doing it well.

The technology column in a board skills matrix was designed for a different era. It was designed when technology was primarily an operational concern — infrastructure, systems, IT spend. When the most important technology question a board faced was whether the ERP implementation was on budget. When "technology director" meant someone who had run an IT function or sat on a technology company's board.

That era is over.

Technology is now the primary driver of competitive differentiation, the primary source of enterprise risk, and the primary vehicle for business model transformation — simultaneously. The decisions being made in technology today — about AI adoption, cloud architecture, data strategy, platform investments, cybersecurity posture, and digital business models — are not operational decisions. They are strategic decisions with consequences that will shape the organisation for a decade.

A single checkbox labelled "Technology" is not a governance response to that reality. It is a governance fiction.


What the Checkbox Misses

The fundamental problem with the technology checkbox is that it treats technology governance as a single, undifferentiated capability — when it is actually a cluster of distinct, non-overlapping competencies that require different backgrounds, different experience bases, and different oversight lenses.

Consider what a board is actually being asked to govern when it governs technology in 2026:

AI and Agentic AI adoption — decisions about which AI systems to deploy, what decisions those systems are authorised to make autonomously, how AI outcomes will be governed, and what the regulatory exposure is. This requires a director who understands how AI systems actually work — architecturally and operationally — not just what they are capable of in a demonstration.

Cloud transformation and infrastructure strategy — decisions about cloud investment, vendor selection, migration approach, cost governance, and the build-versus-buy choices that determine the organisation's technology cost structure for years. This requires a director who has led or governed cloud transformation at scale — not one who has read about it.

Cybersecurity and technology risk — decisions about security posture, incident response capability, regulatory compliance, and the organisation's exposure to technology-driven risk. This requires a director who can interrogate a CISO independently — not one who defers to management's assurance that "we take security seriously."

Digital business model and platform strategy — decisions about how technology creates competitive differentiation, how digital platforms are monetised, and whether the organisation's technology investments are building durable competitive advantage or just keeping pace. This requires a director who understands product strategy, platform economics, and technology monetisation.

Data governance and privacy — decisions about how data is collected, stored, used, and protected — with direct implications for regulatory compliance, customer trust, and AI capability. This requires a director who understands data architecture and the regulatory landscape, not just data as a business asset.

These are five distinct governance domains. They require five distinct competency profiles. A single tick in a "Technology" column cannot cover all five — and in most boards, it is not covering any of them with the depth the organisation actually needs.


How We Got Here — The Skills Matrix as Compliance Exercise

Board skills matrices were designed as governance tools. Their purpose was to give nomination committees and shareholders a structured view of the capabilities available at board level — and to identify gaps that needed to be filled through director recruitment or development.

In practice, many skills matrices have become compliance exercises. They are populated to demonstrate coverage rather than to honestly assess capability. The categories are broad enough that almost any director can claim a tick in almost any column. The result is a matrix that looks comprehensive and provides genuine oversight in very few areas.

Technology is particularly vulnerable to this dynamic because the category is so broad and the capability so difficult to assess from the outside. A director who ran a technology services business 15 years ago and a director who is currently building Agentic AI platforms at production scale will both receive a tick in the "Technology" column. From a skills matrix perspective, they are equivalent. From a governance perspective, they are not remotely comparable.

The nomination committee that treats them as equivalent is not being negligent. It is working within a framework that was not designed to make that distinction. The framework needs to change.


What a Nuanced Technology Governance Framework Actually Looks Like

The solution is not to make skills matrices more complex for the sake of complexity. It is to make the technology governance assessment more precise — so that boards and nomination committees can honestly identify what they have, what they need, and what the gap is.

A more nuanced framework disaggregates technology governance into specific domains and assesses each one against two dimensions: currency (is this expertise current, or is it based on experience that is more than five years old?) and depth (is this expertise at a governance level, or is it operational familiarity?).

Domain 1: AI and Emerging Technology Governance What it covers: AI strategy oversight, Agentic AI governance, AI risk and ethics, emerging technology adoption frameworks, AI regulatory compliance. Currency requirement: This domain is moving so fast that expertise more than two to three years old is of limited governance value. A director whose AI experience is based on early machine learning deployments does not have the mental model needed to govern Agentic AI adoption decisions in 2026. Depth requirement: Governance-level expertise means the ability to interrogate management's AI strategy independently — to ask questions that cannot be deflected with jargon, to recognise when an AI governance framework is genuinely robust versus superficially compliant, and to understand the regulatory trajectory well enough to anticipate future obligations.

Domain 2: Cloud and Infrastructure Strategy What it covers: Cloud transformation governance, vendor concentration risk, cloud cost governance, infrastructure modernisation oversight, multi-cloud strategy. Currency requirement: Cloud technology and economics have changed significantly in the last five years. Experience with early cloud adoption — pre-2018 — provides limited insight into the governance challenges of modern cloud transformation programmes. Depth requirement: Governance-level expertise means the ability to challenge management's cloud investment case, identify the assumptions that are most likely to be wrong, and ask the specific questions about vendor dependency, cost governance, and capability building that most cloud presentations do not address.

Domain 3: Cybersecurity and Technology Risk What it covers: Cybersecurity posture oversight, technology risk governance, incident response capability, regulatory compliance (data protection, sector-specific requirements), AI-specific security risk. Currency requirement: The threat landscape and regulatory environment are evolving continuously. This domain requires active, current engagement — not historical experience. Depth requirement: Governance-level expertise means the ability to interrogate the CISO and technology risk function independently — to assess whether the organisation's security posture is genuinely robust or optimistically presented, and to understand the regulatory obligations well enough to identify gaps.

Domain 4: Digital Business Model and Platform Strategy What it covers: Technology-driven competitive differentiation, platform economics, SaaS and digital product strategy, technology monetisation, ecosystem and partnership strategy. Currency requirement: Digital business models are evolving rapidly. Experience with digital transformation programmes from the early 2010s provides limited insight into platform strategy, AI-native product development, and ecosystem monetisation in 2026. Depth requirement: Governance-level expertise means the ability to challenge management's technology investment case from a commercial perspective — to ask whether the technology is building durable competitive advantage or just generating activity, and whether the monetisation model is realistic.

Domain 5: Data Governance and Privacy What it covers: Data strategy oversight, data quality governance, privacy compliance (DPDPA, GDPR, sector-specific requirements), data architecture, AI data readiness. Currency requirement: The regulatory landscape for data is changing rapidly, particularly in India with the Digital Personal Data Protection Act. Currency in this domain requires active engagement with the evolving regulatory environment. Depth requirement: Governance-level expertise means the ability to assess whether the organisation's data governance framework is fit for purpose — not just compliant on paper, but genuinely capable of supporting AI adoption, protecting customer data, and managing regulatory risk.


The Currency Problem — Why Experience Dates Faster in Technology

There is a dimension of technology governance that is unique among board competencies: the rate at which expertise becomes obsolete.

A director with deep experience in financial governance, M&A, or operational strategy brings expertise that remains largely relevant across decades. The principles of sound financial governance do not change fundamentally from year to year. The frameworks for evaluating M&A transactions are durable. The disciplines of operational excellence are transferable across time.

Technology expertise does not work this way. The director who led a major ERP implementation in 2010 has experience that is of limited relevance to governing an Agentic AI deployment in 2026. The director who oversaw a cloud migration in 2015 — when lift-and-shift was the dominant approach and hyperscaler pricing models were simpler — has a mental model of cloud transformation that may actively mislead their governance of a modern cloud programme.

This is not a criticism of those directors. It is a structural feature of technology governance that nomination committees and boards need to explicitly account for.

The implication is that technology governance capability on a board requires active maintenance — not just initial recruitment. Directors with technology governance responsibilities need to invest continuously in staying current: engaging with practitioners, attending technology governance forums, reading beyond the board papers they receive, and building independent networks that give them access to perspectives beyond management's.

Boards that treat technology governance as a static credential — recruit a technology director, tick the box, move on — will find that their technology oversight capability degrades over time, even as the technology decisions they are being asked to govern become more consequential.


What Nomination Committees Should Be Asking

The practical implication of this analysis is that nomination committees need to ask more precise questions when assessing technology governance capability — both in director recruitment and in annual board effectiveness reviews.

For director recruitment:

For board effectiveness reviews:


The Broader Principle — Governance Precision as a Board Responsibility

The argument I am making about technology governance is an instance of a broader principle: board skills matrices are most valuable when they are honest rather than comprehensive.

A skills matrix that ticks every box but does not accurately represent the depth and currency of the capabilities it claims provides false assurance. It tells the nomination committee, the shareholders, and the regulators that the board has the governance capability it needs — when in fact it has the appearance of that capability without the substance.

In technology governance, the cost of that false assurance is rising every year. The decisions being made about AI adoption, cloud investment, data strategy, and digital business models are among the most consequential strategic decisions organisations are making. The regulatory environment is tightening. The pace of change is accelerating. The consequences of inadequate oversight are becoming more visible and more costly.

A more nuanced approach to technology governance in board skills matrices is not a nice-to-have. It is a governance responsibility — to shareholders, to regulators, to customers, and to the long-term health of the organisations boards are entrusted to oversee.

The checkbox was never enough. In 2026, it is genuinely insufficient.


Raviprasad Bangalore is Senior Vice President & Head of Technology at Comviva (Tech Mahindra), recognised among India's Top 10 AI Trailblazers by ET India. He has built and governed Agentic AI platforms at production scale, led cloud transformation programmes across Fortune 500 enterprises, and managed technology portfolios exceeding $125M. He advises boards and enterprises on technology governance, AI oversight, and enterprise technology strategy.