Andrés is staring at the 48th unread email of the morning, and the coffee in his mug has developed a thin, oily film that suggests it was poured at least 38 minutes ago. He doesn’t drink it. He doesn’t even see it. His focus is entirely on a PDF attachment labeled ‘Final_Artwork_v12_revised_FINAL.’ This is the 8th time he has looked at this specific label for a shipment of recycled bathroom tissue. He knows the hex code for the blue border by heart, yet the system demands his digital signature before the plates can be cast in a factory 8008 miles away. If he clicks ‘approve,’ the machines start humming. If he goes to lunch, the supply chain stops breathing. This is what we call organizational discipline, but in reality, it is a slow-motion hostage situation.

There is a peculiar smell to an office that relies on a single point of human failure. It’s a mix of ozone from the printers and the sour tang of collective anxiety. Everyone knows not to bother Andrés during the month-end close, yet they hover near his cubicle like moths around a flickering bulb. They need his eyes on the SKU updates, his thumb on the shipment releases, and his memory for the specific nuances of a sample request that was filed 18 months ago. He is the unofficial operating system of the entire department. On paper, this is centralization. In practice, it is a glorification of the choke point. We build these structures because it feels safer to have one ‘unusually competent person’ holding the keys than to trust a distributed process that might let a mistake slip through. We prioritize the avoidance of errors over the fluidity of growth, and we call the resulting paralysis ‘governance.’

I found a twenty-dollar bill in the pocket of my old jeans this morning, a small, crinkled miracle that felt like getting away with something. It reminded me that the best things in life are often the ones we didn’t over-manage. But in the corporate world, we are terrified of the unmanaged. We treat every SKU and every artwork revision like a potential catastrophe. We create a reality where Andrés cannot take a Friday off without causing a 28-hour delay in the logistics queue. It is a heroic competence that functions exactly like an addiction. The organization gets a high from knowing Andrés will catch the mistakes, but it loses the ability to function without the fix. It’s a tragedy disguised as an achievement.

The Cemetery Keeper’s Wisdom

João A. understands this better than most, though he has never worked in a glass-walled office or looked at a logistics forecast. João is a cemetery groundskeeper, a man who has spent the last 38 years tending to the silent residents of a hillside in the Azores. He knows exactly where the roots of the old cedar tree interfere with the 1908 plot boundaries. He knows which headstones lean because the soil is sandy and which lean because the mason was lazy. João is the only person who holds the mental map of that terrain. When the municipality tried to digitize the records, they realized the official ledger was missing 88 entries that only João could identify by the shape of the moss or the proximity to the iron gate. João is a master of his craft, but he is also a bottleneck. If João decides to retire, the history of those 488 graves becomes a series of guesses. We celebrate João’s dedication, but we ignore the fragility of a system that requires his specific, unreplicable presence to remain coherent.

The Fragility of Dedication

We do this in manufacturing all the time. We find a vendor, we establish a rhythm, and then we consolidate every single decision-making power into one desk. We think we are streamlining. We think we are ‘leveraging’-a word I’ve come to loathe-our human capital. What we are actually doing is creating a single human throat for the entire enterprise to be strangled by. The irony is that the person at the center of the bottleneck is usually the most loyal, the most hardworking, and the most exhausted person in the building. They are the ones who answer emails at 11:08 PM not because they want to, but because they know that if they don’t, the morning will start with a 58-person pileup of blocked tasks.

The cost of this dependency is hidden until it becomes catastrophic. It shows up in the ‘urgent’ labels that aren’t actually urgent, but feel that way because they’ve been sitting in a queue for 28 hours. It shows up in the forecasts that are always 18% off because the person who knows the real numbers is too busy approving sample requests to update the spreadsheet. It shows up in the way the team talks-everything is a ‘quick question’ that requires a 48-minute explanation. We have traded resilience for the illusion of control. We want to make sure the artwork is perfect, so we make sure only one person can look at it. We want to make sure the SKU is accurate, so we funnel it through a single validator. We are so afraid of a small mistake that we invite a total system collapse.

I once saw a company lose a $48888 contract because their ‘Andrés’ was at a funeral and no one else had the password to the secondary quality-control portal. It wasn’t that the others weren’t capable; it was that the process had been so tightly wound around one individual that the very idea of someone else stepping in felt like a violation of protocol. The protocol had become a suicide pact. We see this in the way we handle sourcing and procurement, especially with complex items like customized paper products. The technical specifications, the GSM weights, the roll diameters-these are all points of data that should live in a shared, transparent environment. Instead, they often live in the ‘Sent’ folder of a single harassed employee.

The Process Over the Person

When you are dealing with a partner like Ltd., you start to realize that the technical details of a product-like the exact dimensions of a toilet paper roll-are only as useful as the system that manages them. If your internal approval process is a tangled mess of ‘Andrés must see this first,’ even the most efficient manufacturer in the world can’t save you from your own delays. The goal shouldn’t be to find a person who can handle the chaos; it should be to build a process that prevents the chaos from concentrating in the first place. You need a partner that understands the specs, but you also need a team that isn’t afraid to make a decision without waiting for the High Priest of SKUs to return from his lunch break.

I remember a specific instance where a shipment of 888 cartons was held at a port because the ‘final’ approval for the pallet stacking pattern hadn’t been checked by the one guy who knew how the warehouse racks were spaced. He was out with the flu. For 8 days, that cargo sat in the salt air, racking up storage fees that eventually totaled $1258. All because the ‘authority’ was a person, not a protocol. It’s a form of organizational vanity to think that we are so special that our work requires constant, high-level manual intervention. Most of what we do is repeatable, or it should be. If it isn’t repeatable, it isn’t a business; it’s a series of improvised miracles.

João A. once told me that he tried to teach his nephew how to read the cemetery soil, but the boy wasn’t interested. The boy wanted to use a drone and ground-penetrating radar. João laughed, but there was a sadness in it. He knew his knowledge was dying with him, but he also knew that the boy’s radar would never fail because it had a headache or wanted to go fishing. There is a middle ground between the coldness of the machine and the fragility of the hero. We find it when we stop asking ‘Who is responsible?’ and start asking ‘How is this verifiable?’ We find it when we stop treating the Andrés of the world as assets and start treating them as warnings. If your top performer is also your biggest bottleneck, you don’t have a talent problem; you have an architecture problem.

The Cost of Heroism

We need to get comfortable with the idea of ‘good enough’ being decided by a system rather than a person. This doesn’t mean lowering standards; it means codifying them. If the artwork meets the 8 predefined criteria, it is approved. Period. It doesn’t need a 9th look from a guy who hasn’t slept in 28 hours. If the shipment update matches the manifest, it moves. If the sample request falls within the $878 budget, it is sent. We have to kill the ‘urgent’ culture by removing the need for urgency. Most urgency is just the sound of a bottleneck being squeezed.

I still have that twenty dollars in my pocket. I haven’t spent it yet. I like the weight of it, the small insurance policy against a bad day. In a way, a well-designed process is like that twenty dollars. It’s there when you need it, it doesn’t require a meeting to activate, and it works whether you’re having a good day or not. It’s the opposite of Andrés. It doesn’t get tired, it doesn’t get sick, and it doesn’t leave the company for a better offer at a firm that promises fewer unread emails. We owe it to the people we work with to stop making them heroes. It’s an exhausting, lonely way to live, and it’s an incredibly dangerous way to run a company. Let Andrés drink his coffee while it’s still hot. Let him look at the 88 unread emails and realize that 78 of them were already handled by a system that didn’t need his permission to exist. That is what real efficiency looks like. It isn’t a person; it’s a path that anyone can walk.

As I look at the clock, it’s 4:08 PM. In many offices, this is when the ‘Andrés’ panic starts-the frantic rush to get the last approvals before the day ends. But it doesn’t have to be this way. We can choose to build something better. We can choose to value the quiet, boring reliability of a clear process over the dramatic, high-stakes rescues of a talented bottleneck. We can choose to let the work flow, rather than letting it pool around a single desk until it turns stagnant. It’s a choice we make every time we design a workflow or assign a task. It’s a choice between a business that grows and a business that just holds its breath, waiting for Andrés to click ‘refresh’ one more time.