Six weeks into a new AI initiative, a delegate gets a message from the board asking for the return figure. The honest answer is that meaningful AI ROI typically takes 12 to 24 months to show up in the financials. That answer is correct, but saying it without a plan sounds like stalling.
The problem is not the timeline. The problem is having nothing credible to show while you wait for it. That is what dual-ROI measurement addresses. It separates what you can measure now from what you will measure later, and gives each its proper place in the conversation with the board.
What is dual-ROI measurement?
Dual-ROI measurement divides the return on an AI investment into two distinct tracks. Trending ROI captures early evidence that value is building, whether that is time saved per task, error rates falling, or adoption growing across the team. Realised ROI is the confirmed financial outcome in the accounts once the operational change has had time to compound. Both tracks run simultaneously and neither replaces the other.
The reason they need separating is timing. Many AI investments take well over a year to show their financial return. A workflow that saves your team four hours a week does not appear in the profit-and-loss account until those hours are redirected into something billable, or until the business makes a hiring decision that reflects the capacity that now exists. The connection between operational improvement and financial outcome is real, but it crosses a gap that takes time.
Trending ROI creates a credible bridge across that gap. Rather than waiting for the P&L to confirm what is already happening in the operation, you track the indicators moving in the right direction, name the mechanism connecting them to financial outcomes, and set an honest timeline for when the realised numbers will arrive. The frame matches how AI investments actually work, which makes it defensible to a board that understands the underlying dynamic.
Why does the board ask for a number that isn’t there yet?
Boards expect AI to pay back faster than it does because the coverage around AI deployments tends to feature headline results without the deployment timelines that produced them. When a project goes live, the board has already filed it under “imminent return” without knowing the typical lead time involved. That gap between expectation and reality is a calibration problem the delegate has to solve.
BCG’s 2025 research found that AI usage is rising across businesses while financial impact is not following at the same rate. That reflects the normal delay between operational change and financial outcome, a delay that shows up consistently across deployments and that the measurement frame needs to account for.
Korn Ferry’s analysis of AI leadership found that organisations tend to assign AI responsibility to strong operators with high expectations but limited preparation for the task. The delegate often inherits a board conditioned to expect rapid returns by the same people who handed the brief over without the resources to deliver them.
Resetting that expectation is part of the delegate’s job. The dual-ROI frame gives you something concrete to show while you do it. Specific indicators moving, a named mechanism, and a committed timeline replace the number that does not yet exist.
Where do trending indicators show up in practice?
Trending indicators are specific, measurable signals that appear before the financial results do. They should tie directly to the business outcome the AI initiative was supposed to produce. If the project was meant to speed up document processing, the trending indicator is processing time. If it was meant to reduce errors, the indicator is error frequency. One initiative, one or two indicators, tracked and reported consistently.
The indicators that hold up are those that sit close to the operational change itself. Time-per-task works well. A task that took six hours and now takes two is a measurable change you can report without qualification. Adoption rates tell you whether the tool is in active use. Error and rework rates tell you whether quality is improving. These are not proxies for financial outcomes; they are the leading indicators that a financial outcome is being built.
What tends not to hold up is selecting indicators because they are easy to generate rather than because they are meaningful. Tool login counts, for instance, tell you a browser tab has been opened. They say nothing about whether the work improved. The trending indicator needs to sit close enough to the actual work that movement in it could plausibly cause movement in the financial outcome.
A useful test is whether a 20% movement in the indicator could be traced to a financial outcome. If the path is not reasonably clear, the indicator is decorative.
When is trending ROI enough, and when isn’t it?
Trending ROI is enough when the initiative is recent, the board understands the timeline, and the indicators are moving in the right direction. It becomes insufficient when realised outcomes were promised by a specific date and that date is approaching, or when indicators have been strong for months but financial results are not materialising. At that point, the mechanism has broken somewhere.
The most common culprit in that gap is data quality. Schellman’s analysis of AI implementation failures found that 77% of organisations name poor data quality as their biggest barrier. An initiative can save time in the operation while the financial benefit evaporates because the hours saved are absorbed into existing overload rather than redirected into commercial activity.
A four-hour saving per week is worth something on the balance sheet only if those four hours end up somewhere useful. If they disappear into the general noise of an overloaded team, the mechanism is broken. Trending ROI shows the saving; realised ROI confirms whether it landed. When the two diverge, that divergence is worth reporting to the board rather than obscuring. Naming a broken mechanism is better for your credibility than presenting climbing indicators while the financial results refuse to follow.
What sits alongside dual-ROI measurement?
Dual-ROI measurement is a reporting frame, not a substitute for a business case. It needs to sit alongside a clear statement of what the AI initiative was supposed to achieve, realistic timelines for when realised outcomes will appear, and a named mechanism connecting operational improvement to financial results. Without those three elements, the trending indicators float without context and the board cannot evaluate them.
MIT’s research on AI deployment returns consistently finds that organisations tend to measure activity rather than outcomes. Dual-ROI measurement is useful only if the outcomes were defined before the initiative launched. If the project went live without a target financial result attached, the trending indicators are measuring movement without a destination.
The practical anchor is the business case. State the problem the initiative solves, quantify the expected financial return, estimate when it will appear, name the trending indicators you will track in the meantime, and set a review date for when realised outcomes will be confirmed. That document replaces the number the board asked for six weeks too early. It tells them what you are measuring, why it matters, and when the real figures will arrive.
If you are working through how to structure that case, or preparing to present AI progress to a board that expected faster results, a conversation is the fastest way to get the framing right. Book a conversation to work through it.
