The Technology Investment That the Board Approved and the Business Ignored
The pattern is familiar. A technology investment is built into the annual plan and approved by the board. The procurement is completed on schedule. The implementation goes reasonably well. Training is delivered. Licenses are activated. Twelve months later, adoption is at 30 percent of the licensed user base, the business units that were supposed to benefit are still running the processes the technology was supposed to replace, and the CIO is preparing an update for the board that explains why the expected productivity improvements have not materialized.
BDO's 2025 Board Survey found that 23 percent of board directors believe their organization's technology implementation lags competitors, and nearly one-third say advancing technology implementation will require the most board time and attention in the coming year. The boards are watching this pattern and are increasingly frustrated by it. The CIOs presenting the updates are often frustrated too. The business leaders who are not adopting the technology have their own explanation for why the tool does not fit their actual work. Everyone is frustrated. Nobody has quite identified the structural cause.
The structural cause is that board-approved technology investments fund the acquisition of capability but not the organizational work required to convert that capability into used value. The business case that secures board approval describes what the technology will do. It rarely describes what the organization needs to do differently for the technology to produce the projected returns, who is accountable for those organizational changes, what they cost, and what the realistic timeline is for adoption to reach the level the financial projections assume. The approval is for the technology. The adoption work is a separate organizational investment that is usually not budgeted, not accountable, and not managed with the same discipline as the technology program it is supposed to support.
Why Business Cases Systematically Undercount Adoption Cost
The business case for a technology investment is almost always built by the IT function or by a project team that is accountable for delivery of the technology, not for adoption of it. The financial model includes licensing costs, implementation costs, infrastructure costs, and training costs. It projects productivity improvements and cost reductions that assume a specific adoption rate, typically 80 to 100 percent of the licensed user base, within a specific timeframe, typically 12 to 18 months post-go-live.
The adoption rate assumption is the financial foundation of the business case. It determines the projected savings and the payback period. And it is almost never validated against the organizational conditions that would need to be true for that adoption rate to be achieved. A business case that projects 85 percent adoption within 12 months needs to answer: what percentage of the user base currently uses the legacy process the technology is replacing, what specific reasons those users have for preferring the legacy process, what organizational changes are required to eliminate those reasons, who is accountable for making those changes, and what those changes cost? If the business case cannot answer those questions, the adoption projection is a financial modelling assumption rather than a plan.
The adoption cost that is systematically undercounted includes the business change management work, redesigning the workflows that need to change for the technology to be used as intended. It includes the role-specific training that is qualitatively different from the generic product training that vendors provide and that rarely produces behavioral change on its own. It includes the management time required to enforce new ways of working, address resistance, and hold teams accountable for adoption targets. And it includes the ongoing optimization work that converts initial adoption into sustained usage, because initial adoption, users logging in and performing basic functions, is not the same as full utilization, users using the technology in the way the productivity projections assumed.
The Three Adoption Failures That Account for Most of the Problem
The Parallel Running Problem
The most common adoption failure is parallel running: employees continue using the legacy process alongside the new technology rather than replacing the legacy process with the new one. They use the new tool for tasks where it is obviously better, continue using the old process for tasks where the new tool has not yet proven itself, and maintain both in parallel indefinitely because neither system owns the full scope of what they need to do.
Parallel running produces the adoption statistics that look encouraging in early post-go-live reviews. A significant percentage of users are logging in. A significant number of transactions are flowing through the new system. The legacy system usage has not dropped proportionately, but that is attributed to the transition period. The transition period extends indefinitely because the decision to turn off the legacy system keeps being deferred, the risks of turning it off keep being cited as higher than the benefits, and the parallel running cost, the overhead of maintaining two systems and two processes, continues accumulating without a clear decision point.
The intervention for parallel running is setting a firm legacy turn-off date before go-live, not after. The turn-off date creates the organizational forcing function that parallel running avoids. It shifts the cost-benefit calculation from "we can continue using the old system" to "we must be competent on the new system before the old one disappears." The resistance to setting a firm turn-off date is real and should be expected. The alternative, allowing parallel running to extend indefinitely, is more expensive and produces lower adoption than the short-term disruption of a defined transition deadline.
The Incomplete Process Redesign Problem
Technology implementations that do not redesign the business processes around the new technology's capabilities consistently underperform against their adoption projections. The new system is introduced as an improvement to the existing process, which it usually is. The existing process is not changed. Users adopt the new system to the extent that it fits their existing process and continue using manual workarounds where the new system does not fit, which is typically where the most significant productivity improvement opportunity exists.
The ERP implementation that adds a new system for purchase order management without redesigning the approval workflow produces users who enter purchase orders in the new system and route approvals through email, because that is what the workflow requires and the system does not enforce a different workflow. The analytics platform deployment that installs a new BI tool without redesigning the reporting process produces users who pull data from the new tool and paste it into the Excel reports that stakeholders are accustomed to receiving, because changing the report format requires a stakeholder change management effort that was not in scope.
Process redesign needs to be in scope before technology selection, not after go-live. The technology should be selected to support the target process design, not to improve the current process incrementally. Organizations that select technology first and design the process to fit the technology consistently produce lower adoption and lower business value than those that design the target process first and select the technology that best supports it.
The Ownership Vacuum Problem
Technology adoption without clear business ownership produces the outcome described in S&P Global's 2025 analysis: only 21 percent of organizations measure the impact of their AI and technology initiatives. If nobody is accountable for measuring the impact, nobody is accountable for achieving it. The ownership vacuum is the condition where IT owns the technology program and the business is a recipient of it, rather than a co-owner of the outcomes it is supposed to produce.
The specific accountability gap that produces adoption failure is the absence of a named business leader who owns the adoption rate as a performance commitment, the way they own revenue targets or cost commitments. When adoption is an IT metric that IT reports on, business leaders treat low adoption as an IT problem to be solved by better training, better user experience, or better change communications. When adoption is a business metric that the relevant business leader owns, it becomes a management priority that the business leader has a personal stake in addressing.
Embedding business adoption ownership into the governance structure of technology programs is the single most effective design change that consistently improves adoption outcomes. The business leader who co-owns the technology investment from the business case stage through go-live and into the adoption phase has a fundamentally different relationship to the technology program than one who was consulted on requirements and shown the demo. That relationship difference produces the management attention and organizational priority that adoption requires to reach the levels the business case assumed.
The Board Conversation That Needs to Change
BDO's finding that nearly one-third of board directors believe technology implementation lags competitors reflects a board-level recognition that the current pattern is not acceptable. The board's role in changing the pattern is specific: it is to require that technology investment business cases include adoption plans with named business owners, specific adoption milestones, and the organizational investment required to achieve them, before approving the technology investment itself.
A board that approves a $5 million technology investment on the basis of a business case that projects $3 million in annual productivity savings without requiring an adoption plan that demonstrates how those savings will be realized is approving the purchase of capability whose conversion to value is left unmanaged. The $3 million savings projection is based on an adoption assumption that has no organizational plan behind it. When adoption reaches 30 percent instead of 85 percent, the savings are $1 million instead of $3 million, and the board is presented with an update that explains the shortfall as a technology or change management problem rather than a business case design problem.
The technology investment conversation that produces better outcomes has three components that are each the board's responsibility to require. An adoption plan with named business ownership and specific milestones. A realistic adoption cost that is included in the total cost of ownership rather than treated as a separate organizational overhead. And an outcome measurement framework that connects technology usage to the specific business metrics the investment was supposed to improve, established before deployment so the before-and-after comparison is clean rather than constructed retroactively.
Info-Tech Research Group's January 2026 CIO Priorities report notes that CIOs are entering 2026 under growing pressure to justify technology investment as AI initiatives scale and risk exposure expands. That pressure is the right pressure applied in the right direction. The CIOs who respond by building stronger adoption programs, connecting technology investment to measurable business outcomes, and redesigning business cases to include the organizational cost of adoption, will produce the board conversations that justify continued investment. The CIOs who respond by improving their update presentations while the adoption problem continues will produce the board conversations that result in reduced IT investment authority and increased board scrutiny of every technology decision.
Talk to Us
ClarityArc helps organizations design technology investment business cases that include adoption plans with named business ownership, realistic adoption cost, and outcome measurement frameworks that connect technology deployment to measurable business value. If your organization is experiencing the pattern of board-approved investments that the business does not adopt, we are ready to help you identify what the business case is missing and build the organizational conditions that produce different outcomes.
Get in Touch