I am pressing the phone so hard against my left ear that I can feel the pulse in my temple, a rhythmic thumping that matches the ticking of the kitchen clock in this drafty house in Skåne. “Storgatan 17,” I say for the fourth time. The person on the other end of the line is perfectly pleasant. Her voice has that curated, professional warmth that suggests she has attended at least 27 seminars on customer empathy. She tells me she understands my frustration. She tells me she is going to get this sorted out. Then, she tells me she needs to transfer me to the scheduling logistics department because, while she can see the order for the insulation, she cannot see the truck’s physical location. I am dropped back into a vat of hold music-a MIDI version of a song I used to like but now associate exclusively with the slow death of my afternoon.
The Modern Institutional Dance
Departments Involved
Human Touchpoint
This is the modern institutional dance. I am caught in a loop where everyone is polite, everyone is informed within their narrow bandwidth, and everyone is utterly useless to the task at hand. It reminds me of an argument I lost last Tuesday. I was right, of course. I told a contractor that the drainage slope was insufficient for the volume of Swedish autumn rain, but he had a spreadsheet that said otherwise. He won the argument because his data was siloed, ignoring the reality of the gravity-fed water pooling at my feet. In the world of departmentalization, being “right” according to your own department’s metrics is the ultimate shield against actually solving a human problem.
The Tragedy of the Expert
Antonio C.-P. knows this dance better than anyone. As a hotel mystery shopper who has spent 187 nights in luxury properties this year alone, he looks for the cracks in the veneer. Antonio doesn’t care if the lobby smells like expensive sandalwood if the person at the front desk can’t tell him why the 777-euro-a-night suite smells like a damp basement. He once told me about a stay in Gothenburg where he spent 37 minutes being bounced between the concierge, housekeeping, maintenance, and the night manager just to find out if the pillows were hypoallergenic. Each person he spoke to was a specialist. The concierge knew the city; housekeeping knew the laundry schedule; maintenance knew the HVAC system; the night manager knew the liability codes. None of them knew the pillows.
Antonio describes this as “the tragedy of the expert.” When you specialize a role down to its atoms, you lose the molecule of the experience. The customer doesn’t live in the atoms; they live in the molecule.
We have built our companies to be efficient for the payroll, not for the person paying. By splitting a single inquiry into 7 different departments, we create an internal order that looks beautiful on an organizational chart. It’s clean. It’s measurable. You can track the KPIs of the finance team separately from the claims team. But for the person in Skåne waiting for their insulation, those boundaries are scars. They are points of friction where information is routinely dropped, like a baton in a relay race run by people who aren’t allowed to look at each other.
The Evaporation of Responsibility
I think about the 127 small decisions that lead to this kind of organizational bloat. It starts with a desire for “clarity of responsibility.” Someone at a board meeting, probably wearing a suit that costs more than my car, says that we need to define roles more strictly to avoid overlap. It sounds logical. It sounds like progress. But what they are actually doing is building walls. They are ensuring that when a problem arises that touches three different areas, it will belong to no one. Responsibility, when sliced too thin, evaporates. I am currently staring at a stack of 47 emails from a single service provider, each one signed by a different “specialist,” yet my original question about the delivery date remains unanswered. They are all answering the questions they *want* me to have, rather than the one I actually asked.
Fragmented Communication Overview
“
The customer doesn’t live in the atoms; they live in the molecule.
The Lethargy of Being Ignored
There is a specific kind of exhaustion that comes from being handled by a fragmented system. It’s not the anger of a fight; it’s the lethargy of being ignored by a thousand polite people. It’s the feeling of being a number in a system that is mathematically incapable of seeing you as a whole. When I talk to people who have successfully navigated these corporate mazes, they don’t talk about the “quality of service.” They talk about the one person they found-the rogue employee who broke protocol, walked across the hall, and looked at someone else’s screen to find the answer. We shouldn’t have to rely on heroes to overcome our own systems. The system itself should be the hero.
The Simplicity of the Host
Antonio C.-P. once told me that the most luxury he ever felt wasn’t in a gold-plated bathroom, but in a small 7-room guesthouse in the Italian Alps. There, the woman who checked him in was the same woman who cooked his breakfast and the same woman who knew exactly which hiking trail would be least muddy after the morning mist. There were no departments. There was only the guest and the host. That is the ultimate goal of streamlined operations: to return to the simplicity of the host.
Unified Role
One person, all functions.
Invisible Tech
Technology as a support, not a barrier.
Restored Dignity
Valuing the customer’s time.
We use technology like Flodex not to add more layers of complexity, but to strip away the unnecessary handoffs that make a customer feel like a nuisance. The goal is to make the technology invisible so the human answer can be visible. When you reduce the number of touches a customer has to endure, you aren’t just improving efficiency; you are restoring dignity.
Mirrors Reflecting Nothing
I find myself back on the phone, the Skåne wind rattling the window pane. I’ve been on hold for 17 minutes now. I am waiting for the finance department to talk to the claims department. I know what will happen. Finance will say the credit hasn’t been issued because the claim hasn’t been closed. Claims will say the claim can’t be closed until finance verifies the original invoice.
The Automated Stand-off
Finance Dept.
Waits for Claim Closure.
Claims Dept.
Waits for Invoice Verify.
They are two mirrors facing each other, reflecting an empty room. Neither of them will pick up a phone and call the other.
They will wait for the system to update. They will wait for the “workflow” to trigger an automated response. They have outsourced their agency to a piece of code that was written by someone who has never been to Storgatan 17.
The Moment of Truth
If we want to build institutions that last, we have to stop optimizing for the department and start optimizing for the moment of truth. The moment of truth is that split second when a customer asks a question and expects a real answer. If that answer requires a committee, you have already lost. I don’t care how many 5-star reviews you’ve bought or how many “Customer Excellence” awards are hanging in your lobby. If I have to tell you my address 7 times, you don’t know who I am. And if you don’t know who I am, you shouldn’t be taking my money.
The Need for Authority
We need to get back to the idea of the “Generalist with Authority.” Someone who can see the whole problem and has the power to fix it without asking for permission from a vice president of nothing. It requires trust, which is the one thing departmentalization is designed to eliminate. Silos are built on a foundation of distrust-distrust that employees can handle complexity, and distrust that the customer is telling the truth. We replace trust with “process,” and in the process, we lose the person.
Complexity Reduction
65% Potential