The things that never worked

I found out yesterday that something I built had never worked. Not once. Not a single time, across hundreds of real uses, since the day it launched.

Nobody told me.

That silence is worth sitting with. As founders we're trained to interpret user silence as a green light. No complaints, no frantic messages, no one reaching out to say this is broken. So we move on. We build the next thing. We assume what we shipped is running fine.

Sometimes it is. Sometimes silence means people are quietly getting value and life is good. But sometimes silence means something else: the feature was broken, and the workaround was easier than the complaint.

That's what happened here. The thing I'd built to do a job — silently, every time someone tried to use it — failed. And the people using it didn't flag it as broken. They went around it. They adapted. The workaround became normal, and normal became invisible, and invisible meant I never found out.

What the dashboard doesn't show you

When you're running a product you watch your numbers. Traffic. Activity. Errors. A green dashboard feels like permission to move forward. But dashboards only catch what you thought to measure. A silent failure — one that doesn't crash, doesn't log, doesn't send you an alert — doesn't show up anywhere. It just sits there, making your product slightly less than what you intended.

The real artists ship line gets repeated a lot in founder circles. I've said it myself. But shipping without auditing is just moving fast through a list. The question isn't whether you shipped. It's whether what you shipped actually does the thing it was supposed to do — not in the demo, not in the first five minutes after launch, but consistently, for real people, over time.

That's harder than it sounds. You can't test everything forever. At some point you hand it to users and trust the feedback loop to surface what's wrong. But feedback loops have gaps. Low-friction workarounds fill those gaps. And the distance between shipped and working can stay quiet for a very long time.

I fixed the thing yesterday. The fix was fast, once I found it. Most fixes are. The hard part wasn't the fix. It was realizing that for every day the feature wasn't working, I had no idea. And I wouldn't have known if I hadn't gone looking.

So I'm adding go looking to the regular list. Not just shipping. Not just responding to what surfaces. Deliberately going into the quiet corners and asking whether what's supposed to work actually does.

The things you don't audit are the things you don't know are broken.