System Status: The UX Heuristic AI Is Breaking — and Why That's Product Enshittification

There's a rule so old and so obvious in my field that we sometimes forget to say it out loud. It's number one on Jakob Nielsen's list of usability heuristics, and it's been sitting at the top since before half the people building AI today could ride a bike.

It's called visibility of system status, and it boils down to a single, almost parental idea: tell people what's going on.

That's it. When something is loading, show a spinner. When a file saves, say "saved." When the elevator hears your button press, light the button up so you don't stab it eleven more times like a raccoon attacking a vending machine. Good systems keep you informed about what they're doing, when they're doing it, and — this is the part everyone forgets — why.

It's not a courtesy. It's a right. The user has a right to understand the thing they're using. And I'm here to tell you the AI industry is breaking this rule so thoroughly, so casually, and so often that it has stopped looking like a bug and started looking like a business model.

Let me show you what I mean.

The Profile You Never Asked For

Picture opening your fridge to grab milk and discovering someone has quietly added a roommate. They've been living in there. They have opinions. You did not invite them, you cannot remember hiring them, and when you ask what they're doing, the fridge just hums.

That's roughly the energy of Meta reportedly spinning up AI personas and AI-generated accounts across its platforms — digital "people" with names and faces and posts, populating the same feeds where your aunt shares casserole recipes. Nobody asked for them. Nobody opted in. They simply appeared, acting on the platform, as if they were part of it, with no clear signal of what they were, who made them, or why they were there.

From a system status standpoint, this is the whole heuristic set on fire and rolled down a hill. The system took an action that affects you, gave you no notice, and offered no explanation. You're left doing the thing humans do when a system goes quiet: inventing a story to fill the silence. And the stories people invent about silent AI are never flattering. "Probably harmless" is not where the mind goes. The mind goes straight to "what else is it doing that I can't see?"

And here's the thing — that suspicion isn't paranoia. It's the rational response of a population that already doesn't trust this stuff.

The Numbers Behind the Side-Eye

A YouGov survey from December 2025 put hard numbers on the mood. Roughly 35% of Americans use AI weekly. But only about 5% say they deeply trust it. Trust runs lowest exactly where the stakes run highest — healthcare and finance. The places where a wrong call costs you a kidney or a down payment.

Read that gap again, because it's the whole ballgame. A third of people use AI every week. One in twenty actually trusts it. That means there's an enormous crowd of folks using these tools while holding their nose — relying on something they fundamentally don't believe.

That's not a stable relationship. That's not even a relationship. That's a hostage situation with a friendly UI.

Now layer system status on top. If people already don't trust AI, what does hiding its reasoning do? It confirms every fear they walked in with. Every unexplained recommendation, every silent action, every mystery profile is more evidence for the prosecution. You cannot earn trust from a skeptic by being more opaque. You earn it by opening the hood — even just a crack — and letting them see something that makes sense.

Your users don't need a PhD. They don't need to understand transformer architecture or gradient descent or whatever's printed on the conference lanyards this year. But they absolutely need to be able to ask the system a simple question and get a real answer:

• Why did you recommend this insurance plan and not the cheaper one?

• Why did you flag this line in my budget as a problem?

• Why is there an account here that has my friends but isn't a person?

If the answer to any of those is a hum from the fridge, you've broken the oldest rule in the book.

The Three Uncomfortable Reasons

So why do smart companies, full of smart people, keep violating a heuristic a design intern could recite in their sleep? In my experience it comes down to three reasons, and they get progressively harder to admit out loud.

Reason one: nobody translated it.

The data scientists know how it works. The engineers know how it works. But that knowledge lives in a dialect of math and jargon that never got translated into human. Nobody on the team sat down and asked, "How would we explain this to the person actually using it?" So the explanation simply doesn't exist in a shippable form. This is the most innocent reason, and also the most fixable. It's a translation problem, not a moral one. You have the answer. You just left it in the back room.

Reason two: they're afraid you'll bail.

This one's spicier. Some companies suspect — correctly — that if users truly understood what the AI was doing, a meaningful chunk would walk. "We trained this on your DMs" does not fit gracefully on a welcome screen. So the reasoning stays hidden, not because it's hard to explain, but because the explanation is bad for business. That's not a UX gap. That's a choice. And it's a choice that treats your user's consent as an obstacle rather than the entire point.

Reason three — the one nobody says at the all-hands: they don't actually know.

This is the black box problem, and it's the scariest of the three because it's frequently true. With many large models, the people who built them genuinely cannot tell you why it produced this specific output instead of that one. Not because they're hiding it. Because the honest answer is a shrug wearing a lab coat. You can't show system status for a process you can't follow yourself. So you ship the magic, cross your fingers, and hope nobody asks the "why" out loud at a moment that matters — like, say, when it's denying someone's medication coverage.

Take a breath and look at those three side by side. We didn't explain it. We won't explain it. We can't explain it. Whichever one is true on a given Tuesday, the user gets the identical experience: a system acting on their life with no visible reasoning. The motive is invisible to them. Only the silence comes through.

This Is Drift, Wearing a Hoodie

Here's where it connects to everything I've been circling for weeks.

Every one of those three reasons is a form of organizational drift — the slow slide from letting signals shape your decisions to gathering signals and then ignoring them. And the loudest signal in the room is that trust number. Five percent. The companies can see it. It's in the surveys they read, sometimes the surveys they commission. They know users don't trust the thing. They know visibility of system status is the cheapest, oldest, most proven way to start fixing that.

And they mostly don't do it.

That's the tell. It's not an ability problem — they could ship an "explain this recommendation" button next quarter if they wanted to. It's a motivation problem. The trust gap is visible, the fix is known, and the will to act on it just isn't there, because narrative and growth are pulling harder than honesty. They can read the room. They've simply decided the room doesn't get a vote.

Why I Call It Enshittification

There's a word for what happens when a product slowly gets worse for the people using it while getting better for the people running it. It's a deeply unscientific, deeply correct word: enshittification.

It's the arc every degrading product follows. First it serves you. Then it serves the business at your expense. Then it just sort of exists, extracting value while you wonder when it stopped feeling good to use. And hiding system status is one of the purest expressions of that slide, because it's the moment a product stops treating your understanding as something it owes you and starts treating it as friction to be minimized.

When an AI quietly creates a profile you never sanctioned, nudges your budget for reasons it won't share, or steers you toward an insurance plan with motives kept in the dark — that product is no longer working for you. It's working on you. The difference is one preposition and your entire dignity as a user.

And the maddening part is how unnecessary it all is. Transparency isn't expensive. A short "here's why" costs a fraction of what it costs to claw back the trust you torch by staying silent. The companies winning the actual ROI in AI, the ones whose users stick around, tend to be the ones who let people see a little of the wiring. Turns out humans forgive a system they understand far faster than one that hums at them.

What I'm Actually Asking For

I'm not asking anyone to publish their model weights or live-stream their training runs. I use these tools every day; I want them to succeed. I'm asking for something my profession decided was non-negotiable decades ago, long before "AI" became the word you legally have to say four times per earnings call.

I'm asking for visibility of system status. The user's plain, boring, foundational right to know what the system is doing, when, and why.

So here's the move, and it's the same one I keep landing on because it's the only one that works. The next time your team ships an AI feature that acts on a user without explaining itself, name it out loud in the room. Ask which of the three reasons is really driving the silence. Did we fail to translate it? Are we afraid they'd leave? Or do we genuinely not know? Then ask the harder follow-up: which of those is a reason you'd be comfortable defending to the person on the other side of the screen.

Because users don't need to be engineers. They never did. They just need to know why the AI flagged that budget line, recommended that plan, or moved into the fridge without asking.

Give them that, and you've done more for trust than any model upgrade ever will. Hide it, and no amount of magic will save you — because the magic was never in the secrecy.

It was in being worth understanding in the first place.