P1.12.3Humor degrades the information in the same copydesignresearch

Pairing a punchline with instructions someone needs to remember costs the instructions

Aliases: information cost · humor and memory · cognitive load · advertising recall

What it is

When humor and critical information share one piece of copy, they compete for processing resources: the reader spends cognition on the punchline, and the retention of content that must be remembered and acted on — parameters, steps, warnings — drops. This is humor's information cost: the joke does not merely occupy space, it takes memory. What ends up remembered is typically the gag itself, not the message the gag was carrying. The cost peaks in safety warnings, error-recovery steps, and permission explanations, because there the information must be taken away in one pass, often with no second chance.

Why it happens

The cost arises at decoding. Resolving a punchline is real cognitive work: noticing two interpretations collide, searching for the resolution cue, cashing in the incongruity — each step consumes working memory and attention, which is precisely the expenditure called cognitive load. Within one sentence, that budget belongs to the information, so encoding of the message is discounted while attention is withdrawn. On top of the competition comes a second bias: the punchline is the most distinctive, most unexpected element of the sentence, and distinctive stimuli are privileged in both encoding and retrieval — the joke is written into memory deeper than the prose around it. The two effects compose into an asymmetry: the information loses resources at encoding, then is eclipsed by the joke at recall; the user walks away with the gag, and the content it was supposed to ferry stays where it was.

Studying it

  • Paradigms: two evidence lines. Advertising-effectiveness research treats humor as a property of whole ads and measures brand recall and message-point recall after real or simulated exposure — ecologically valid, but humor cannot be separated from the other creative elements. Memory laboratories use list paradigms mixing humorous sentences with neutral ones under free recall and recognition — cleanly separating "how much of the joke itself is remembered" from "how much of the surrounding material is remembered," at the cost of material divorced from real reading.
  • Variables: independent variables include humor presence, type, and message relevance (relevant versus unrelated humor manipulated separately), and available cognitive capacity (for example, via a secondary task); dependent variables include message-point recall, comprehension accuracy, recognition speed, and compliance in warning and instruction scenarios.
  • Use in interface research: evaluating the net effect of inserting humor into error copy, permission explanations, and onboarding text, with recall of critical content and subsequent task correctness as the primary outcomes — not "was it funny" as the verdict on the copy.
  • Methodological cautions: the direction of the effect is contested. The review tradition on humor in advertising (Weinberger and Gulas's classic review and subsequent meta-analyses) steadily supports humor raising attention and liking; its effect on message recall and comprehension is inconsistent across studies, positive in some and negative in others. "The humor was remembered" and "the ad's content was remembered" are two different dependent variables, and conflating them reverses the conclusion. Most evidence also comes from low-stakes, time-pressure-free viewing, and extrapolating it to high-stakes reading such as error recovery has no basis.

Where it stops holding

The cost scales with how much must be remembered from the same line: copy that carries no take-away content — greetings, empty states, completion notices — gives humor nothing to compete with, and the cost approaches zero; the test is "does this sentence contain content the user must carry away." The second opening is structural: the competition lives within one sentence, so splitting the information sentence from a separate easter-egg sentence and placing the gag after the message ends the contest for a single encoding pass. Third, tone is not a joke: light wording adds almost no decoding burden, and the cost grows continuously with the completeness of the gag, a rising curve from breezy tone to full setup-plus-punchline. Finally, the inconsistency in the advertising literature is itself an evidence boundary — relevant humor (the joke bound to the selling point) has reports of positive effects; "net cost is negative" should be held as the conservative default for critical-information contexts, not as a universal law.

Applying it

  • Maintain a list of critical-information copy: safety warnings, error-recovery steps, permission and privacy explanations, payment and deletion confirmations, numeric and dosage hints — no joke structure in these positions by default.
  • Separation principle: information sentence and easter-egg sentence are physically distinct, information first and gag after; the gag must be deletable as a whole sentence without harming the information, and one sentence never carries both a punchline and must-remember content.
  • Keep the light tone; keep full jokes (setup plus punchline) out of critical-information copy.
  • To validate: have someone who has never read the copy read it once and later recount the key parameters and steps; omissions clustering on the joke-occupied sentences indicate intrusion. Optionally compare recall of key points between a humorous and a plain version; if the plain version is significantly higher, keep it plain.

Related

  • Same group: P1.12.1 Humor may target only the system, never the user · P1.12.2 Waiting scenes carry humor better than error scenes · P1.12.4 Humor that cannot be localized turns into noise after translation
  • Nearby: P1.06.1 Jokes do not belong in error and loss scenarios · T2.04 Error messages · T2.07 Permission and privacy copy
  • Search terms: cognitive load · humor and memory · advertising recall · incongruity resolution

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/P1.12.3