Change Readiness Is Not a Mood: What ERP and Digital Transformation Leaders Keep Missing

Most failed transformations don’t collapse because somebody forgot to configure a field in SAP. That happens, of course. But the larger failure is usually quieter: people don’t believe the change makes sense, don’t see what it gives them, don’t trust that leaders will stay the course, or privately suspect they won’t be able to work well in the new system. Then leaders call it “resistance,” as if the workforce has developed a character flaw.

That framing is convenient. It’s also lazy.

The research on change readiness tells a more awkward story. Readiness is not enthusiasm. It’s not attendance at training. It’s not the smile people give during a town hall because the steering committee is in the room. It’s a bundle of beliefs, judgments, emotions, and intentions that form — and reform — as people encounter the change. Holt, Armenakis, Feild, and Harris tested readiness as a multidimensional construct across more than 900 organizational members, identifying four key belief areas: change-specific efficacy, appropriateness, management support, and personal valence.

• ERP and digital transformation failure is rarely “just technical”; readiness shapes whether people actually use the new way of working.
• Hard data from ERP studies show readiness strongly influences perceived usefulness and ease of use — two predictors of system adoption.
• Communication matters less as broadcasting and more as sense-making: “Why this?”, “Why now?”, “Can we do it?”, “What changes for me?”
• Participation is powerful, but not automatically positive. Deeply involved employees may become more informed — and more anxious.
• Resistance should be read as diagnostic evidence, not simply noise to be overcome.

The uncomfortable data behind “people risk”

ERP has always had a strange double life. On paper, it promises integration, better data, fewer redundant processes, faster decisions. In the actual organization, it can feel like a forced migration from one social order to another.

Kwahk and Lee note that ERP adoption was reported at about 80% among Fortune 500 companies, while ERP failure rates were estimated at 60–90%. Their empirical study drew on 283 responses from 72 Korean organizations that had already implemented enterprise-wide ERP systems. Readiness did not merely sit in the background as a pleasant HR variable; it indirectly influenced behavioral intention to use ERP through perceived usefulness and perceived ease of use.

The numbers are not small. In their model, readiness for change and computer self-efficacy explained 57% of the variance in perceived usefulness, with readiness adding 38% above computer self-efficacy alone. For perceived ease of use, the two explained 43% of the variance, with readiness adding 21%.

That should make project teams pause.

Not “Are they trained?” but “Do they believe this will work?”

Training asks: can people perform a transaction?

Readiness asks harder questions:

• Do employees believe the change is necessary?
• Do they think this particular solution is the right one?
• Do they believe leaders are genuinely committed?
• Do they think they personally can succeed in the new environment?
• Do they see any benefit — not abstract enterprise benefit, but something that matters in their daily work?

Armenakis and colleagues later developed the Organizational Change Recipients’ Beliefs Scale around five beliefs: discrepancy, appropriateness, efficacy, principal support, and valence. Their 24-item assessment was designed to act as a barometer of buy-in during change efforts, not just before the launch party.

This matters because many ERP programs over-measure technical readiness and under-measure belief readiness. They know how many test scripts passed. They know how many users attended training. They know the number of open defects. But they often don’t know whether warehouse supervisors, finance analysts, customer service teams, or regional planners actually believe the new process is workable.

And by then, go-live is two weeks away.

Readiness is not a pre-go-live checkbox

Gregory Stevens argues that readiness is often confused because researchers and practitioners use overlapping words — openness, commitment, receptivity, attitude, intention, capacity. His solution is useful: stop treating readiness as a static state and understand it as a recursive process shaped by context, time, cognitive evaluation, affective response, and action.

This seems obvious once stated, but many transformation plans still behave as if readiness is something to “create” in Phase 2 and then move on from.

People are ready, then not ready. Confident on Tuesday, doubtful after a bad data-migration rehearsal on Friday. Supportive after a good demo, irritated when they discover the report they need has disappeared. The readiness curve is not a staircase; it’s more like weather.

Weiner’s organizational readiness theory adds another useful distinction. At the collective level, readiness involves shared commitment to implement the change and shared belief in collective capability. Those judgments depend on how people appraise task demands, resources, and situational constraints.

That last part is often underestimated. Employees are not only asking, “Do I like this change?” They’re asking:

• Do we have enough time?
• Are the people who designed this close enough to operational reality?
• Will managers protect us during the productivity dip?
• Are the old KPIs still punishing the new behavior?

This is where readiness becomes political, practical, and slightly messy — as it should.

The participation paradox: involvement can create anxiety

Participation is one of the sacred cows of change management. Usually for good reason. The classic logic is sound: people support what they help create. Participation improves perceived fairness, surfaces local knowledge, and can increase commitment.

The Swedish hospital downsizing study gives empirical support to the broad point. Nurses in the proactively managed hospital reported higher organizational justice, more participation in decision-making, more positive attitudes toward downsizing, and stronger commitment to change than those in the reactive hospital. The multivariate difference for participation variables was significant, F(4,708)=45.35, p<.001.

Yet participation is not magic.

In a longitudinal ERP-related IS implementation study, communication and awareness had a strong direct effect on readiness (β = 0.59), and also strongly predicted perceived valence (β = 0.70) and satisfaction with participation (β = 0.70). Valence itself predicted readiness (β = 0.42). But satisfaction with participation had a small, statistically significant negative direct effect on readiness (β = -0.20, p < .05).

That is awkward. And interesting.

The expert’s burden

The most involved employees often see the sausage being made. They attend workshops, test edge cases, notice unresolved design gaps, hear competing promises, and understand exactly how much local workaround knowledge is being squeezed into a standardized template.

So their participation may be satisfying — they’re heard, involved, respected — while also making them more sober about the project. They know too much to be naively confident.

This doesn’t mean participation is bad. It means participation without psychological containment can overload the very people the project most depends on. Super users, SMEs, process owners, and local change agents need more than invitations. They need:

• honest escalation routes;
• permission to name risks without being labelled “negative”;
• visible decisions after feedback;
• time protection from their normal workload;
• recognition that expertise often produces anxiety, not just advocacy.

There’s a small tragedy in many ERP programs: the people closest to reality become the least reassured by generic reassurance.

Resistance is sometimes the organization speaking in code

Mathews and Linski challenge the traditional view of resistance as deficiency. Their argument is that resistance behaviours may reflect disruptions to valued human goods, not merely stubbornness or irrationality.

This fits the ERP world painfully well.

When a planner resists a new scheduling process, maybe she’s protecting autonomy. When a finance user complains about workflow approvals, perhaps he’s worried about competence and reputational damage. When field teams reject mobile reporting, maybe they’re defending speed, customer intimacy, or a local practice that headquarters never bothered to understand.

Some resistance is self-interested. Some is badly informed. Some is political theatre. Fine. But enough of it is signal that dismissing it becomes managerial negligence.

What leaders should measure before go-live

A change readiness assessment should not be another 60-question corporate survey that disappears into PowerPoint. It should guide action. The best version is short, repeated, segmented, and linked to interventions.

At minimum, measure:

1. Belief in the case for change

Do people understand the discrepancy between the current state and desired future? Do they believe the pain is real, or do they think leaders are importing a global template for political reasons?

2. Belief in the solution

Appropriateness is underrated. People may agree that change is needed while doubting that this ERP design, this rollout sequence, or this governance model is the right answer.

3. Efficacy and capacity

Not just “Were you trained?” Ask whether people believe they can perform the new work under real workload, real data quality, real customer pressure, and real month-end deadlines.

4. Principal support

Employees watch leaders with anthropological precision. They notice who attends, who cancels, who says “strategic priority” but delegates every hard decision.

5. Personal valence

This is the blunt question: “What’s in it for me?” In academic language, valence. In working language, “Will this make my job better, worse, safer, harder, more visible, more controlled, more meaningful?” The recent Employee Digital Transformation Readiness review also identifies digital skills, psychological readiness, behavioral intention, managerial support, resistance, and innovativeness as core dimensions, based on a PRISMA review covering 22 e-readiness articles, 504 digital transformation articles, and 178 digital transformation readiness articles.

A better readiness conversation

The practical implication is not complicated, though execution is. Transformation teams should stop asking whether the business is “ready” as if readiness were a yes/no gate. Better questions are sharper:

• Where is readiness strong, and where is it performative?
• Which employee groups see benefit, and which only see burden?
• Where does participation create ownership — and where does it create expert fatigue?
• Which readiness beliefs are deteriorating as go-live approaches?
• What resistance themes keep recurring, even after communication?

The mildly uncomfortable truth is that readiness work forces leaders to confront the social consequences of their own design choices. A rushed timeline is not a communication problem. A broken role design is not a training problem. A benefit case that only makes sense at board level is not an adoption strategy.

ERP and digital transformation programs don’t need more slogans about embracing change. They need better evidence about what people believe, fear, understand, and quietly doubt.

That’s less glamorous than a launch video.

It’s also much closer to the work.

When leaders need to test these readiness signals against project evidence before go-live, the Readiness Diagnostic Sprint provides a focused assessment and executive-ready mitigation plan.

For a practical way to structure people-side evidence early in the programme, use the Change Complexity Assessment Tool alongside the readiness discussion.

Sources and further reading

• Holt et al. (2007), “Readiness for Organizational Change: The Systematic Development of a Scale”
• Armenakis et al. (2007), “Organizational Change Recipients’ Beliefs Scale”
• Weiner (2009), “A theory of organizational readiness for change”
• Kwahk & Lee (2008), “The role of readiness for change in ERP implementation”
• Razmi, Sangari & Ghodsi (2009), ERP readiness assessment using fuzzy ANP
• Stevens (2013), “Toward a Process-Based Approach of Conceptualizing Change Readiness”
• Mathews & Linski (2016), “Shifting the paradigm: reevaluating resistance to organizational change”

If you are working through this on a live programme, browse the ERP transformation readiness resources for related guidance on what to measure and where people risk tends to concentrate.