What Boards Should Ask About Stalled Technology Adoption
The Oversight Question That Catches Adoption Failures Early
Boards routinely review technology investments before they're approved, weighing cost, risk, and expected benefit. Far fewer boards routinely ask what happened to that investment a year later. That gap in oversight is exactly where stalled adoption tends to live undetected, quietly eroding the return a technology purchase was originally approved to deliver.
Why Should Boards Track Adoption After Approving a Purchase?
Because the return the board approved the investment on depends entirely on sustained adoption, not just successful implementation, so oversight that stops at go-live misses the part of the risk that matters most.
A successful implementation and a successful investment are not the same thing. A system can be technically implemented on time and on budget, and still fail to deliver the return the board approved it for, if the people meant to use it stop doing so within a few months. Oversight that ends at "implementation complete" misses this distinction entirely.
What's the Key Question a Board Should Ask About a Past Approval?
Ask what current usage looks like compared to the adoption target set at approval, since that comparison reveals whether the investment is delivering what was promised.
This question only works if an adoption target existed at approval in the first place, which is itself worth confirming. If no target was ever set, that's a useful finding on its own, revealing that the original business case may not have included a clear standard for what success would actually look like.
How Can the Board Tell If Management Is Tracking Adoption at All?
Management should be able to produce actual usage data, not a general status update, when asked about any major technology investment approved in the past one to two years.
| Board Request | Strong Response | Weak Response |
|---|---|---|
| Show current usage data | Specific numbers, trended over time | A general statement that "it's being used" |
| Compare to original target | A clear comparison against the approved business case | No recollection of an original target |
| Name the adoption owner | A specific individual, currently accountable | "The team" or no clear owner |
| Explain any decline | A specific cause and corrective action | No explanation available |
A management team that can walk through this table confidently has genuine visibility into adoption. A management team that struggles with more than the first row likely doesn't, regardless of how the original implementation was reported.
What's a Governance Red Flag Related to This Issue?
A red flag is a technology investment that was reported as successfully implemented but for which no one can produce current usage data months or years later.
That combination, a confident implementation report paired with an absence of ongoing usage data, is a common and easy-to-miss pattern. It's easy to miss because the implementation report was likely accurate at the time; the gap opened up afterward, once attention moved elsewhere and nobody kept tracking what happened next. Independent research on the broader industry backs up how common this pattern is: only 7% of insurance companies had successfully scaled AI systems as of 2025, according to Insurance Business Magazine's reporting, despite a much larger share having implemented pilots successfully in the first place.
Should Adoption Metrics Be Part of Standard Board Reporting?
Yes, for major technology investments, adoption metrics belong in the same reporting cycle as other performance indicators the board already reviews, rather than being raised only if a problem surfaces.
Folding adoption tracking into regular reporting normalizes it as an expected part of technology governance, rather than something that only gets discussed reactively once a rollout has clearly gone quiet. A Reinsurance Audit Preparation AI Agent can help management assemble this kind of recurring adoption reporting efficiently, rather than treating each board request as a one-off data-gathering exercise.
How Should the Board Weigh a Pattern Across Multiple Investments?
Treat a repeated pattern as an operating discipline issue, not a series of unrelated project failures, and ask management directly what structural change will prevent it from recurring.
One stalled rollout might reasonably be attributed to a specific project's circumstances. Two or three stalled rollouts across different technology investments point to something systemic, most likely a missing organizational habit of assigning adoption ownership and tracking usage, and deserve a structural response rather than another one-off fix.
What Role Should the Board Play Before Approval, Not Just After?
The board should ask, at approval, what adoption ownership and measurement plan will be in place after go-live, rather than only reviewing that plan after a stall has already occurred.
Asking this question at the point of approval is far more effective than asking it later, because it puts the adoption plan requirement in place while there's still time to build it properly, rather than treating it as damage control after usage has already begun to slip.
A board that reviews technology purchases carefully but stops watching once implementation is declared complete is only overseeing half of the investment's risk. The other half, whether the organization actually kept using what it bought, is where a meaningful share of promised value tends to quietly disappear, and it deserves the same level of board attention as the original approval did.
Frequently Asked Questions
Why should boards track adoption after approving a technology purchase?
Because the return the board approved the investment on depends entirely on sustained adoption, not just successful implementation, so oversight that stops at go-live misses the part of the risk that matters most.
What's the key question a board should ask about a past technology approval?
Ask what current usage looks like compared to the adoption target set at approval, since that comparison reveals whether the investment is delivering what was promised.
How can the board tell if management is tracking adoption at all?
Management should be able to produce actual usage data, not a general status update, when asked about any major technology investment approved in the past one to two years.
What's a governance red flag related to technology adoption?
A red flag is a technology investment that was reported as successfully implemented but for which no one can produce current usage data months or years later.
Should adoption metrics be part of standard board reporting?
Yes, for major technology investments, adoption metrics belong in the same reporting cycle as other performance indicators the board already reviews, rather than being raised only if a problem surfaces.
How should the board weigh a pattern of stalled rollouts across multiple investments?
Treat a repeated pattern as an operating discipline issue, not a series of unrelated project failures, and ask management directly what structural change will prevent it from recurring.
What role should the board play in setting adoption expectations before approval?
The board should ask, at approval, what adoption ownership and measurement plan will be in place after go-live, rather than only reviewing that plan after a stall has already occurred.
Does this oversight responsibility apply to smaller technology purchases too?
It applies most clearly to major investments, but the same tracking discipline benefits smaller purchases too, even if board-level review is reserved for the larger ones.
