Boards are receiving more proposals for AI and digital transformation than ever. Most come with business cases, risk registers, and governance frameworks. Yet leadership teams often leave the room without a shared picture of what success looks like for the people whose work will change, how confidence will be built among those affected, or whether the initiative fits the organisation's actual capacity and culture.

The gap is not usually negligence. It is that board-level oversight questions are often framed around controls, timelines and financial return. These matter. But they miss the threads that determine whether a programme delivers real value, holds the trust of the people who will use it, and actually fits how the organisation works.

The VTA Framework offers boards a clearer lens. Value, Trust and Alignment are not alternatives to financial rigour or risk management. They are the questions that sit underneath them, shaping whether a programme will land as intended or become another well-intentioned initiative that stalls.

Value: for whom, and is there a meaningful reason to act?

Boards typically review the business case: cost savings, revenue uplift, efficiency gains. These are important. But a sharper question is: value for whom? A digital transformation that cuts process time by 30 per cent creates value for finance and operations. Does it create value for the customer-facing team whose role changes, or the person whose work pattern shifts entirely?

This matters because when value is distributed unevenly, trust fractures. A team that experiences a programme as adding complexity or surveillance rather than support will resist it, slow it, or leave. The hidden cost is often higher than the forecast saving.

Boards should ask: Who benefits from this programme? Who might experience it differently? Are there people for whom this programme creates burden rather than relief? And crucially: have we asked them?

Justice and fairness are embedded in this lens. If a programme concentrates benefit at the top and risk at the bottom, or if the people most affected have had no say in the design, the board is signing up for implementation failure disguised as a project plan.

Trust: how will the people affected understand and place confidence in this?

Trust is not the same as communication. A well-resourced change management plan can deliver information without building confidence. Trust emerges when people understand not just what is changing, but why; when they see that their concerns are heard; and when they experience the change as transparent and fair.

For AI and digital programmes, trust is particularly fragile. If a system is introduced as efficiency-driven without clarity about how decisions will be made, what happens to roles, or how fairness is being built in, suspicion runs deep and fast. People will assume the worst if the best case is not made explicit and credible.

Boards should ask: Who needs to trust this programme, and why might they not? What would shift their confidence? Have we planned for the people who will be sceptical, not just the early adopters? Do the people who will live with this change every day know they have been heard?

Equity and fairness are at the heart of this question. If trust is being built selectively (with unions, with senior teams, but not with frontline staff), or if communication happens after decisions are made, the board is fragmenting the organisation rather than moving it forward together.

Alignment: does this fit the organisation's reality, people, workflows, systems, data, capability and governance?

Many programmes fail not because the idea is wrong but because it does not align with how the organisation actually works. A new system might be excellent in isolation but crash when it meets legacy infrastructure, competing priorities, or cultural norms that were not captured in the business case.

Alignment is also about people and governance. A programme that demands new skills but offers no learning; that changes roles but does not address what happens to those whose roles shrink; that introduces new decision-making authority but does not clarify who is accountable: these programmes create confusion that slows delivery and damages morale.

Boards should ask: Have we mapped this against our actual infrastructure, data landscape, and skill base, not the version we wish we had? Does this programme fit our governance structure or does it create parallel authority? Are roles and accountability clear, and have we addressed what happens to people whose work changes fundamentally?

Alignment must also surface whose needs are being met. A programme aligned with finance systems and executive dashboards but misaligned with frontline workflows creates daily friction. A programme designed for one division but imposed on another without adaptation will fail. Asking aligned with whose needs keeps the board honest about whether this is a solution or a mandate.

Bringing it together: the board's role

Boards do not need to become programme managers. They do need to ask the questions that reveal whether a programme is built on solid ground. Value, Trust and Alignment offer a framework for that conversation. They sit alongside, not instead of, financial oversight and risk management. They deepen it.

When a board asks "what is the value for the customer-facing team whose role is changing?", it often surfaces that implementation planning has assumed adoption without designing for it. When it asks "what would shift trust for the people who are sceptical?", it often reveals that communication happens after go-live, not before. When it asks "is this aligned with how we actually work?", it often uncovers mismatches between the business case and the operating model.

These are not soft questions. They are the ones that distinguish programmes that deliver from programmes that consume resources and disappoint.

The board's oversight role is to ensure that leadership teams have thought clearly about these threads before money and attention are committed. It is to surface where Value, Trust and Alignment diverge, and to ask what that means for feasibility and risk. It is to ensure that the people whose work will change have been part of thinking about whether this programme is just, equitable and fair as well as efficient.

None of this requires the board to become expert in digital or AI. It requires clarity on what clarity looks like, and the willingness to ask for it.