The Cost of Small Problems

A package didn’t arrive this week.

The details hardly matter. An app said it had been delivered. It hadn’t. There was no package, no photo, and no clear explanation of what had happened. What followed was familiar to anyone who has spent time dealing with modern customer service: messages, waiting, uncertainty, and the realization that a problem which should have taken five minutes to resolve might consume considerably more time and attention.

What surprised me was how angry I became.

At first, I assumed I was upset about the money. The order was around thirty dollars. A few household items. Nothing particularly remarkable. Laundry sanitizer. Stain remover. Jet-Dry.

The more I thought about it, the less convincing that explanation became.

What I have been realizing lately is that problems do not have fixed sizes.

A missing package is not a thirty-dollar problem. It is a thirty-dollar problem relative to everything surrounding it.

There was a time in my life when a missing order would have been an inconvenience. I would have reordered the items, driven to a store, or simply absorbed the loss while waiting for a refund. The problem would have remained roughly the same size as the amount printed on the receipt.

Today, the math feels different.

A missing package is one thing when you have a car, flexible finances, and multiple alternatives. It is something else entirely when replacing it requires planning, transportation, waiting for refunds, and deciding which other expenses may need to be postponed. The dollar amount remains unchanged. The margin surrounding it does not.

I found myself explaining this to a friend recently when I said that I hate how my life exists at a different scale now.

For days I kept turning that sentence over in my head before realizing that scale was not quite the right word. What I was really describing was margin.

The package had not become more expensive. The consequences of losing it had become more significant.

The order itself was unremarkable. Laundry sanitizer. Stain remover. Jet-Dry. The sort of household purchases that rarely attract attention when they arrive successfully.

The laundry sanitizer helps maintain a household that includes a six-year-old child and a partner whose work often involves cleaning public spaces. The stain remover helps extend the life of clothes I would prefer not to replace prematurely. The Jet-Dry was mostly a small gesture for someone who genuinely enjoys optimizing a dishwasher.

None of those purchases are dramatic.

That is precisely the point.

Much of adulthood consists of small acts of maintenance. The dishes get washed. The clothes last another year. The internet works. The package arrives. The system functions.

We rarely notice any of it because successful infrastructure disappears into the background. Its success is measured by its absence from our thoughts.

Failure is different. Failure reveals the system.

Two weeks earlier I had spent my days helping operate an election. Every chair, every touchscreen, every translation, every checklist existed to make participation possible. Most voters never noticed those systems because they worked.

A missing package revealed something similar. The package was not the story. The story was the invisible network of transportation, logistics, software, customer service, and trust that normally allows the package to arrive without requiring a second thought.

Most infrastructure becomes visible only when it breaks.

What frustrated me most was not the missing package. It was the way a trivial problem immediately began demanding more attention than it deserved. A simple transaction transformed into a dispute. An errand became a process. A routine purchase became another problem requiring management.

The older I get, the more convinced I become that anxiety is often less about the size of a problem than the anticipated cost of resolving it.

A problem that can be fixed quickly remains small. A problem that requires phone calls, documentation, waiting periods, appeals, and uncertainty begins to expand. Not because the original issue changed, but because the effort required to navigate the solution grows larger than the problem itself.

Perhaps that is why so many people feel exhausted despite the fact that most of the individual challenges they face seem relatively minor. We are not carrying one enormous burden. We are carrying dozens of small ones, each demanding a little more attention than it should.

For most of my career, I worked on systems at scale. I spent years helping organizations understand how people moved through complexity, where friction appeared, and what happened when systems failed. What I rarely considered was how differently those failures are experienced. A missing package is a rounding error when alternatives are plentiful. It becomes something else when the alternatives disappear.

That realization has been uncomfortable because it forces me to confront more than a failed delivery. Some of the margin I once relied upon no longer exists. Some of that is circumstance. Some of it is the consequence of choices I made during years when addiction narrowed my world and reduced my options.

The package was only thirty dollars.

What arrived at my door instead was a reminder that problems are rarely measured by their objective size. They are measured by the resources available to absorb them.

I spent years helping build and improve systems for other people. Lately, I have been learning what those same systems feel like from the outside.

That may have been the real delivery.