The US$4.5 Million Programme That Nobody Governed

The board of a Caribbean conglomerate with operations in financial services, hospitality, and real estate approved a US$4.5 million digital transformation programme in March. The programme was ambitious: replace the group’s legacy ERP system with a cloud-based platform, implement a customer-facing digital portal for the financial services subsidiary, deploy business intelligence dashboards for all three business units, and build a centralised data warehouse. The timeline was twenty-four months. The business case projected annual savings of US$1.8 million from process automation and improved decision-making.

The board approved the programme on the basis of a twelve-page presentation delivered by the group’s chief information officer. The presentation contained the project scope, a high-level timeline, the investment requirement, and the projected benefits. It did not contain a detailed risk assessment. It did not identify the dependencies between the four workstreams. It did not describe the change management approach for the 340 employees whose daily workflows would be affected. And it did not define the governance structure that would oversee the programme’s execution.

The board’s approval resolution was brief: “The Board approves the Digital Transformation Programme as presented, with a total investment of US$4.5 million over twenty-four months, to be overseen by the CIO with quarterly progress reports to the Board.”

Eighteen months later, the programme was in crisis. The ERP implementation was eleven months behind schedule. The original vendor had been replaced after a contract dispute at month eight, requiring a restart of the configuration and data migration work. The customer portal had been launched but had experienced three significant outages in its first six weeks, eroding customer confidence. The business intelligence dashboards had been delivered for the financial services subsidiary but not for hospitality or real estate, whose data had proved far more difficult to integrate than anticipated. And the data warehouse project had been quietly descoped to a “future phase” that had no timeline or budget.

The total spend was US$5.2 million — fifteen per cent over the approved budget — with approximately forty per cent of the originally scoped functionality delivered. The projected US$1.8 million in annual savings had not materialised. Staff morale in the finance and operations teams, who had endured months of parallel processing during the troubled ERP migration, was at its lowest point in a decade. And the CIO, who had been the sole point of accountability for a programme that was too large and too complex for any single individual to govern, had resigned.

The board chair’s post-mortem assessment was characteristically direct: “We approved four and a half million dollars on the basis of a twelve-page presentation. We appointed no steering committee. We defined no milestones. We established no independent assurance over the programme. We received quarterly updates that told us what had been done but not whether it was on track. And when the programme went off the rails, we had no mechanism to detect it until the CIO told us — by which time it was too late to prevent the overruns. We did not govern this programme. We funded it and hoped for the best.”

This fictional scenario, while not attributable to any specific Caribbean conglomerate, reflects a governance failure that Dawgen Global encounters repeatedly across the region. Caribbean boards approve significant technology investments without establishing the governance structures, the oversight mechanisms, and the assurance processes that complex technology programmes require. The result is programmes that exceed budgets, miss timelines, deliver incomplete functionality, and fail to realise the business benefits that justified the investment.

Why Technology Programmes Fail Without Board Governance

Technology transformation programmes are among the highest-risk investments a Caribbean enterprise can make. They are complex, cross-functional, dependent on external vendors, subject to scope change, and disruptive to the organisation’s operations during implementation. Without adequate governance, the risks compound.

Scope Creep and Scope Collapse: Without governance to manage scope, technology programmes either expand beyond their original boundaries as stakeholders add requirements, or collapse as features are quietly descoped to manage timeline and budget overruns. The conglomerate’s data warehouse was descoped not because it was no longer needed but because the programme could not absorb the cost and complexity within the remaining budget. Governance mechanisms — formal change control, scope baseline management, and board-level approval for significant scope changes — prevent both creep and collapse.

Vendor Dependency and Vendor Failure: Caribbean enterprises frequently depend on a small number of technology vendors and system integrators. When the vendor relationship fails — as it did in the conglomerate’s ERP implementation — the programme suffers delays and cost overruns that can be catastrophic. Governance mechanisms that include vendor performance monitoring, contractual protections, and contingency planning for vendor failure reduce the enterprise’s exposure to vendor dependency risk.

Change Management Neglect: Technology transformation programmes succeed or fail based on whether the people who must use the new systems are prepared, trained, and supported through the transition. The most technically successful implementation will fail if the users resist it, work around it, or revert to the old processes. Governance structures that include change management oversight ensure that the human dimensions of transformation receive the same attention as the technical dimensions.

Benefit Realisation Failure: The business case for technology investment typically projects specific benefits: cost savings, revenue growth, efficiency improvements, or risk reduction. Without governance that tracks benefit realisation against the business case, the enterprise may complete the technology implementation without achieving the benefits that justified the investment. The conglomerate’s projected US$1.8 million in annual savings had not materialised because nobody was tracking whether the operational changes needed to capture the savings had been implemented.

The Board’s Role in Technology Governance

The board’s role in technology governance is not to manage the technology programme — that is management’s responsibility. The board’s role is to ensure that the governance framework exists, that it is functioning, and that the board receives the information it needs to fulfil its oversight responsibility.

Strategic Alignment: The board should satisfy itself that the technology strategy is aligned with the enterprise’s business strategy. Technology investment should be driven by business objectives — the specific operational improvements, customer experience enhancements, risk reductions, or competitive advantages that the technology is intended to deliver. The board that approves a technology programme without understanding the business outcomes it is designed to achieve cannot assess whether the programme is succeeding.

Investment Governance: Significant technology investments should be subject to the same governance rigour as any other major capital allocation decision. The business case should be detailed, the assumptions should be stress-tested, the risks should be identified and mitigated, and the approval should include defined milestones at which the board will assess progress and decide whether to continue, adjust, or terminate the investment. The conglomerate’s twelve-page presentation and single approval resolution were inadequate for a US$4.5 million investment.

Programme Governance Structure: The board should ensure that significant technology programmes are governed by a steering committee that includes senior business leaders, not only IT personnel. The steering committee should meet regularly, receive detailed progress reporting, manage scope and change control, oversee vendor relationships, and escalate issues to the board when they exceed the committee’s authority to resolve. The conglomerate’s decision to assign sole oversight to the CIO created a single point of failure that governance by committee would have prevented.

Risk Oversight: Technology programmes carry specific risks that the board should understand and monitor: implementation risk (the programme may not be completed on time or within budget), technology risk (the selected technology may not perform as expected), integration risk (the new systems may not integrate with existing systems), security risk (the new technology may introduce vulnerabilities), and adoption risk (users may not adopt the new systems). The board should receive reporting on these risks and their mitigation throughout the programme.

Independent Assurance: For significant technology investments, the board should consider engaging independent assurance over the programme’s governance, execution, and benefit realisation. Independent assurance — provided by a qualified technology advisory firm that is independent of the programme’s management and vendors — gives the board an objective assessment of whether the programme is on track and whether the governance mechanisms are functioning effectively. The audit series documented the value of independent assurance; the same principle applies to technology investment oversight.

Benefit Realisation Tracking: The board should require that the business case benefits are tracked and reported against actuals throughout the programme and for a defined period after implementation. Benefit realisation tracking holds management accountable for delivering the outcomes that justified the investment and provides the board with evidence of whether the technology investment is creating the value it promised.

The Technology Governance Framework for Caribbean Boards

Technology Strategy Review: The board should review and approve the enterprise’s technology strategy at least annually, assessing its alignment with business strategy, the adequacy of technology investment, the progress of in-flight technology initiatives, and the emerging technology risks and opportunities. The technology strategy review should be a substantive agenda item, not a perfunctory update.

Investment Approval with Stage Gates: Significant technology investments should be approved with defined stage gates — predetermined milestones at which the board reviews progress, reassesses the business case, and decides whether to proceed to the next phase. Stage-gate governance prevents the sunk cost fallacy — the tendency to continue investing in a failing programme because of the money already spent — by creating formal decision points at which termination or redirection is an explicit option.

Steering Committee with Business Leadership: Every significant technology programme should have a steering committee chaired by a senior business leader, not the CIO. The committee should include representatives from the business units affected by the programme, the finance function, and the IT function. The committee’s mandate should include scope management, vendor oversight, change management, risk management, and benefit realisation tracking.

Regular Board Reporting: Technology programme reporting to the board should be structured, quantitative, and exception-based. The reporting should include progress against milestones, budget variance, risk status, vendor performance, change management progress, and benefit realisation tracking. The board should receive this reporting at least quarterly for major programmes, with provisions for interim reporting when significant issues arise.

Post-Implementation Review: After significant technology implementations, the board should require a post-implementation review that assesses whether the programme delivered the scope, the timeline, and the budget that were approved, whether the projected benefits are being realised, what lessons were learned, and what residual risks remain. The post-implementation review closes the governance cycle and informs the enterprise’s approach to future technology investments.

Board Digital Competence

Effective technology governance requires that the board has sufficient digital competence to exercise informed oversight. This does not mean that every director needs to be a technology expert. It means that the board as a whole should have the capability to understand the strategic implications of technology decisions, to ask the right questions about technology risk and investment, and to evaluate the quality of the information it receives about technology programmes.

Board Composition: Caribbean boards should consider whether their composition includes directors with relevant technology experience. A director who has led or overseen significant technology implementations, who understands cloud computing, cybersecurity, and data governance, and who can challenge technology proposals with informed questions adds substantial value to the board’s technology governance capability.

Director Education: Boards should invest in director education on digital transformation, cybersecurity, and technology governance. The Caribbean Institute of Corporate Directors and similar professional bodies offer governance programmes that include technology oversight dimensions. Directors who understand the fundamentals of digital transformation are better equipped to govern it.

External Advisory: Boards that lack internal technology competence should consider engaging external technology advisors who can attend board meetings, review technology proposals, and provide the independent perspective that enables informed governance. The cost of external advisory is negligible compared to the cost of governing a multimillion-dollar technology programme without adequate expertise.

Dawgen Global’s Technology Governance Advisory

Dawgen Global’s Technology Governance Advisory helps Caribbean boards and executive teams establish the governance frameworks that significant technology investments require.

Technology Governance Framework Design: Dawgen Global designs technology governance frameworks tailored to the enterprise’s size, complexity, and technology investment profile. Our frameworks include investment approval processes, steering committee structures, reporting templates, stage-gate mechanisms, and benefit realisation tracking.

Programme Assurance: Dawgen Global provides independent assurance over in-flight technology programmes, assessing governance effectiveness, programme health, vendor performance, risk management, and benefit realisation. Our assurance reports provide the board with an objective, independent view of whether the programme is on track.

Board Digital Education: Dawgen Global delivers board education sessions on digital transformation governance, cybersecurity oversight, and technology risk management, designed to build the board’s collective competence in technology governance.

Post-Implementation Review: Dawgen Global conducts post-implementation reviews of completed technology programmes, assessing scope delivery, budget performance, benefit realisation, and lessons learned. Our reviews close the governance cycle and inform future investment decisions.

CIO and Technology Leadership Advisory: Dawgen Global advises enterprises on the design of the technology leadership structure, including CIO role definition, technology team capability assessment, and the relationship between the technology function and the board.

Govern the Investment or Govern the Failure

The fictional conglomerate that spent US$5.2 million on a digital transformation programme delivering forty per cent of the scoped functionality did not experience a technology failure. It experienced a governance failure. The technology was available. The vendors were capable. The business case was sound. But the governance structures that should have ensured the programme’s success — the steering committee, the stage gates, the risk oversight, the change management, the independent assurance, and the benefit tracking — were never established.

The board approved the investment and then delegated everything to a single individual who was asked to manage a programme that was too large, too complex, and too consequential for any one person to oversee. When the programme failed, the board discovered that it had no mechanism to have detected the failure earlier, no framework to have intervened when intervention could have changed the outcome, and no basis for understanding what had gone wrong.

Caribbean boards that approve significant technology investments have a choice: govern the investment proactively, with the structures, the oversight, and the assurance that complex programmes require, or govern the failure retrospectively, in the post-mortem that explains why the investment did not deliver what it promised. The governance costs a fraction of the investment. The failure costs far more than the governance would have.

Govern Your Digital Transformation

Dawgen Global invites Caribbean boards and executive teams to assess the governance of their technology investments and establish the frameworks that protect the enterprise’s investment and ensure that digital transformation delivers its promised value.

Request a proposal for Dawgen Global’s Technology Governance Framework and Programme Assurance services. Email [email protected] or visit www.dawgen.global to begin the conversation.

DAWGEN GLOBAL | Big Firm Capabilities. Caribbean Understanding.

Request a proposal for Dawgen Global’s Technology Governance Framework and Programme Assurance services.

Email: [email protected]

Web: www.dawgen.global

About Dawgen Global