Embedded Files
Why do our most experienced experts push back the hardest on digital rollouts?
Why do our most experienced experts push back the hardest on digital rollouts?
When a highly experienced employee pushes back during an enterprise system rollout, the default corporate diagnosis is often “reluctance to adapt” or “fear of technology.”
Over the years, I have often wondered whether we are completely misinterpreting the signal.
Think of the veteran production planner, the senior buyer, or the lead accountant. For a decade or more, their professional identity was built on deep intuition, personal networks, and a labyrinth of intricate spreadsheets that rescued daily operations whenever official tools fell short. They were the recognized, go-to problem solvers of their department.
When a standardized enterprise platform arrives, it doesn't just replace their software. It standardizes their judgment.
Suddenly, the person everyone relied on is expected to click through the exact same rigid sequence as a new hire. The tension isn't about learning where the new buttons are; it is about what happens to someone's professional autonomy, status, and sense of contribution when their craft is automated.
How should an organization navigate those changes? In discussions with project directors, HR leaders, and change practitioners, I see very different philosophies play out.
Some advocate for redefining the role upward: If the platform absorbs the routine transactional volume, the idea is to elevate the expert into handling complex exceptions, edge cases, and root-cause analysis. Proponents point out that this preserves their institutional status while freeing them from administrative drudgery. On the flip side, I have seen teams struggle with this in practice. Sometimes inventing special new roles just dilutes the clarity of the new operating model.
Others argue for uncompromising process discipline: In this camp, the entire business case of an integrated platform rests on strict adherence to global standards. The thinking is that giving veteran staff special leeway or customized workarounds simply bakes obsolete habits into the new landscape. Advocates accept that some senior talent may choose to leave, viewing it as the natural price of modernization. Yet, when that level of tacit knowledge walks out the door, the business often discovers too late how much informal duct tape was actually keeping operations intact.
A third perspective focuses on operational safety and governance: Rather than changing the software design to suit individuals, these programs channel the expert’s credibility into risk mitigation. They are given genuine authority over cutover readiness, fallback procedures, and hypercare support. They remain the guardians of continuity, but within the boundaries of the new architecture.
Every organization’s culture handles this balance differently, and what succeeds in a heavily regulated plant environment might fall flat in a decentralized commercial team.
Page updated
Google Sites
Report abuse