I once watched a manufacturing company in Ho Chi Minh City spend $2.3 million on a shiny new ERP system, only to watch their employees quietly return to Excel spreadsheets within six months. The technology was fine. The implementation was technically sound. But nobody told anyone *why* they should care, and nobody prepared them for the disruption. That company learned an expensive lesson: digital transformation fails not because the technology is bad, but because people are left behind.
This is the dirty secret of transformation initiatives that nobody really talks about in the glossy case studies.
The Real Cost of Ignoring People
Here's a statistic that should keep you awake at night: 70% of digital transformation initiatives fail to achieve their intended outcomes, according to research from the Economist Intelligence Unit. But here's what's interesting—when you dig into *why* they fail, technology issues rank fifth or sixth on the list. The top reason? Organizational resistance and poor change management.
Yet most companies allocate maybe 5-10% of their transformation budget to change management, if they allocate anything at all. They're essentially betting that if you build it, they will come. Spoiler alert: they won't.
The problem is that digital transformation is fundamentally a *people* problem wearing a *technology* costume. Your team doesn't care about your cloud migration strategy in the abstract. They care about whether they'll still have a job, whether they'll look stupid learning new software, and whether anyone actually respects what they've done before.
What Actually Moves People
I learned this working with a logistics startup in Da Nang that was implementing a new warehouse management system. Instead of rolling it out company-wide, they recruited a small group of power users—people who were genuinely curious, a bit technical, and respected by their peers. These weren't appointed managers. They were the people other workers naturally talked to during breaks.
We spent three weeks getting this group fluent with the system, then we did something radical: we let them teach everyone else. Not through formal training sessions (nobody learns anything useful from a 2-hour PowerPoint), but through pair work and peer learning.
Share this post
Related Posts
Need technology consulting?
The Idflow team is always ready to support your digital transformation journey.
Adoption jumped from the predicted 60% after three months to 89% within six weeks.
The insight that practitioners rarely share: Change adoption isn't about how good your training materials are. It's about creating a permission structure where people feel safe admitting they don't understand something, and then having trusted peers—not corporate trainers—help them through it.
The Three Truths Nobody Wants to Hear
First, people are grieving. Even when you're "upgrading" to something objectively better, you're destroying a way of working that someone has mastered. That mastery is status, efficiency, and confidence. Acknowledge this. Don't just say "the new system is better." Say "I know you've gotten really good at the old way, and that was valuable, and now we're changing the game on you, and I understand why that's frustrating."
Second, digital transformation always costs more than the software. When a Vietnamese financial services company went through major transformation last year, they budgeted $8 million for technology and discovered they needed another $5 million for organizational redesign, process changes, and change management. The spreadsheets nobody tells you about.
Third, your change management strategy will fail if it's generic. Every organization has different cultural currents, different power structures, different ways that information actually flows (not the org chart way, but the *real* way). A bank in Hanoi has different change dynamics than a tech startup in HCMC. A manufacturing plant has different dynamics than a services firm. You have to diagnose your specific situation before you prescribe the treatment.
The Practical Moves That Work
If you're leading transformation, here's what the people who actually pull this off do:
Build a coalition that's diverse enough to be credible. Get champions from operations, IT, finance, and the frontline workers who'll actually use the system. Not just executives nodding in boardrooms. Get the 52-year-old warehouse supervisor who's seen three previous "transformations" and is skeptical. If you can bring her along, you've won credibility that consultants can't buy.
Show early wins, even if they're not the "main" transformation. One manufacturing client I worked with implemented a small mobile app for shift handover notes six months before the big ERP migration. Nothing revolutionary, but suddenly, shift supervisors were thinking in terms of digital workflows. The psychological shift matters.
Create feedback loops where resistance is heard as information, not obstruction. When someone says "this won't work," they usually have observed something real, even if their conclusion is wrong. Investigate. You might find risks that matter.
Honestly acknowledge what people are losing. A telecommunications company in Vietnam implemented new CRM software and realized that some sales reps would lose the ability to manually adjust customer pricing—a "flexibility" that was actually just hiding inconsistent margins. Be transparent about this. Don't pretend constraints are features.
The Unsexy Reality
Transformation work is boring. It's months of repeating the same message in different formats. It's one-on-one conversations with people who are afraid. It's tracking adoption metrics that are frustratingly slow. It's change fatigue setting in around month four, when the novelty has worn off but you're nowhere near stable yet.
The companies that succeed don't do this because it's easy or exciting. They do it because they've learned—sometimes the expensive way—that ignoring people's capacity to change is the fastest way to turn a strategic advantage into a very expensive mistake.
Digital transformation is ultimately about your organization's ability to evolve. That ability lives in people, not in software.
---
When organizations here in Vietnam approach me about transformation work, I always start with change management before we ever discuss architecture. Idflow Technology has spent the last few years focused on exactly this—building tools and processes that help teams actually *manage* transformation, not just buy it. Because the best technology in the world is just expensive office furniture if nobody knows how to use it.
