Mixthinks All articles
Opinion

The Breakage Report Card: Grading Software by How It Fails You

Mixthinks
The Breakage Report Card: Grading Software by How It Fails You

Photo: Profpcde, CC0, via Wikimedia Commons

Every app puts on a show when things go right. The welcome modal, the confetti, the tooltip that calls you a natural. None of it tells you much. The real personality shows up when the wheels come off.

A product's failure states are its unguarded moments. They reveal whether the team expected things to break, whether they respect your time, and whether they think of you as a partner or a problem to be routed to support. You can learn a lot from a five-minute audit of the last five error messages you saw.

The Five-Minute Collection

You don't need a spreadsheet or a special app. Just gather the last five errors you can remember or find. Check your phone's recent screenshots, your email for failed-send notices, your browser tabs for whatever went sideways on Tuesday. If you're drawing a blank, that's fine—open three tools you use daily and try something slightly out of bounds. Upload the wrong file type. Paste a link with a typo. Unplug your Wi-Fi for ten seconds.

The goal is to capture the exact wording, not to fix anything. Write down what the tool said, what you were trying to do, and how you felt in the moment. That last part matters more than it sounds.

Three Questions and a Cost Line

For each error, ask three questions and then one more.

Clarity: Does the message tell you what actually happened? Not "something went wrong"—what went wrong. A file that's too large is different from a file that's corrupted, and both are different from a server that took the day off.

Blame: Who does the message point at? Some errors read like a scolding. "Invalid input" suggests you broke it. "We couldn't reach the server" suggests the tool did. Neither is always accurate, but the choice is never accidental.

Next step: Does it give you a way forward? A retry button, a different format, a link that actually opens, a support path that doesn't feel like a maze. Or does it leave you to guess?

Cost: Did it tell you what you lost? This is the line most tools skip. "Your changes weren't saved" is a very different message from silence. One lets you react; the other makes you wonder if your last twenty minutes of work just evaporated.

Clarity Is a Form of Respect

Vague errors are not mysterious by accident. They're often a decision—someone chose not to write the specific case because the specific case felt like edge-case work. But from the user's side, every error is the main event. You weren't trying to test the system. You were trying to send an invoice, book a flight, or get through a Tuesday.

A clear error message does the translation work for you. "Your PDF is 32 MB. The limit is 25 MB. Try compressing it or splitting it into two files." That's not poetry. It's just honesty, and it saves a support ticket.

The Finger-Pointing Test

Blame is where software values get loud. Tools that blame the user tend to be tools that treat failure as a compliance problem. Tools that own the failure tend to be tools built by people who have watched real users struggle.

You'll see the difference in small wording choices. "You entered an invalid email" versus "That email address doesn't look right—check for a missing @ or a typo." The second one still tells you what to fix, but it doesn't make you feel like you're in trouble. In a consumer app, that's the difference between a shrug and a flinch.

Escape Hatches Beat Explanations

A good error doesn't just explain. It gets you out. Sometimes that means a retry button that preserves your work. Sometimes it means a "download what you have" option. Sometimes it means a contact link that goes to a human instead of a help-center article titled "Why Can't I Log In?"

The worst errors are the ones that dead-end. "Contact your administrator" is a special kind of cruel when you are the administrator. "Please try again later" is fine once. After the third time, it's a confession that nobody on the team knows what's happening either.

What the Report Card Tells You

Once you've scored your five errors, look for the pattern. A tool that fails clearly, owns its mistakes, and gives you a way out is a tool that expects failure and respects the people who encounter it. A tool that fails vaguely, blames you, and offers no exit is a tool that treats errors as a public-relations problem.

That pattern is worth more than a feature comparison. Features tell you what a team can build. Failure states tell you what a team believes about you when things don't go according to plan.

The Takeaway

You don't need to run this audit every week. Once a quarter is enough. But when you're deciding whether to keep a tool, renew a subscription, or move your workflow somewhere else, don't just look at the demo. Look at the last time it broke.

If it told you what happened, what it cost you, and how to recover without a support ticket, that's a product with good manners. If it left you guessing, that's not a bug. That's the product.

All Articles

Related Articles

The AI Plus-One Test: When an Embedded Feature Earns Its Seat

The AI Plus-One Test: When an Embedded Feature Earns Its Seat

Buy the App That Says No: A Five-Minute Test for Software Restraint

Buy the App That Says No: A Five-Minute Test for Software Restraint

The Half-Life of a Good Prompt

The Half-Life of a Good Prompt