Technology Modernization Fails Without a People Plan

I have sat in enough steering committee meetings to notice a pattern: the technology workstream gets a detailed plan, a dedicated budget line, and a named executive owner. The people workstream gets a training deck and a hope.

The asymmetry is built into how projects get funded

Technology modernization budgets are typically built around licenses, infrastructure, and implementation partners, all of which are easy to scope and easy to defend to a finance committee. The people side, training, workflow redesign, sustained change support, is harder to scope precisely, so it is often underfunded relative to its actual importance to the outcome.

The result is predictable: the system launches on time and on budget, and six months later utilization is disappointing, because the people who were supposed to use it differently were never given the support to actually change how they work.

Adoption is a design problem, not just a training problem

Training alone rarely solves this, because the underlying issue is usually not a lack of knowledge. It is that the new system asks people to work differently than they have for years, often without redesigning the incentives, workflows, and manager expectations that reinforced the old way of working. Training people on a new tool while leaving the old incentives in place produces confusion, not adoption.

Funding the people plan like it matters

Organizations that get this right treat the people plan as a co-equal workstream to the technology plan, with its own budget, its own named owner, and its own success metrics that go beyond training completion to actual usage and performance. That shift, from treating people work as a communications afterthought to treating it as core project scope, is often the single highest-leverage change available to a modernization effort already underway.

Why the budget conversation gets this backwards

Technology budgets are built around line items that are easy to scope and easy to defend in front of a finance committee: licenses, infrastructure, implementation partners. The people side of modernization, training, workflow redesign, sustained change support, resists that kind of clean scoping, so it consistently loses out in budget conversations relative to its actual importance to the outcome. The system launches on time and on budget, and six months later, utilization is disappointing, because the people expected to work differently were never given the sustained support to actually do so.

Why training alone does not solve this

The instinct, once low adoption becomes visible, is usually to add more training. That rarely works, because the underlying issue is often not a knowledge gap. The new system asks people to work differently than they have for years, frequently without redesigning the incentives, workflows, and manager expectations that reinforced the old way of working. Training someone on a new tool while leaving the old incentives fully in place produces confusion and quiet resistance, not adoption.

Funding the people plan as core scope

Organizations that get this right treat the people plan as a co-equal workstream to the technology plan, with its own dedicated budget, its own named owner, and its own success metrics that go beyond training completion to actual usage and performance data. That single shift, from treating people work as a communications afterthought to treating it as core project scope with real resourcing behind it, is often the highest-leverage change available to a modernization effort that is already underway.