The Budget Line That Is Always Too Small
Digital transformation programme business cases have a predictable structure. The technology investment is quantified with precision: licences, implementation services, infrastructure, integration. The productivity benefit is modelled with aspiration: efficiency gains, cycle time reductions, error rate improvements. And somewhere between the technology line and the benefit projections is a change management line that represents five to eight percent of the total programme cost and receives a fraction of the governance attention.
The change management line is not small because programme sponsors undervalue people. It is small because people costs in transformation are genuinely hard to quantify, because the cost categories that most naturally describe the people challenge do not appear in standard programme cost templates, and because the business case scrutiny that large technology investments receive is not consistently applied to the change management investment that determines whether the technology investment delivers its return.
The result is predictable and recurring. Technology is deployed. Adoption is lower than projected. Productivity benefits are slower to materialise than modelled. The gap between projected and actual benefit is attributed to implementation complexity, change in business requirements, or market factors. The underinvestment in the people programme that is the actual cause receives less attention because it is harder to demonstrate causally than a technology failure.
The Costs That Do Not Appear in the Template
The standard programme budget template has categories for technology, implementation services, project management, and training. The people costs that drive transformation outcomes are distributed across categories that are harder to see as transformation costs.
Productivity loss during transition is typically the largest unmeasured people cost. When a team moves from a mature process supported by familiar tools to a new process supported by new tools, their productivity drops during the transition period. The drop is both immediate, as people learn new tools and processes, and sustained, as new habits form and inefficient workarounds are developed and then corrected. For a team of fifty people experiencing a twenty percent productivity reduction for six months during a major system transition, the fully loaded cost of that productivity loss is significant and is almost never included in the programme cost baseline.
Manager time for change leadership is a cost that is rarely explicit. Effective change management through a transformation programme requires significant manager engagement: running team conversations about the change, identifying and addressing individual concerns, coaching people through the new ways of working, and resolving the conflicts between old and new processes that arise during transition. This time has an opportunity cost, and in organisations where managers are already stretched, the transformation adds to that load without adding capacity.
Attrition risk has a cost that is rarely modelled. Transformation programmes that are poorly managed increase turnover, particularly among experienced employees who have the market optionality to leave. The fully loaded cost of replacing an experienced employee who leaves during a poorly executed transformation includes the recruitment cost, the onboarding cost, the productivity ramp time for the replacement, and the lost institutional knowledge that the departing employee took. In most organisations, this cost is not attributed to the transformation programme; it appears in HR costs and is treated as unrelated.
External support dependency during transition is a cost that compounds if not managed. Organisations that go live on new systems with insufficient internal capability rely on implementation partners and vendors for support through the transition period. This reliance is appropriate for a defined transition window, but it becomes a structural dependency if the internal capability development investment does not keep pace with the transition. The cost of extended external support dependency, which often runs well past the original go-live date in transformations with insufficient capability development investment, is a programme cost that was not in the original business case.
Why Organisations Consistently Underinvest
The structural reasons for underinvestment in people programmes are worth understanding because they persist across organisations and across transformation types, suggesting that the solution requires deliberate design rather than individual programme manager awareness.
The ROI calculation challenge is the most fundamental. Technology investment in a transformation has a relatively clear cost and a relatively plausible projected return that can be modelled and compared. Change management investment has a clear cost and a diffuse return that contributes to the adoption that enables the technology’s return, but cannot be cleanly separated from other factors that affect adoption. The investment case for change management depends on a chain of logic that is harder to defend to a CFO than the investment case for technology.
The visibility problem compounds the ROI problem. Technology investment produces visible outputs: systems that are built and deployed, features that are released, infrastructure that is running. Change management investment produces invisible outputs: employees who are less anxious, managers who are more capable of leading change, processes that have been adapted to the new ways of working. The invisible outputs are less compelling in budget conversations than the visible ones.
The timing mismatch creates a third structural pressure. The change management investment is needed throughout the programme and intensifies at go-live and through the adoption period. The business case scrutiny for change management investment is highest early in the programme, when the adoption risk it addresses is abstract. By the time the adoption risk is concrete and visible, the programme is already past the investment decisions that would have been most effective.
The Investment Structure That Changes the Outcome
The people programme investment structure that consistently improves adoption outcomes has three components that address the structural underinvestment problem rather than just arguing for a larger budget.
Embedding change costs in technology deliverable budgets rather than treating them as a separate programme line changes the visibility problem. If the ERP implementation project budget includes the change management, training, and capability development costs required to reach the adoption target for each module, those costs are subject to the same scrutiny and governance as the technology costs. They are more likely to be fully funded and to be treated as programme requirements rather than nice-to-haves.
Measuring adoption as a primary programme metric alongside technical delivery milestones changes the governance attention. If the programme steering committee reviews adoption metrics monthly alongside delivery progress, underperformance in adoption receives the same escalation attention as a delayed technical milestone. The change management investment that is not working gets identified and adjusted; the change management investment that is working gets defended against cost pressure.
Resourcing the internal capability explicitly rather than treating it as something that emerges from training creates a transition pathway from external to internal support dependency. Identifying the specific people who will own the new capabilities after the external implementation partner has left, resourcing their development through the programme, and measuring their readiness as a programme deliverable, produces a different outcome than hoping that internal capability develops as a side effect of working alongside the implementation partner.
The digital transformation that delivers its projected return is not the one with the best technology. It is the one where the people adopted the technology and the processes changed to support it. The investment required to get there is not a soft add-on to the real programme. It is the programme.