The board meeting is tomorrow morning. Your slides are ready. The AI work is genuinely in progress. The team is engaged, the decisions have been sensible, and the vendors have delivered what they promised. What you do not have is a revenue figure to put in front of the room.
This is the most common position in a delegated AI mandate, and one of the most dangerous to handle badly. Reach for optimism you can’t back up and you’ve set a target you might not meet. Hedge into silence and the board loses confidence in the whole programme. Many delegates don’t find the third position until they’ve already spent some credibility. Report what is real, specifically and without apology.
What does reporting AI progress mean when results haven’t landed yet?
A standard board update assumes you’re reporting outcomes. When AI work is still in its first six months, outcomes aren’t ready. Reporting progress at this stage means showing the board what capability the team has built, what risks have been managed, and what leading indicators suggest the work is heading in the right direction. That is an honest update, and it is enough.
The mistake delegates make under pressure is reaching for financial projections to fill the gap. Projected ROI is not the same as trending ROI, and a board familiar with financial reporting will notice the difference. The Propeller research on measuring AI ROI draws a clear line between realised ROI, financial outcomes visible in the P&L, and trending ROI, early indicators that the programme is on track. Both are legitimate and reportable. In the first six months, only the second is available.
Scaled Agile’s research on what boards ask about AI identifies five areas they consistently probe, including strategic alignment, ROI measurement, risk management, and capability building. Trending ROI and capability evidence speak directly to most of those questions. Your board does not need a revenue figure to make a sound assessment. It needs enough information to judge whether the work is being run well.
Why does the framing of these early updates matter so much?
The way you frame the first few board conversations about AI sets the expectation standard every subsequent update will be measured against. Report confident projections in month two and they become targets by month four. An overstated early narrative can trap you as completely as a stalled pilot. Getting the framing right from the start protects your credibility for the months when the work is still earning its returns.
Spencer Stuart’s research on AI leadership notes that effective delegates develop their own understanding of the technology alongside running the programme. That depth is what lets them speak with authority to a board drawing its assumptions from vendor pitches and press coverage. Meaningful AI returns typically take twelve to twenty-four months from initial deployment, and stating that timeline plainly is accuracy rather than pessimism. A board that understands it is more likely to give the programme the space it needs.
EY’s research on AI governance finds that boards face significant investor pressure to be seen as acting on AI, which creates a hype-cycle gap between board-level expectation and operational reality. That gap lands squarely on whoever is communicating AI progress. Closing it early, with specific and accurate framing, is easier than managing the fall-out from a gap the board discovers on its own.
Where does the pressure for results come from, and what can you do with it?
In a founder-led business, pressure for AI results typically comes from two directions at once. The founder wants confirmation that the delegation was a sound decision. The board wants to see the competitive positioning they’ve read about in the financial press. Both pressures are real, but they are usually calibrated to the wrong timeframe, one driven by a need to justify the mandate and the other by the AI hype cycle.
BCG’s research on the AI adoption puzzle found that AI tool usage has risen substantially across organisations while commercial impact measurement consistently lags. The gap between activity and demonstrable commercial impact is a sector-wide pattern. Naming that pattern to the board reframes the conversation from why results haven’t appeared yet to what measurement infrastructure is needed to capture them.
The OECD’s 2025 research on AI adoption documents the same gap between tool deployment and measurable commercial return at comparable scale. When you name the pattern and show the board what measurement you have in place, you’re demonstrating that you understand how AI investments actually develop. A projected revenue figure with no data behind it is less reassuring than that.
When should you show trending ROI, and when should you hold it back?
Trending ROI covers early indicators that the work is pointing in the right direction. Time saved on specific processes, team adoption rates, accuracy gains on document-heavy tasks, reduction in manual errors on a targeted workflow. These are legitimate progress markers when tracked and verified against a baseline. Report them clearly as leading indicators, not as proxies for financial outcomes that are not there yet.
The dual-ROI framework keeps these two types of evidence in separate parts of the board update. Trending ROI sits in the are-we-on-track section. Realised ROI sits in the what-has-it-delivered section. In the early months, the second section carries a clear note. Financial results are expected from a stated quarter onwards, and here is what is being tracked to get there. Naming the timeline plainly builds more trust than optimism does.
Harvard Law’s analysis of AI risk disclosures in the S&P 500 finds that reputational risk is the top AI concern for a significant share of major companies. For a delegate in an owner-managed business, that risk is personal as much as it is commercial. Overstating early AI progress and having to walk it back six months later costs more credibility than a careful, specific early report ever would.
What should the early AI board update actually contain?
A credible no-results-yet report has three distinct sections, each with its own claim. Capability built covers what the team can now do that it could not at the start of the mandate. Risks managed covers the decisions made to keep the work legal, safe, and controlled. Leading indicators cover the early data that shows the programme is heading somewhere worth going.
Capability built means specific things. The team has completed a readiness assessment. You have mapped which workflows are candidates for AI and which are not. You have a governance framework, even a lightweight one, and one or two tools in active use with a measurement plan attached. Think of them as preconditions. A well-informed board can assess whether those preconditions are in place and judge whether the programme is set up to deliver.
PwC’s research on AI predictions notes that many organisations underestimate the time required to build data quality and governance foundations before meaningful AI returns are achievable. The capability-built section of your board report is where you show what those foundations look like in your business. Listing them specifically is not padding. It demonstrates that you understand which conditions need to be in place before financial returns follow.
McKinsey’s research on AI in the workplace finds that businesses which track workflow-level efficiency gains and adoption rates early are better positioned to make credible claims when financial results arrive. Your leading indicators are the measurement infrastructure that makes the next board update more defensible, and the one after that more persuasive.
The night before a board meeting is not the time to discover that your narrative does not hold. Build the three-part framework now, and every update you give will be honest, specific, and harder to challenge than any projection you might have reached for instead.
