Delight intensity must match the event's actual weight

What it is

The intensity of a celebration, reward, or excited feedback must stay proportionate to what the triggering event actually weighs for the user: heavier events earn larger celebrations, lighter events quieter ones. The case for this proportionality principle sits not on the "is it enthusiastic enough" side but on the information side — the scale of a celebration is the product broadcasting what it thinks matters, and users back-read its value judgments from the intensity.

Why it happens

Users do not only receive a celebration; they decode it. A celebration is a cost the product pays — time, attention, screen area — and where and how big it is spent is back-read as a value signal. A full-screen animation for a trivial action reads as one of two bad things: flippancy (this product cannot tell what matters) or flattery (it is courting me, not respecting me). A genuinely major moment met with a dismissive one-liner reads as indifference (this product does not think my event matters). Both misreadings fail at the same point — the feeling that "it does not understand what this event means to me" — and much of emotional design's payoff comes exactly from being understood, not from the physical force of the stimulus. The deeper layer is that intensity inflates: users calibrate the product's intensity ceiling from the biggest celebration they have seen, so celebrating a minor event oversize spends the headroom a major event would have needed — by the time the real peak arrives, an equal or even larger celebration can no longer register as one. Intensity is a budget, not a price that can be re-tagged per event.

Where it stops holding

The yardstick must be user-side weight (money involved, irreversibility, a first time, hours invested), not engineering-side event frequency: what is routine for the system may be once-in-a-lifetime for this user. Celebrations also face a propriety constraint independent of proportion — in serious contexts (medical, financial, bereavement) any celebration can read as making light of things, and correct proportion will not rescue it. And proportion is necessary, not sufficient: even a well-matched celebration decays under high-frequency repetition, which the laws of repeated exposure govern separately.

Applying it

• Grade user events into routine (happens on every operation) / milestone (first time, cumulative totals, stage crossings) / major (money, irreversibility, high effort), and fix a celebration budget per grade — routine gets ambient feedback only (sub-second micro-animation), milestone gets one skippable screen-level moment, only major earns a full-screen moment plus a keepable artifact (badge, record, certificate).
• Keep the intensity ladder monotonic: the full-screen celebration appears only at the top grade, preserving unspent intensity headroom for the events that deserve it.
• Base the grading on user-side criteria (money, irreversibility, first-time, time since the last similar event) and audit it against real user event streams before shipping.
• To validate: screenshot-inventory every celebration moment, rank them by visual intensity, and check each against the grading table; then have users rate each one on "does this celebration match what just happened" — low scores clustering on the strong side mark over-celebration, on the weak side, under-celebration.

Related

• Same group: P1.09.2 Surprise is the source of delight and zeros out once predictable · P1.09.3 Emotional peaks need an attributable object · P1.09.4 Recovery after failure is a low-cost peak location
• Nearby: P1.02.2 High-frequency delighters become interference · P1.03.1 Overall evaluation is dominated by peaks and endings
• Search terms: proportionality · costly signaling · celebration budget