The Executive Five-Year Agenda

Leadership teams need a forward view that is concrete enough to guide action but flexible enough to survive technical, regulatory, and market change. Over the next five years, the decisive issue will not be whether organisations can access AI tools at all. It will be whether they can turn scattered access into governed capability.[2], [3], [16], [17], [23], [24], [40]

That is now visible across contexts. NIST frames AI as a lifecycle governance issue rather than a one-time procurement decision.[2], [3] OECD work shows adoption gaps, implementation weakness, and the continuing importance of compute, skills, procurement, and institutional capacity.[16], [17], [23], [24] The practical consequence is that a serious five-year agenda has to answer two questions at once:

  • what must we do now to stop unmanaged AI use from creating avoidable exposure?
  • what capabilities must become durable by the end of the period?

The most useful way to read this chapter is through six questions:

  1. What should leadership teams do in the next 12 months?
  2. What has to become real in the next 24 months?
  3. How should AI investment be judged over a five-year window?
  4. What capabilities must become durable?
  5. How should the agenda change across leadership contexts?
  6. What should boards and executive teams expect to see if the agenda is working?

1. What Should Leadership Teams Do In The Next 12 Months?

The immediate objective is not to become an AI leader in every domain. It is to establish visibility, control, and a minimum evidence standard before AI use spreads faster than oversight.

In the next 12 months, most leadership teams should:

  • build or refresh an AI inventory that includes material tools, workflows, vendors, and owners
  • classify systems by use case, consequence of failure, and dependency profile
  • stop unmanaged adoption in sensitive workflows and define clear restrictions on unsanctioned use
  • name accountable owners for material AI systems and escalation routes for incidents or overrides
  • define minimum evidence requirements before wider rollout, including testing, review, and monitoring
  • set a reporting rhythm for board, executive, or equivalent oversight review

This phase is about visibility, containment, and decision discipline. The point is not to create a perfect governance architecture in year one. It is to stop the organisation from being surprised by its own AI use.

2. What Has To Become Real In The Next 24 Months?

Once the organisation has visibility and basic controls, the next priority is to make AI repeatable as a managed capability rather than a sequence of disconnected pilots. This is where many organisations stall.[2], [23]

In the next 24 months, management should focus on:

  • standard approval and escalation processes rather than ad hoc exception handling
  • stronger vendor governance, contract discipline, and change-notification rights
  • active monitoring for drift, incidents, complaints, overrides, and material context changes
  • clearer data-readiness, traceability, and documentation practices
  • targeted capability building in business, operations, and oversight functions, not only technical teams
  • use-case prioritisation tied to measurable economic, service, research, or institutional value

This phase is about moving from experimentation to governable scale. If the organisation cannot show how it reviews changes, tracks incidents, and pauses weak systems, it is not scaling capability. It is scaling exposure.

3. How Should AI Investment Be Judged Over A Five-Year Window?

AI spending should be judged with the same discipline as other strategic investments, but with a broader cost lens than many teams apply at pilot stage.

Leadership should expect investment cases to include:

  • model and platform access cost
  • infrastructure and deployment cost
  • integration and workflow redesign cost
  • monitoring, review, and governance cost
  • vendor dependency and exit cost
  • obsolescence risk if providers close capability gaps quickly
  • realistic assumptions about adoption, error reduction, and measurable value creation

This matters because AI can appear inexpensive when only the software line item is counted. The real economic question is whether the organisation creates enough value after infrastructure, oversight, and change costs are included. For countries and large systems, the same logic extends to compute, energy, cloud concentration, and trusted-access dependencies.[24], [55]

Agenda View

Time Horizon Leadership Question What Good Looks Like
12 months Can we see and control the AI that already matters? Inventory, ownership, basic restrictions, and evidence rules exist
24 months Can we operate AI as a managed capability rather than a pilot portfolio? Approval, monitoring, escalation, and vendor discipline are repeatable
Five years Are we building durable institutional strength rather than temporary momentum? Capability survives staff change, vendor change, and market change
Investment logic Are we counting the full cost of governable AI use? Spending cases reflect integration, oversight, and dependency cost

4. What Capabilities Must Become Durable?

Over a five-year horizon, the competitive question shifts. The issue is no longer whether the organisation can use AI at all. The issue is whether it can build durable capability while maintaining trust, legitimacy, and strategic room to maneuver.

Leadership teams should aim to build:

  • a repeatable governance operating model
  • a credible internal evidence standard for higher-impact systems
  • stronger resilience against vendor concentration and opaque dependencies
  • organisational capability to redesign work around AI rather than merely layer tools on top
  • a differentiated position based on trust, reliability, and disciplined execution
  • institutional ability to stop, replace, or redirect systems when the external environment changes

This phase is about institution building, not just technology adoption. Over a five-year window, strong organisations become easier to distinguish from weak ones. Strong organisations can explain where AI is used, why it is there, who owns it, how it is monitored, and what dependencies it creates. Weak organisations mostly have pilots, vendors, and slide decks.

5. How Should The Agenda Change Across Leadership Contexts?

The five-year horizon is the same across contexts. The governing problem is not.

  • SMEs should focus on a short list of durable workflow gains, safe vendor use, explicit data-handling rules, and enough internal competence to challenge supplier claims.[16], [17]
  • Cooperatives and mutuals should build governance that preserves member legitimacy as well as operational efficiency.[18]
  • Research institutions should normalize AI-assisted research without weakening disclosure, reproducibility, or data protection.[19], [20]
  • Large enterprises should reduce unmanaged adoption, build reusable governance and platform layers, and concentrate investment where scale or differentiation is real.[2], [3]
  • Public-sector institutions should prioritize lawful service redesign, procurement maturity, implementation capacity, and movement out of pilot limbo into governable operations.[21], [22], [23]
  • National leadership should treat the period as a capacity-building window across talent, research, compute, cloud, public-sector use, resilience, and security.[24], [25]

In each setting, the right five-year plan is the one that strengthens capability without accepting hidden dependency or avoidable loss of control.

6. What Should Boards And Executive Teams Expect To See If The Agenda Is Working?

Boards and executive committees should expect recurring attention in four areas:

  • material AI risk exposure
  • major deployments and use-case expansion
  • incidents, complaints, and remediation
  • strategic capability gaps in data, talent, governance, or vendor dependence

The board does not need to manage AI directly. It does need confidence that management can see the real exposure, challenge weak assumptions, and intervene when AI use outpaces control.

By the end of a credible five-year agenda, the organisation should be able to say:

  • we know where AI is used
  • we know which uses matter most
  • we know who is accountable
  • we can show what evidence supports deployment
  • we can slow, pause, or stop systems when the context changes
  • we understand which external dependencies we have chosen and why

That is the difference between AI ambition and durable AI capability.

Final Perspective

The executive agenda should balance urgency with discipline. Waiting too long creates strategic weakness. Moving too fast without evidence, governance, organisational readiness, or infrastructure realism creates avoidable exposure.

After reading this chapter, a leadership team should be more disciplined in four ways:

  • focus the first year on visibility, control, and minimum evidence
  • use the next two years to make approval, monitoring, and oversight repeatable
  • judge investment through full-system cost, not tool price alone
  • treat the five-year horizon as institution building rather than technology theater

The practical change is to stop asking what is our AI strategy? as if it were a slide deck question and start asking what capabilities will still be visible, governable, and useful five years from now?

Key Questions for Leaders

  • What should we do in the next 12 months that will still matter in five years?
  • Which capabilities must become durable internal strengths?
  • Which dependencies are we accepting today that may constrain us later?
  • Where do we need board-level or equivalent oversight now rather than later?
← AI Across Leadership Contexts Next: Appendix A →
This site uses Just the Docs, a documentation theme for Jekyll.