Marcus is clicking. The mouse makes a sharp, plastic sound that echoes against the laminated desk, a rhythm of frustration that has lasted for exactly 31 minutes. He is staring at a screen that should represent the pinnacle of modern efficiency, yet he feels more like a medieval scribe than a digital pioneer. The notification is centered, mocking in its clean sans-serif font: ‘Session Expired.’ All the data-the 11 policy numbers, the 21 unique identifiers for the fleet, the 51 separate addresses for the regional offices-has evaporated. It didn’t go into a database. It went into the void. This is the promised land of digital transformation, and it feels remarkably like a waiting room in a windowless government building.

The Invisible Barrier

I say this as someone who recently walked into a glass door. It was one of those perfectly polished, floor-to-ceiling sheets of architectural hubris. I saw the space ahead, I saw the goal, and I assumed the path was clear because there were no visible barriers. The impact was a dull thud against my forehead and a very public lesson in the danger of invisible friction. Digital transformation is that glass door. It looks like an open path, but the moment you try to move through it at speed, you realize the barriers haven’t been removed-they’ve just been made transparent. You don’t see the ‘form 12-B’ anymore, but you certainly feel the impact when the system refuses to let you proceed because you used a hyphen where it expected a slash.

We were told the paper would die. We were promised that the death of the filing cabinet would herald an era of fluid, frictionless commerce. Instead, we have simply traded physical weight for cognitive load. We didn’t actually remove the bureaucracy; we just backlit it. We took a process that required a single, messy ink signature and replaced it with a gauntlet of 21 mandatory dropdown menus, three separate two-factor authentication codes, and a CAPTCHA that asks us to identify fire hydrants until we begin to doubt our own humanity. It is faster to move an electron than a courier, but if the electron has to stop at 41 virtual checkpoints, the speed of the medium is irrelevant.

The Wisdom of the Submarine Galley

Kai H. knows a thing or two about friction, though his world is made of steel and pressurized seawater rather than code. Kai is a submarine cook, a man who operates in a kitchen the size of a walk-in closet while 101 sailors wait for their calories. On a submarine, every movement is choreographed. If Kai needs to reach the turmeric, he shouldn’t have to move 11 other jars to get there. Space is a premium, but time and mental energy are the real currencies. Kai once told me that the most dangerous thing on a boat isn’t a leak; it’s a process that takes three steps when it should take one. In a high-pressure environment-whether it’s 201 meters below the surface or in the middle of a high-stakes insurance claim-complexity is a liability. It creates a ‘mental drag’ that eventually leads to catastrophic error.

Most corporate ‘portals’ are the antithesis of Kai’s galley. They are sprawling, disorganized, and built on the bones of legacy systems that were never meant to talk to each other. When a company says they are ‘going digital,’ what they usually mean is that they have hired a developer to build a web interface for a 31-year-old COBOL database. They aren’t reimagining the workflow; they are just putting a tuxedo on a pig. The pig is still slow, and now it’s angry because it has to handle 121 simultaneous login attempts.

“

Complexity is a tax on the soul that no one voted for.

”

Ignoring Context for Compliance

Consider the way we handle risk. In the old days, you talked to a broker. You had a conversation. You explained that your warehouse was built in 1991 but had a new roof installed in 2011. The broker understood context. Today, you enter that data into a portal. The portal doesn’t understand context; it only understands ‘valid’ and ‘invalid.’ If the roof doesn’t fit into the predefined categories of the dropdown menu, the system stalls. You spend 41 minutes trying to find a workaround for a problem that didn’t exist when the process was human. We have automated the ‘how’ but completely ignored the ‘why.’

This is why so many digital initiatives fail to deliver the ROI that was promised in the 51-page slide deck presented to the board. They measure success by the number of forms moved online, not by the amount of time saved by the user. They measure the ‘digitization rate’ instead of the ‘frustration rate.’ If your digital transformation requires a 111-page PDF manual to explain how to use the ‘simple’ new interface, you haven’t transformed anything. You’ve just written a digital encyclopedia for a library that no one wants to visit.

The Philosophy of Subtraction

There is a better way, a path that prioritizes the user’s heartbeat over the system’s architecture. It involves stripping away the ‘ghost’ requirements-the fields we collect ‘just in case’-and focusing on the 11% of data that actually drives 91% of the decision-making. It means building systems that are as intuitive as a physical tool. You don’t need a manual to use a hammer; the design tells you where to put your hand. Why should an insurance claim be any different?

This philosophy is at the heart of platforms offering foreign worker insurance, which recognize that the value isn’t in the portal itself, but in the speed and clarity of the protection it provides.

Hiding the Signposts

I find myself thinking back to the glass door. The problem wasn’t the glass; the problem was the lack of indicators. A simple decal, a handle, or a frame would have signaled to my brain how to interact with the barrier. In the digital world, we are obsessed with making things ‘clean’ and ‘minimalist,’ but we often remove the very signposts that help users navigate. We hide the ‘Submit’ button behind a scroll, or we use icons that are so abstract they could mean anything from ‘save’ to ‘launch a missile.’ We are so focused on the aesthetic of the future that we have forgotten the ergonomics of the present.

Kai H. has a rule in his galley: if you use a tool more than 11 times a day, it shouldn’t be in a drawer. It should be on a magnet, on the wall, exactly where your hand naturally falls. How many of our digital processes follow this rule? Most of them feel like the tool is in a drawer, inside a locked cabinet, in a room you need a keycard to enter, and the keycard reader is currently ‘undergoing scheduled maintenance.’ We have built digital labyrinths and called them ‘user journeys.’

The Justification of Obfuscation

I suspect the reason we cling to these clunky systems is a deep-seated fear of simplicity. Simplicity looks easy, and in the corporate world, if something looks easy, it’s hard to justify the $151-per-hour consulting fee. Complexity provides a shroud of ‘expertise.’ If the system is difficult to use, we assume it must be doing something very sophisticated. But true sophistication is the removal of the unnecessary. It is the 21 lines of code that do the work of 1001. It is the interface that anticipates the next step so the user doesn’t have to.

We are currently in the ‘adolescent’ phase of digital transformation. We have the strength of the new tools, but we lack the wisdom to use them with restraint. We are like kids with a 3D printer, making things just because we can, without asking if the world actually needs another plastic whistle. We are digitizing bureaucracy because it’s the path of least resistance. It is much harder to change a business process than it is to build a web form that mimics the old process. But if we don’t do the hard work of process reform, we are just accelerating our own obsolescence.