Sarah gripped the cheap BIC pen, the one with the teeth marks on the cap, and circled the number $84.21 on her billing statement for the third time. The ink was starting to bleed through the thin paper, leaving a blue stain on the oak laminate of her kitchen table.

She had been on hold for fourteen minutes, a duration long enough to notice the specific way the dust motes danced in the afternoon light but not long enough to achieve any sense of inner peace. When the line finally clicked, Sarah, who had prepared a concise three-sentence summary of her problem, found herself speaking to a man named Kevin.

The problem Sarah faced was a nested doll of failures. Her order had arrived four days late, which was a Shipping problem. One of the items inside was cracked and leaking a viscous, citrus-scented fluid, which was a Product problem. And, most importantly to Sarah’s immediate stress levels, she had been charged twice for the privilege of this disaster, which was a Billing problem.

Kevin could see the double charge, certainly. He could even initiate a partial reversal. But his screen-the interface that dictated the boundaries of his reality-would not allow him to see why the shipping was delayed or authorize a replacement for the broken unit.

“I can handle the $84.21, Ms. Miller,” Kevin said, his voice echoing the practiced empathy of a man who had said this forty times since lunch. “But for the damaged item, I’ll need to transfer you to Product Integrity. And for the shipping delay credit, that’s a Logistics ticket.”

– Kevin, Customer Support

The Architecture of Inefficiency

We have entered an era of hyper-specialization where the “Fixer”-that legendary figure who could see a problem and simply resolve it-has been systematically dismantled in favor of the Specialist. The theory, born in the mid-twentieth century and refined by the cold logic of digital efficiency, suggests that if you break a task into enough tiny pieces, the machine runs faster.

But the theory forgets that a problem is not a machine. A problem is an event, and when you shatter an event into three different departments, you don’t solve it. You just distribute the frustration.

Lessons from the Archives

In my world-museum education and archival management-we have a process called “Accessioning.” It is a rigorous, often tedious sequence of events that brings an object into a permanent collection. If a Roman coin from the 2nd century arrives at our loading dock, it isn’t tossed from person to person. A single registrar usually oversees the entire intake.

They check the legal title (did we actually buy this?), the physical condition (is it corroding?), and the provenance (where has it been for 1,800 years?).

If we worked the way modern corporations do, we would have a “Legal Specialist” look at the deed, then put the coin in a box. Three days later, a “Metals Specialist” would open the box to check for rust, but they wouldn’t know if the coin was stolen. Then a “History Specialist” would look at the emperor’s face but wouldn’t know if the museum actually owned the thing.

If the coin got lost in between, no one would be responsible because everyone did their specific job perfectly. The coin’s history is a single, integrated truth. To fragment the data is to lose the object.

The Lathe Incident

I made a mistake once that still keeps me awake when I try to go to bed early, as I did tonight before the weight of these thoughts dragged me back to the desk. I was coordinating a traveling exhibit on industrial tools. I had split the logistics into “Transport,” “Insurance,” and “Installation.” I thought I was being sophisticated. I thought I was being “scalable.”

Because the Insurance person didn’t talk to the Installation person, a 400-pound lathe was delivered to a gallery with a floor load limit of 200 pounds. The Transport team did their job-they delivered it. The Insurance team did theirs-they covered the transit.

But because no one owned the whole movement of that lathe from the truck to the pedestal, the floorboards groaned, cracked, and nearly sent a piece of 19th-century history into the basement. I was the one who had fragmented the responsibility, and I was the one who had to explain the splinters in the floor.

The API Marketplace

We see this fragmentation everywhere, but it is particularly galling in the digital marketplace. You buy a thing, and the “store” is really just a front-end for a dozen different third-party APIs. The payment processor is in Ireland, the warehouse is in Ohio, the customer service bot is hosted on a server in Virginia, and the actual brand owner is a holding company in a skyscraper that doesn’t even have a loading dock.

When the “thing” goes wrong, you are the only one who sees the whole picture. To the company, you are a collection of disparate tickets. This is why there is a growing, almost desperate hunger for “end-to-end” competence.

It’s the reason people are returning to small shops and specialized boutiques that refuse to scale themselves into oblivion. There is a profound relief in talking to a person who knows the product, knows the stock room, and knows how to hit the “Refund” button without asking three supervisors for a digital key.

When a business decides to own the entire experience-from the authenticity of the device to the final delivery at your door-they are rejecting the fragmentation that has made modern life so exhausting. They are choosing to be the registrar with the Roman coin, holding the whole story in their hands. They understand that a customer doesn’t want a “Shipping Specialist”; they want their package.

Trapped in the Cage

The tragedy of the specialist is that they are often talented people trapped in a cage of “Not My Department.” Kevin, the billing guy Sarah was talking to, might be a brilliant problem solver in his private life. He might be the kind of guy who can fix a lawnmower with a paperclip or navigate a boat through a storm.

But at his desk, his brilliance is filtered through a software suite that only allows him to click four buttons. He is paid to ignore the “broken unit” part of Sarah’s story. He is paid to be a fragment.

This creates a psychological phenomenon I call “Administrative Gaslighting.” You know you have one problem. The person on the phone insists you have three. You begin to wonder if you are the crazy one for thinking that a single transaction should be treated as a single event.

We’ve traded the Generalist for the Specialist because the Specialist is cheaper to train and easier to replace. You can teach someone to handle “Billing” in a week. Teaching them to understand the entire ecosystem of a business, the nuances of the product, and the logistics of the supply chain takes months, maybe years.

The Bedrock of Trade

Ownership means that if a customer calls with a leaking box and a double charge, you don’t transfer them. You fix it. You go down to the warehouse, or you call the warehouse, and you stay on the line until the new tracking number is generated.

But our current systems are designed to prevent that kind of initiative. Initiative is “unstandardized.” It’s hard to track in a spreadsheet. It doesn’t fit into the “Key Performance Indicators” that measure how many calls Kevin can take per hour.

If Kevin actually solved Sarah’s whole problem, he would be on the phone for thirty minutes, his “Call Volume” metric would drop, and his manager would give him a “Performance Improvement Plan.” The system is literally designed to keep the problem broken.

The Artificial Scent of Defeat

Sarah eventually got her refund, though it took two more phone calls and an email thread that involved four different people. By the time the $84.21 was back in her account, she wasn’t happy; she was just tired. The victory felt like a defeat because of the sheer amount of life-force she had to expend to achieve it.

She looked at the leaky box on her table. The citrus smell was starting to fill the kitchen, a sharp, artificial scent that would forever be associated in her mind with the sound of midi hold music. She realized that she didn’t just want her money back. She wanted the time back.

She wanted the version of the world where things worked the way they were supposed to-not as a series of disconnected modules, but as a single, coherent promise.

We are all Sarah, leaning against our kitchen windows, watching squirrels, waiting for someone to take responsibility for the whole box. We are all waiting for the “Fixer” to come back from the exile of specialization. Until then, we are just the glue holding the fragments together, trying to make sense of a world that has been optimized into pieces that no longer fit.

I finally turned off the light in my office. The house was quiet, save for the hum of the refrigerator and the distant sound of a siren. I thought about the Roman coin in the museum, sitting in its velvet-lined tray, whole and understood.

It’s a small comfort, but in a world of silos, it’s enough to finally let me sleep. Responsibility isn’t something you can delegate in percentages. It’s a binary state.

You either have it, or you are just another person on the line, telling someone else to wait for the click.