Closed Enough to Break Alone
When something stops working, the question that decides whether you can fix it isn't how complicated the thing is. It's whether anyone, anywhere, ever wrote down what's inside.
That sounds obvious once you say it, but the intuition runs the other way. We assume a simple device is inherently more fixable than a complicated one, that more moving parts should mean more ways to go wrong and more places for a failure to hide. Sometimes that's true. But it isn't the variable that decides your options once the thing has actually failed. The variable is whether there's a lower layer you can reach, one the friendly interface doesn't control.
Take a piece of software with a dashboard that shows you almost everything, except the one flag that's currently wrong. You delete a thing, the dashboard says it's gone, you go to recreate it, and the system tells you it still exists somewhere. The dashboard wasn't lying, exactly. It made an editorial decision about which state was worth surfacing, made by someone who never anticipated your specific sequence of actions. If there's an API underneath that dashboard, you're fine. You go around the curated view, call the raw endpoint, find the leftover record, delete it directly. The failure was total from the dashboard's point of view and fully recoverable one level down. The dashboard hid the problem. It never owned the problem.
Now take a consumer device with the same category of failure: a state that's wrong, and an interface that won't show it to you. Except this time there's no lower layer. No API, no service manual, no schematic, no forum thread where someone reverse-engineered the protocol out of boredom. The board is potted, the firmware is signed and closed, the support line reads from the same script whether or not your failure matches the three cases it was written for. When the interface can't represent your problem, you have nothing to fall back to, because the interface was the entire documented surface. There was never a second layer. There was just the one layer, and now it's wrong, and nothing sits underneath it to appeal to.
That's the actual axis: not simple versus complex, but documented versus undocumented. Put more precisely: does the state of this thing exist anywhere outside of whatever's currently telling you it's fine? A watch with a stuck gear and a print-run service manual from decades ago is more repairable than a sealed earbud from six months ago, even though the watch has an order of magnitude more moving parts. Mechanical complexity was never the obstacle. The obstacle is a company deciding that documenting the interior wasn't worth the support cost, and that decision travels with the object for its entire working life. It doesn't matter how good the engineering was at launch. It matters whether the engineering left a trace someone outside the company can read.
That decision is rarely made out of malice. It's usually just triage: this failure mode looked rare enough, this edge case unlikely enough, that publishing the internals wasn't worth the engineering time or the competitive exposure. Reasonable, from inside the company, on the day it's made. But the cost of that call doesn't stay inside the company. It gets stored, quietly, in every unit that ships, and it comes due only when something breaks in a way nobody planned for. By then the person paying it is whoever owns the thing, standing in front of a device that won't reset, with a support line reading from a script written for someone else's failure.
The fix, if you can call it that, isn't complexity reduction. It's leaving a documented seam somewhere: an API underneath the UI, or a schematic that outlives the product line. None of that has to be visible in ordinary use. It only has to exist for the day ordinary use stops working and someone needs a lower layer to reset against. Most products never need it. The ones that do need it badly, and by then it isn't a feature request, it's the only thing standing between a repair and a landfill.
Closed systems don't fail more often. They're just closed enough to break alone.