H3.03.3no humor over real lossdesignresearch

Humor cannot paper over real loss

Aliases: error humor · mascot error · loss-calibrated tone

What it is

When money, data, permission, or someone else’s rights are already damaged—or still unknown—the recovery surface cannot shrink the situation with jokes, mascots, or celebratory rhetoric. Not using humor to dissolve real loss targets the moment when loss has not yet been named: people are judging whether the thing still exists and whether it can be retrieved. A wisecrack reads as “you do not take this seriously.” A harmless, immediately self-healing hiccup may keep product personality. That is not this entry’s object.

Why it happens

Humor needs shared psychological distance. When loss or uncertainty already fills attention, distance is zero and the joke is read as contempt. People re-estimate the product: if even “was I charged” needs a mascot, the recovery button that follows is no longer trusted. Repeat failure turns the same gag from cute to mockery; willingness to recover drops faster the second time. Jokes also occupy the slot that should state scope, so working memory handles the punchline and the outcome sentence is squeezed out. Tone has to track loss: the larger and the less certain, the straighter the sentence.

Studying it

Cross loss (none / reversible / irreversible or unknown) with tone (plain / mild personification / joke) and watch how people judge state and whether they continue.

Independent variables: loss type, reversibility, whether the failure has already repeated, whether the joke occupies the outcome sentence. Dependent variables: accuracy of state judgment, feeling dismissed, willingness to keep recovering, underestimation of severity.

Do not use real charges to test humor in high-loss conditions. Use simulated balances or a paragraph just written. Gags must be retested per language; funny in the source language is not acceptable in the target.

Where it stops holding

A brand may stay light on empty states, waits, and low-risk refreshes if there is no loss and no pending transaction. Security alerts, payment disputes, and frozen accounts must be plain. Empathy and calm are not mechanical coldness; what is forbidden is asking a harmed person to tend the brand’s mood. A user describing their own failure with a joke is not a license for the product to joke back.

Applying it

  • Tag error situations by loss; high-grade templates ban puns, mascot lines, and self-display such as “we messed up!”
  • Write state, scope, and next step first, then delete any sentence that only works as a punchline.
  • When the same error upgrades from harmless to harmful (retry still fails, a charge is discovered), switch tone to plain automatically; do not keep the first screen’s joke.
  • Verify with a script in which money may have been taken but is not yet certain: “how seriously do you think they are treating this?” and “do you still trust this retry?” If severity is talked down or the button is not trusted, the joke has already dissolved the loss.

Related

  • Within the group: H3.03.1 Blame-the-user copy blocks recovery · H3.03.2 Internal jargon is not an error explanation
  • Adjacent: T2.04 Error copy · P1.12 Humor boundaries in error scenarios · H7.13 Payment failure and unknown state
  • Search terms: humor in errors · loss-calibrated tone · error severity

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/H3.03.3