The rhythmic clicking of a ballpoint pen is usually the background noise of my existence, but today it feels like a metronome for a slow-motion disaster. We are 45 minutes into a meeting that was supposed to last 25, and the oxygen in the room is being systematically consumed by a debate over a 0.05% edge case. The Vice President of Strategy is leaning forward, his eyes bright with the kind of fervor usually reserved for religious awakenings or new keto diets, explaining why we need a custom-coded notification system for the three clients who might-just might-request a delivery on a leap year Sunday during a solar eclipse. Meanwhile, the standard intake form that 85% of our users struggle with every single day is still a bloated, 15-page PDF that requires a printer, a scanner, and a blood sacrifice to submit correctly. I find myself staring at the dust motes dancing in the light of the projector, wondering at what point we decided that the mundane was beneath our dignity.

I’m Morgan B., and I spend my weeks coordinating hospice volunteers, a role that should, in theory, be about the simplest human needs. But even here, in the quiet hallways where the stakes are as final as they get, the siren song of the ‘strategic’ exception lures us away from the ‘obvious’ necessity. Last month, our leadership team spent 15 hours debating the logistics of a virtual reality program for homebound patients-a beautiful idea, truly-while the 5 basic oxygen tank suppliers we use still haven’t received an updated contact list in 205 days. We are architects of the extraordinary who can’t seem to fix a leaky faucet.

The Myth of Standardization

I fell into a Wikipedia rabbit hole last night-one of those 3:15 in the morning ventures where you start at ‘List of common misconceptions’ and end up reading about the development of standardized screw threads in the 1800s. It’s fascinating, really. Before Joseph Whitworth came along in 1841, every workshop had its own thread size. If you lost a bolt, you couldn’t just buy a new one; you had to custom-make a replacement. It was a nightmare of ‘bespoke’ solutions. We think we’ve moved past that, but in the digital and corporate world, we’ve just moved the mess to our workflows. We treat every slight deviation from the norm as a puzzle to be solved with a new, complex layer of software or policy, while the standard gauge-the thing everyone uses-is left to rust.

Why does the edge case get the funding while the everyday process gets the shrug? I think it’s because solving an edge case feels like an intellectual victory. It’s a trophy. It says, ‘We are so sophisticated that we have even considered this improbable scenario.’ It feels like innovation. Fixing a clumsy, confusing, and fragile standard process, on the other hand, feels like chores. It feels like admitting we’ve been doing it wrong for the last 15 years. There is no glory in making a form shorter. No one gets a promotion for ensuring the basic email auto-responder actually contains the correct phone number. And yet, that phone number being wrong is exactly what causes 155 support tickets a week.

The Glory of the Trivial

I’ve been guilty of this myself. I once spent 5 days designing an elaborate ‘Volunteer Recognition Matrix’ with 25 different tiers of achievement based on hours served and types of patient interaction. I was so proud of the complexity. It was a masterpiece of Excel engineering. But when I presented it, one of my veteran volunteers looked at me and said, ‘Morgan, this is great, but could you just make sure there are actually pens that work in the sign-in room?’ I had spent $625 worth of my own billable time on a matrix while ignoring a $5 problem. I felt the heat rise in my neck. I’m probably still making that mistake in different ways every single day, but at least now I try to catch the pen-clicking before it becomes a project plan.

There is a peculiar comfort in the ‘unusual’ problem. It’s a distraction from the crushing weight of the familiar. In the shipping industry, for example, everyone wants to talk about the latest drone delivery technology or autonomous vessels. It’s sexy. It’s futuristic. But if you talk to the people on the ground, they’ll tell you that the real revolution wasn’t a computer chip; it was a metal box. The standardized shipping container. It didn’t solve a ‘custom’ problem; it solved the most basic, boring problem in the world: how to move stuff from a ship to a truck without touching it 45 times. When you look at companies like AM Shipping Containers, you see the power of getting the ‘box’ right. They understand that while everyone is chasing the 1% of ‘high-concept’ modular architecture, the real value lies in the 95% of practical, sturdy, and reliable use cases that keep the world turning. If the box isn’t right, the fancy custom interior doesn’t matter.

The User Hurdle vs. The User Journey

We are currently obsessed with the ‘user journey’ for the person who has everything, yet we ignore the ‘user hurdle’ for the person who just wants to get their job done. In my hospice work, the ‘obvious case’ is a family that needs to know what to do when their loved one’s breathing changes. It’s a scary, standard, universal moment. We should have the most streamlined, clear, and compassionate response for that. But instead, our internal systems are often more concerned with the ‘edge case’ of a patient who has three different insurance providers and a primary residence in a different state. We’ve built a cathedral of complexity around the exception and left the common room with a dirt floor.

I remember a particular volunteer, Sarah. She’s been with us for 15 years. She’s seen three different ‘strategic overhauls’ of our volunteer portal. Each time, the IT department adds new features-tracking for specialized certifications, a social media integration, a mood-tracking emoji system. And each time, Sarah calls me because the ‘login’ button has moved to a sub-menu under ‘Resources’ and she can’t find it. We are solving problems Sarah doesn’t have while creating new ones for the only thing she needs to do: tell us she’s arrived at a patient’s bedside. It’s a form of institutional gaslighting. We tell our staff and our customers that we are ‘improving’ things, but what we are actually doing is satisfying our own desire for novelty.

The Great Stink of Workflow Inefficiency

I’ve been reading about ‘The Great Stink’ of London in 1858-another Wikipedia gem. The city was obsessed with ‘innovative’ ways to deodorize the Thames using lime and carbolic acid. They were trying to solve the ‘smell’- the edge case of the symptom-while the obvious case, the fact that all the sewage was dumping directly into the water they drank, was considered too massive and ‘boring’ to tackle. It took a heatwave that literally made the Parliament building uninhabitable for them to finally build the basic, standardized sewer system that actually solved the problem. We are currently pouring carbolic acid on our workflows, hoping the smell of our inefficiency goes away, while refusing to lay the pipes for a standard process.

I recently tried to change my own approach. I took the 5 most common complaints from my volunteers-the ones I usually ignore because they aren’t ‘strategic’-and I decided to spend my entire week on just those. No new projects. No ‘visioning’ sessions. Just fixing the things that actually happen every day. It was the most exhausting week of my year. It turns out that fixing the ‘obvious’ is incredibly hard. It requires untangling years of ‘temporary’ fixes that became permanent. It requires admitting that our core logic was flawed from the start. It’s much easier to just build a shiny new feature on top of the rubble.

The Fear of the Ordinary

I suspect we do this because we are afraid of the scale of the ordinary. If we admit that our basic workflow is broken, we have to admit that we’ve been wasting 45% of our time for years. That’s a heavy realization. It’s much more pleasant to believe that we are doing great, and we just need this one little custom ‘leap year’ feature to be perfect. It’s a form of procrastination. We work on the 5% so we don’t have to face the 95%.

In the boardroom today, the VP finally stopped talking. There was a silence that lasted about 15 seconds. I should have kept my mouth shut. I should have just let the eclipse-notification project go through. But instead, I asked, ‘How many people actually asked for this?’ The answer, as it always is, was ‘None yet, but we want to be proactive.’ Proactive. The word that justifies a thousand wasted hours. I looked at my notes, where I had written down the names of 25 volunteers who still can’t access the training manual because the link is broken. I didn’t say anything else. I just watched the pen-clicker start up again, 75 clicks a minute now.

A Radical Commitment to the Ordinary

We don’t need more ‘solutions’ for things that might happen. We need a radical commitment to the things that *do* happen. We need to stop treating the standard case as a footnote to the exception. The soul of an organization isn’t found in its ability to handle a crisis; it’s found in the friction of its Tuesday afternoons. If we can’t get the Tuesday right, the solar eclipse won’t save us.

I’m going back to my office now to check the pens in the sign-in room. It’s not strategic. It won’t get me a mention in the quarterly report. But it’s a standard problem with a standard solution, and for today, that feels like enough of a revolution. I might even fix that typo on Mrs. Gable’s form. It’s only been there for 15 years, after all. Maybe it’s time to stop waiting for a ‘strategic’ reason to be better.