So, You've Had a “Human Behavior Matters” Awakening. Now What?

In the last piece, I made the case that the silence after go-live – dashboards full of activity while the actual work stays unchanged – is where enterprise ROI quietly leaks away. The argument tends to land. Almost everyone nods along.

The hard part arrives on a Monday morning, with a steering committee Wednesday and kickoff in six weeks, when nodding along must turn into a plan, and nobody handed you one.

If that’s where you’re sitting, take a breath. That feeling isn’t a personal failing; it’s the most common starting point there is. Most leaders were trained to run the technical side of an implementation and left to improvise the human side, then held accountable for adoption numbers no one taught them how to influence.

The good news: this work is not mysterious. More than two decades of Prosci research has turned the people side of change into something closer to a discipline than an art. At its center is the ADKAR model – the sequence individuals actually move through in change: Awareness of the need. Desire to participate. Knowledge of how. Ability to perform. Reinforcement to sustain.

The reason to pick up that lens now, not after the first disappointing adoption report, is simple: the people side can’t be retrofitted. Trust spent in the first six weeks is expensive to buy back in month six. Here’s how to use it from the beginning, in four moves.

Assess before you announce

Before vendor selection, before the charter, before the budget locks, leadership should be able to answer two questions: how disruptive is this change, and how ready is the organization to absorb it?

These aren’t gut checks — they’re scored. Scope, timeline, how much roles actually change, history with past changes, current saturation, strength of sponsorship: each rated, and the totals give an honest read on the effort required. A low score means light-touch change management will do. A high score means the people-side investment must scale with the technical one, and skipping it is the most expensive shortcut available.

Most organizations skip this step anyway. Not from carelessness; the calendar is looming and the assessment feels skippable. Six months later they discover they bought a Ferrari and budgeted for a Honda’s worth of driving lessons. The assessment takes days; the discovery takes quarters to recover from.

Plan against ADKAR, not against the calendar

Most implementation plans follow the technical timeline: requirements, build, test, train, launch, support. Reasonable for software. Wrong for people who don’t adopt on a Gantt chart’s schedule, but in a sequence.

A people-side plan asks, for every impacted group:

• By when do they need Awareness?
• Who is best positioned to build their Desire, especially among the people from the last piece: the ones burned two years ago, the ones whose responsibilities the tool absorbs?
• What Knowledge gap will training close, and what gap will it not close?
• How will real Ability develop in live conditions, when workarounds are tempting?
• What will provide Reinforcement after launch, so the load doesn’t fall on a handful of champions until they burn out?

Each element becomes a milestone with a date, an owner, and activities. Nothing exists because it’s “standard,” everything exists because some ADKAR element requires it.

ADKAR also earns its keep as a diagnostic, and here a little empathy becomes a precision instrument. Adoption never stalls everywhere; it stalls at one letter. The team that looks defiant has a Desire problem – no one made the case in terms that matter to them. The person who looks incompetent has an Ability problem – they need coaching, not another training deck. The group drifting back to old habits has a Reinforcement problem – the system still rewards the old way. Naming the letter replaces blame with something fixable.

Run the project with two engines, not one

The biggest predictor of failed change, study after study, is the absence of an active and visible sponsor. Not a name on the org chart – a sponsor doing the work: showing up at kickoffs, building peer support among executives, telling employees directly why the change matters.

Active sponsorship correlates more strongly with success than scope, budget, or methodology. It is the cheapest lever in the entire effort and the one most often left unpulled, usually because no one told the sponsor, concretely, what the role requires. Part of your job is to make that job visible, early, while their calendar can still bend.

Run two engines in parallel: project management moving the technical work, change management moving the people work: sponsor engagement, manager readiness, communications, resistance. The two must share milestones, not trade status updates once a month like polite strangers.

Measure what actually changed

Logins, license utilization, and feature touches are activity metrics: they say the platform is being touched, not that the work has changed. Plenty of failed implementations had beautiful login numbers right up until the renewal conversation.

Real measurement asks three questions, in order. Did the initiative deliver the business case – the revenue, efficiency, or customer outcome that justified it? Did the people who had to change actually change – adoption and proficiency measured in behavior, not access logs? How well did the change effort itself perform – and what would we do differently?

The first is what executives care about. The second is the only honest predictor of the first. The third is what makes the next change cheaper.

The compounding return

Done well, change management isn’t an overhead line – it’s the mechanism that makes the investment compound. The first major change costs the most, because the organization is also learning how to absorb change at all. The second is easier. By the fifth, change capability is a competitive advantage, and the cost per initiative drops dramatically.

But compounding rewards those who start early. Every implementation run without this discipline isn’t neutral; it’s a withdrawal. It teaches people that change is chaotic, and the safest move is to wait it out. That lesson is expensive to walk back.

The organizations that figure this out early stop asking whether they can afford to do change management properly. They start asking how they were ever willing to leave that much ROI on the table – and how much is still leaking from the initiative launching next quarter.

The platform was always going to be the easy part. The discipline is in everything around it. And it starts wherever you are, even on a Monday morning, six weeks from kickoff.