Technology governance is no longer an IT responsibility. It is an enterprise governance responsibility. 

Technology increasingly determines how companies acquire customers, operate, allocate capital, manage risk, protect data and create competitive advantage. 

Yet many boards still approach technology primarily through budgets, projects and cybersecurity incidents.

That is no longer enough.

Technology decisions increasingly influence revenue, customer experience, operating models, capital allocation, regulatory compliance, resilience and reputation.

Artificial intelligence is accelerating this shift further.

Boards do not need to become technical experts. But they do need enough technology fluency to understand the strategic choices management is making, the assumptions behind them, the risks they create, and the governance mechanisms required to oversee them.

My own career across banking, technology and enterprise transformation has reinforced this view.

The question for boards is therefore not:

“Do we have enough technology expertise?”

It is:

“Do we have enough technology understanding to exercise effective oversight?”

Why Technology Governance Has Become a Board Issue

At one point, a technology failure was primarily an IT problem.

A server went down.

A system stopped working.

A software implementation was delayed.

The technology team fixed it.

That world has largely disappeared.

Today, a technology failure can mean:

A customer cannot transact.

A financial institution cannot serve clients.

Sensitive data is compromised.

A supply chain stops.

A regulatory obligation is missed.

An algorithm makes a flawed recommendation.

A cyberattack disrupts operations.

A digital transformation consumes significant capital without delivering expected benefits.

In other words, technology risk has become business risk.

This has important implications for boards.

If technology affects strategy, capital allocation, customers and resilience, then technology governance cannot remain solely a management or IT responsibility.

My Technology Journey Shaped This Perspective

My perspective on technology governance comes from having spent a significant part of my career on both sides of the technology-business boundary. 

At Polaris and HCL Technologies, I worked at the intersection of business requirements and technology, including banking and wealth-management technology.

At Wipro, I built an 80-member specialist testing organisation and worked across testing, banking and financial-services technology, business requirements and pre-sales.

Later, at Franklin Templeton, I moved into senior leadership across Technology, Operations, Business Excellence and Transformation.

I established and led a 65-member Centralised Testing Services organisation, one of the firm’s global testing organisations.

The work exposed me to something that I believe boards need to appreciate:

Technology projects rarely fail because the technology exists.

They fail because the business problem was poorly defined, assumptions were wrong, implementation was weak, adoption was inadequate, risks were underestimated, or accountability was unclear.

That is a governance issue.

Five Questions Every Board Should Ask About Technology

1. What Business Problem Are We Solving?

This sounds obvious.

It isn’t.

Organisations can become attracted to technology because it is new, fashionable, or because competitors are adopting it.

The board should ask:

What problem are we solving?

How material is that problem?

What happens if we do nothing?

What measurable business outcome are we expecting?

This is particularly important with AI.

“Everyone is adopting AI” is not a strategy.

A board should expect management to explain where AI creates measurable value.

2. What Value Are We Expecting From the Investment?

Every major technology investment contains assumptions.

Customer adoption.

Productivity improvements.

Cost savings.

Revenue growth.

Implementation timelines.

Data quality.

Vendor performance.

Employee capability.

The board does not need to validate every assumption.

But it should understand the assumptions that could materially change the business case.

A ₹100 crore technology investment based on optimistic adoption assumptions deserves far more scrutiny than a routine technology upgrade.

The board’s role is not to second-guess management.

It is to ensure that material assumptions are visible.

3. Who Owns the Risk and the Outcome?

One of the most common mistakes in technology transformation is confusing project ownership with business accountability.

The CIO may own implementation.

The technology team may own the platform.

The vendor may own delivery.

But who owns the business outcome?

If the objective is improved customer retention, someone in the business must own customer retention.

If the objective is lower operating cost, someone must own the cost outcome.

If AI is being used in decision-making, accountability for the final decision must remain clearly established.

Technology governance becomes much stronger when accountability is unambiguous.

4. What Happens When the Technology Fails?

Boards should spend more time discussing failure scenarios before approving major technology initiatives.

What if the model produces inaccurate outputs?

What if the vendor fails?

What if the data is incomplete?

What if a cyberattack occurs?

What if employees misuse the system?

What if the implementation takes twice as long?

What if the expected savings do not materialise?

What is the business continuity plan?

This is where technology governance meets enterprise risk management.

The objective is not to eliminate technology risk.

That is impossible.

The objective is to ensure that the organisation understands the risk, has appropriate controls and knows what it will do when something goes wrong.

5. How Will the Board Know Whether It Is Working?

Technology projects often generate dashboards full of activity metrics.

Number of users.

Systems migrated.

Modules implemented.

Tickets closed.

Milestones achieved.

But activity is not necessarily impact.

The board should ask for measures that demonstrate business value.

Has customer experience improved?

Has productivity improved?

Has risk been reduced?

Has revenue increased?

Has cost declined?

Has resilience improved?

Has the investment delivered the expected return?

The board needs enough visibility to distinguish progress from actual outcomes.

AI Governance Creates New Board Responsibilities

Artificial intelligence is changing the technology governance conversation.

AI can influence advisory, customer engagement, risk management, fraud detection, compliance, cybersecurity and operational decision-making.

That creates a new governance question:

Where should an organisation allow technology to support judgement, and where should humans retain final decision authority?

This is particularly important in regulated sectors.

Regulatory direction is increasingly placing responsibility on regulated entities for areas such as the accuracy and appropriate use of AI outputs, data protection, and compliance.

For boards, that means AI governance cannot simply be delegated to the technology department.

Boards should understand:

• where AI is being used,
• what decisions it influences,
• what data it relies upon,
• what controls exist,
• how outputs are validated,
• who is accountable,
• and what happens when the system is wrong.

The board does not need to understand the mathematics behind an AI model.

It needs to understand the business and governance consequences of using it.

Technology Fluency Is Different From Technical Expertise

This distinction matters.

A board does not need five technologists.

Nor does every Independent Director need to understand software architecture.

But the board collectively needs sufficient capability to challenge management intelligently.

Technology fluency means being able to ask:

Why this technology?

Why now?

What value will it create?

What are the material risks?

What dependencies are we creating?

What happens if the technology fails?

Who is accountable?

How will we know whether the investment worked?

These are business questions.

And that is precisely why they belong in the boardroom.

What My Transformation Experience Taught Me

My years in enterprise transformation reinforced another important lesson.

Successful transformation requires alignment between four things:

Strategy. Technology. People. Governance.

Ignore strategy, and technology becomes an expensive experiment.

Ignore people, and adoption fails.

Ignore governance, and risks accumulate.

Ignore technology, and the strategy may become impossible to execute.

The board therefore has an important role in looking across these dimensions rather than examining them independently.

A technology committee may examine systems.

An audit committee may examine controls.

A risk committee may examine cyber risk.

Management may own transformation.

But the board must ultimately see the connections.

The Board’s Role Is Changing

The traditional question was:

“Do we have adequate IT controls?”

The more relevant questions today are:

“Is technology helping execute our strategy?”

“Are we creating new concentrations or dependencies?”

“Are we allocating capital appropriately?”

“Are we prepared for technology disruption?”

“Are we governing AI responsibly?”

“Do we have the organisational capability to execute?”

That is a much broader conversation.

It moves technology governance from the IT agenda to the enterprise strategy agenda.

My View

After three decades across financial services, technology, transformation and entrepreneurship, I have come to believe that technology governance is ultimately about decision quality.

Boards do not need to become technologists.

They need to become better technology-informed decision-makers.

The best technology governance is not about slowing innovation down.

It is about making innovation more deliberate.

It asks whether the organisation understands what it is building, why it is building it, what could go wrong and how success will be measured.

And perhaps most importantly, it ensures that accountability does not disappear behind the technology.

Technology may make the decision faster.
It may make the decision better.
But governance must still make clear who owns the decision.

Ultimately, effective technology governance is not about slowing innovation. It is about improving the quality of board-level decisions around technology, risk, investment and long-term value creation. 

How do you think boards should balance technology innovation with governance and risk oversight?