Nobody puts “frustration” on a digital transformation roadmap, but it’s one of the most consistent costs I’ve watched organizations underprice — and, if I’m honest, one I underpriced in my own life for a long time too.
The cost that doesn’t show up in the business case
Every transformation program I’ve been part of has a budget line for licenses, integration work, and training hours. None of them, in my experience, has ever had a line for the cumulative frustration of the people living through the change — the small daily friction of a workflow that used to make sense and now doesn’t quite, multiplied across months and across a few thousand people. That cost is real. It shows up as quiet disengagement, as the good people who leave for reasons that never quite make it into an exit interview, and as a change program that technically launched on time but never actually took hold the way the business case promised.
Why this is a mindful-leadership problem, not just a change-management one
Change management frameworks are good at sequencing communication and training. They’re much less good at addressing the actual felt experience of the person in the middle of the change — the low-grade, hard-to-name frustration of feeling behind, or unsure, or quietly worried that the skills that made you valuable are being made obsolete faster than you can adapt. I don’t think that’s a gap in the frameworks so much as a genuinely hard thing to build a process around. But leaders who at least name it — who acknowledge the frustration directly instead of only communicating the upside — consistently get further with their teams than leaders who treat resistance as something to be managed past.
What this looks like for the person in the middle of it, not just the leader
This is where it gets personal for me, not just professional. Twenty-three years into a career built on staying ahead of technology shifts, I still notice the same low-grade frustration in myself when the pace outstrips my ability to sit with it — the sense of always needing to be one step further along than I actually feel. I built Daily Mental Mirror originally for exactly this: a short daily reflection to notice, in a few minutes, how much of the day actually felt focused and intentional versus reactive and scattered. Not to fix the pace of change — nothing fixes that — but to have an honest, private record of how you’re actually experiencing it, instead of just pushing through and assuming it’ll sort itself out.
If you’re leading a team through a transformation right now, the frustration your people are feeling is not a sign the program is failing. It’s a predictable, priceable cost of real change. Naming it honestly, for yourself and for the people you lead, tends to be cheaper in the long run than pretending it isn’t there.