A board has limited time and a specific job. It doesn't approve tools or vendors; it approves direction, investment and risk, and it holds named people to account for results. A 40-slide AI deck works against that job. It buries the decision under background, invites a debate about methodology, and lets the presenter avoid choosing. A one-page AI strategy forces the choices to be made before the meeting, and gives the board something it can read in five minutes, challenge line by line and minute as agreed.

The format matters less than the discipline. One A4 page or one executive summary slide both work; what fails is a page so dense it is a deck in disguise. Lead with the answer, keep supporting detail in an appendix, and let the page say what the board is being asked to approve.

This course's standard one-pager has six sections, and each is fed by work you have already done. The AI ambition states, in one sentence, why AI matters to this organisation now; it draws on the readiness baseline from Module 1 and the sector profile from Module 7. The use-case portfolio lists the three to five initiatives you are backing, from the scorecard in Module 2. The investment plan gives the budget, its staging and the primary initiative's return, from the calculator in Module 3 and the waves in Module 4. Governance commitments come from the audit and charter in Module 5. People and culture summarises the change plan from Module 6. Success metrics name the three to five outcomes the board will see every quarter.

Keep the strategy distinct from a technical roadmap. A roadmap says how: which platform, which integration, which sprint. A strategy says what and why: where the organisation will compete with AI, what it will spend, what it won't do and how the board will know it is working. Product names, architecture diagrams and vendor logos belong in the roadmap; if they appear on the one-pager, the board will discuss them instead of the strategy.

A useful test for every line: could a director ask "so what are you asking us to decide?" and find the answer on the page? If a line informs but asks for no decision and supports no commitment, move it to the appendix.

The ambition statement is the first line a board reads, and often the only line it repeats afterwards. It is the strategic narrative in its shortest form: why AI matters for this organisation now. Most first drafts fail in one of two ways. Some are generic: "We will become an AI-first organisation" could be signed by any company in any sector, so it commits to nothing. Others are tool lists: "We will roll out Copilot, a chatbot and a churn model" describes a roadmap, not an ambition.

This course uses a three-part formula. Every ambition statement answers three questions in one sentence.

Why AI? Name the strategic context: the organisation's industry position and the specific challenge or opportunity that makes AI matter now. Your sector profile from Module 7 does most of this work. A sector scored as a Fast Follower, where competitors already compete on AI, has a different "why" from one scored as Data Builder, where the first job is capturing the data.

What kind of AI? Specify the primary AI type or application domain, using the classification from Module 1: predictive, generative or agentic, and the work it will be applied to. "Supervised generative AI for legal research" tells the board where the risk sits and who checks the output; "AI" tells it nothing.

What will it make possible? Commit to a measurable or observable outcome: something the success metrics will track and the board can test in a year. "Better client service" is a hope. "Three AI-enabled service lines in market by the end of 2027" is a commitment.

Write it, then test it three ways. Could a competitor sign it unchanged? If so, the context is too thin. Does it name a product or vendor? If so, it has slipped into roadmap language; product names change, and the ambition shouldn't. Could a director check in a year whether it has happened? If not, the outcome is too vague.

Keep it to one sentence of roughly 30 to 45 words. A longer statement usually hides two ambitions that haven't been reconciled. And keep it honest: if your readiness baseline shows the organisation at the start of its AI journey, the ambition should say where it is starting, not claim leadership it hasn't earned.

Meridian is a useful test case because one firm sits in three sectors. Its legal service line scored as a Fast Follower, financial advisory as Compliance-First and consulting as a Data Builder, so its ambition must lead with the line where competitive pressure is greatest without promising the other two more than their postures allow.

The scorecard you built in Module 2 may list a dozen candidates, each with four scores and a weighted total. The board needs three to five initiatives and the decision behind each. Compress, don't summarise: the scores, the parked ideas and the workshop notes go to the appendix; the table shows what you are backing.

Give each initiative five columns: name, AI type, horizon, value driver and status. Name the initiative by the work it changes, such as "legal research assistant", not by the product. Use the portfolio types from the use-case module for the horizon: quick wins, each deliverable in under six months; scale opportunities, which take six to eighteen months and usually depend on data work; and transform bets, 18 months or more away and funded only as bounded experiments. Tie each to one of the four value drivers: cost reduction, revenue growth, risk reduction or new capability. A row that names a technology but no value driver tells the board what you will buy, not what it will get.

The investment summary sits beside the table. State the total budget and its horizon, how spend is staged across the horizons, and what releases each stage: the go/no-go gate from Module 4. Then give the primary initiative's three numbers from your calculator in Module 3: net benefit, ROI and payback. Put the cautious case next to them. A very high return invites the question "what have you left out?", and the answer should already be on the page. Finally, state the sourcing decision, build, buy or partner, for at least the primary initiative, with its one-line reason.

Behind the one-pager sits a one-page appendix addressed to the CEO, who will be asked the follow-up questions. For each priority use case it gives the function, the job-to-be-done and the pain-point evidence from the user interviews in the functional implementation module, and a short business case: cost, benefit, ROI and payback. For Meridian's legal research assistant: legal; associates need to find and summarise relevant case law for a matter; each of 40 associates spends about six hours a week on research; £105K year-one cost against £675K annual benefit, a 543% ROI and 1.9-month payback. For the HR onboarding chatbot: HR; new joiners need straight answers to policy and IT questions; much of the HR team's week goes on answering the same ones, and interviews found two versions of the same leave policy.

Where a use case has no completed business case yet, say so and say when it will have one, before its wave's gate. An honest gap is defensible; an invented figure is not.

Governance commitments state four things. First, the regulatory classification of every system in the portfolio, by risk tier, with the date any obligations apply. Name the benchmark you use: a UK firm may choose the EU AI Act because some of its output is used in the EU, while remembering that the UK's own approach is principles-based. Second, the structure: who chairs the AI governance committee, who is the AI Risk Owner, and that each system has a named owner and sits on the AI register. Third, the responsible AI principles every deployment is tested against; this course uses fairness, transparency, accountability, privacy and reliability. Fourth, the data governance behind the priority use cases: who owns each data source, where the data comes from and whether you may use it this way, the quality standard it must meet, and how long inputs, outputs and logs are kept, including by vendors. Report status honestly. Your readiness audit from Module 5 shows what is done, what is partly done and what isn't; the one-pager commits to closing the gaps by a named point in the roadmap.

People and culture names the literacy programme, which tiers it covers and by when; the user champions; and the change timeline, from the 90-day plan built in Module 6 to the later waves. Say how many people the programme affects and what won't change for them: a specific answer builds more confidence than reassurance.

Success metrics are where most AI strategies are weakest. Choose three to five, each with a baseline, a target, a date and an owner, and report them to the board every quarter. Link every one to a business outcome. "Number of AI tools deployed" and "licences issued" are activity measures: both can rise while nothing improves. "Research hours per associate" or "cost efficiency achieved" can't. A people measure such as literacy completion can earn a place as a leading indicator, because adoption depends on it, but it shouldn't crowd out the outcomes.

Then check every target against your own plan. Meridian's legal research target, a 20% reduction by Q2 2027, means taking six hours a week to 4.8, well inside the modelled fall to 1.5, so it is a cautious and credible target. Its £500K cost-efficiency target sits between the legal assistant's cautious case of £337.5K a year and its expected £675K, so the board should hear how it will be counted: hours redeployed to client work and tracked through utilisation, not hours multiplied by a rate. A target the plan can't reach, or one that counts capacity as cash, is the first line a sceptical director will test.

Complete all six sections in the AI Strategy One-Pager Builder.