Board-Level Technology Illiteracy — The Governance Gap That Enron Made Impossible to Ignore
A non-executive director who cannot distinguish between a systems integration programme and an enterprise resource planning implementation is not equipped to challenge the executive team's technology investment decisions — and most boards today are populated with precisely such directors.
The Gap Nobody Wants to Name
The collapse of Enron has produced, predictably, a torrent of commentary about corporate governance, accounting standards, and the failure of oversight. Much of it is justified. But there is a dimension of the governance failure that has received almost no attention, and it is one that extends far beyond Enron to virtually every large organisation with a significant technology estate: the profound technology illiteracy of the people charged with overseeing executive decision-making.
I do not use the word “illiteracy” loosely. In my experience of working with and presenting to boards across multiple sectors, the level of technology understanding among non-executive directors is not merely low — it is so low that it renders a significant proportion of board-level oversight functionally meaningless. These are intelligent, experienced people. Many have distinguished careers in finance, law, or general management. But when a Chief Information Officer presents a business case for a major technology investment — or, more critically, when a programme reports that a complex systems implementation is “on track” — most board members lack the knowledge to ask the questions that would reveal whether they are being told the truth.
What Enron Actually Exposed
The Enron story is typically told as one of accounting fraud and conflicted interests, and those elements are real. But beneath the headline narrative lies a more structural problem. Enron’s board approved transactions, investment structures, and technology-enabled trading platforms that very few of its members understood in any technical depth. The special purpose entities that ultimately brought the company down were not simple financial instruments — they were complex, technology-dependent constructs whose risk profiles required a form of understanding that the board simply did not possess.
This is not unique to Enron. It is the normal condition of corporate governance in organisations where technology has become central to operations and strategy. The board approves technology investments it cannot evaluate, oversees technology programmes it cannot interrogate, and relies on executive assurances it cannot independently verify. The governance structure assumes a level of competence that does not exist.
The Structural Problem
The roots of this illiteracy are not difficult to trace. The generation of leaders currently occupying non-executive positions built their careers in an era when technology was a back-office function — something managed by a specialist department, relevant to operations but peripheral to strategy. The CIO, where the role existed at all, reported to the finance director and was concerned primarily with keeping systems running. Technology decisions were technical decisions, appropriately delegated to technical people.
That world has gone, but the composition of boards has not caught up. Technology now sits at the centre of competitive strategy, operational capability, and regulatory compliance. Major technology programmes represent some of the largest capital investments an organisation makes, and their failure rates are alarmingly high. Yet the people charged with overseeing these investments and challenging executive decisions about them are, in the main, the same people — or people with the same backgrounds — who learned to treat technology as someone else’s problem.
The board that cannot distinguish between a programme that is genuinely on track and one that is reporting green while heading for catastrophe is not governing — it is merely presiding.
The Consequences in Practice
The practical consequences of this gap are visible in every sector, though they are rarely attributed to their root cause. Technology programmes that should have been challenged at board level proceed unchecked, because the board lacks the vocabulary to frame its concerns. Business cases built on optimistic assumptions about systems integration, data migration, or organisational adoption pass through governance without serious scrutiny, because the assumptions are expressed in language that non-executive directors do not speak.
When programmes fail — and the failure rate for large-scale technology programmes remains stubbornly high — the post-mortem almost never identifies the board’s inability to provide meaningful oversight as a contributing factor. Instead, the failure is attributed to poor project management, inadequate requirements, or vendor underperformance. These may all be true, but they are symptoms. The underlying condition is a governance structure that was designed for a world in which the board understood the business activities it was overseeing.
The pattern I have observed repeatedly is this: a programme begins to drift. The early warning signs are there — scope ambiguity, integration challenges, stakeholder disengagement — but they are expressed in terms that require some technical literacy to interpret. The programme reports remain green, because the programme team understands that the board will not probe beneath the RAG status. By the time the problem becomes visible in language the board can understand — typically when costs escalate or deadlines slip beyond any plausible recovery — the opportunity for intervention has passed.
What Needs to Change
The current wave of governance reform, prompted by the Enron and WorldCom scandals, is focused almost entirely on financial controls, audit independence, and conflicts of interest. These are necessary reforms. But they will not address the technology governance gap, because they assume that the problem is one of integrity and process rather than competence.
What is needed is a more fundamental rethink of board composition and capability. This does not necessarily mean populating boards with technologists — the skills required for effective non-executive oversight are broader than technical expertise. But it does mean ensuring that every board includes members who can engage substantively with technology strategy, who can interrogate a programme business case with the same rigour that a financially literate director applies to a set of accounts, and who can recognise the early warning signs that a major technology investment is not delivering what was promised.
It also means changing the way technology is presented to boards. The current model — a quarterly update, heavy on acronyms and Gantt charts, light on business impact and risk — is designed for a board that is expected to receive and note rather than to challenge and decide. If boards are to provide genuine oversight of technology, they need information structured for decision-making, not for reassurance.
The Uncomfortable Truth
The uncomfortable truth is that most organisations know this gap exists and have chosen not to address it. Appointing a technology-literate non-executive director means acknowledging that the current board cannot adequately oversee a significant category of organisational risk. It means admitting that governance structures that appear robust — that satisfy regulators, that reassure shareholders — have a blind spot large enough to accommodate the kind of failures that destroy companies.
Enron has forced a conversation about governance that was long overdue. But if that conversation remains confined to financial controls and audit independence — if it does not extend to the competence of boards to oversee the technology-dependent strategies that now drive most large organisations — then the reforms will address yesterday’s failure while leaving tomorrow’s governance gap wide open.