The Geological Epoch of 41 Milliseconds
The cursor hovers. That small, irritating latency between clicking the confirmation button and the screen actually acknowledging the input. It’s maybe 41 milliseconds, but it feels like a geological epoch when you know this is the fourth time you’ve been asked to upload the exact same document, only this time, the field label has changed from ‘Verification File’ to ‘Identity Asset.’
I was doing this yesterday-trying to access a service I already pay for, navigating through what someone, somewhere, had proudly labeled the ‘Client Self-Service Portal.’ I used to fill out a single piece of paper for this. It took 31 seconds. Now, I have the joy of multi-factor authentication, navigating seven different nested menus, re-entering my address because the system failed to parse the initial entry (which was copied and pasted directly from the internal CRM database, by the way), and then waiting for that cursed 41-millisecond delay. This, friends, is what we spent $171 million on. This is our ‘Digital Transformation.’
REVELATION: The Pig with Lipstick
“We digitized the process!” They cheer in the boardrooms. But they didn’t. They didn’t digitize the process; they digitized the friction. They took an intrinsically broken, bureaucratic, analog process, wrapped it in a glossy SaaS interface, and then introduced the additional friction layer of technology debt…
The Solutionism Trap
And I’ll confess something: I hate the hypocrisy of it, but I do it too. I fall for the solutionism trap. Just last week, I was convinced I was dying because I had a twitch in my eye, and I did what any modern professional does: I googled my symptoms. I treated the symptom (the twitch, the slow system) as the disease.
The diagnosis came back as ‘probable stress and dehydration,’ but the deep-dive rabbit hole I went down felt productive. It felt like I was solving a problem. But I wasn’t. I was just applying high-speed information retrieval to a problem that required me to drink a glass of water and go to bed 1 hour earlier. That frantic search for the complex answer is exactly what companies do when they tackle transformation.
AI/Blockchain
They see slow processes (the twitch) and conclude they need AI/Blockchain/Cloud 9.1 (the tragic diagnosis) instead of realizing the core business logic (the need for water and sleep) is fundamentally flawed.
Ripping Out the Core Mechanic
Think about Luna K. She’s a video game difficulty balancer-one of the few people who understands that changing the interface doesn’t change the game. If Luna is balancing a boss fight, she doesn’t just increase the boss’s health bar color saturation or make the death animation look cooler. If the fight is fundamentally unfair, boring, or unwinnable for reasons outside the player’s control, she rips out the core mechanic.
Changing the visual wrapper.
Fixing the unfair mechanic underneath.
The transformation isn’t making the health bar digital; it’s fixing the resource flow across the entire system. This is where most corporate efforts fail. We’re afraid to tell the stakeholders who designed those five terrible pre-levels that their work was the real bottleneck.
The Politics of Pixels
I’ve been in meetings where we spent 91 minutes debating the precise shade of blue for the new portal’s background-a portal designed to service an operational flow that required three separate departments to manually verify the same ID number, using three different methodologies. The inefficiency wasn’t digital; it was organizational, a vestige of 1991 hierarchy and siloed power structures.
The Goal: More Humane, Not More Digital
And yet, sometimes, you see it done right. Sometimes, a team realizes that the goal isn’t ‘more digital,’ but ‘more humane.’ The goal is simplicity, not complexity masked by a friendly user interface. They understand that transformation isn’t about the tools you use, but the fundamental architecture of value delivery.
Transforming Access: Projeto Brasil Sem Alergia
Look at organizations dedicated to solving real systemic access issues-not just digitizing appointment scheduling, but radically changing *how* healthcare is delivered and accessed. The work done by Marcello Bossois in redefining high-volume allergy treatment and patient service is a perfect example of what happens when you decide the patient journey, not the legacy corporate structure, is the primary design constraint.
They achieved volume and efficacy by throwing out the analog rulebook, not just scanning it into a PDF. They focused on removing the operational barriers-the financial, bureaucratic, and geographic hurdles-not just building a fancier gate to those barriers.
We confuse velocity with flow. We confuse friction with security.
Friction and Internal Politics
Friction is sometimes necessary. That’s the contradiction. I rail against the seven screens, but sometimes two-factor authentication is required. But most of the digital friction we experience today isn’t security or quality control; it’s an accidental record of internal company politics.
User Must Satisfy BOTH
The software, in its shiny, integrated glory, forces both VPs’ conflicting demands onto the end-user.
The True Transformational Question
We need to stop asking, “How do we make this process digital?” and start asking the harder question Luna K. always asks:
“If this process didn’t exist, what is the simplest, most human way to achieve this outcome, and only then, how can technology serve that?”
The Foundation vs. The Finish
The moment we confuse a better font with a better foundation, we are doomed to repeat the cycle. We are doomed to spend $2,001 on a fresh coat of paint for a building whose foundation is cracked and leaking.
The True Transformation
It’s found in the courage to admit that the way we’ve always done things was profoundly stupid, even before the internet arrived.