Publicly displayed failure increases reluctance to try again

What it is

A missed recognition, a wrong PIN, insufficient balance—if the screen broadcasts it with full-bleed red type, a harsh sound, or an enlarged face or ticket across the glass, the cost flips from “this might not work” to “it already failed in public.” Public failure display increases retry aversion is about how visible and theatrical the error is, not about whether failure occurs. The next attempt on a public screen is voluntary; people can leave. Turning failure into subtitles for bystanders makes leaving beat trying once more. The claim does not explain why acting in public is costly in the first place. It tracks how the funnel drops people at the “already reached” stage once failure has been amplified.

Why it happens

On a private device, failure is usually a brief note to the operator. On a public board, the same note has every person who can see the glass as audience. Full screen, high contrast, long dwell, and sound encode “this did not work” as an event, and bystanders look up. The operator expects a second failure to play again, so they leave after the first, including recoverable misses (hand offset, scan too far). Recognition failures cut deeper: there is no way to prove to bystanders that “the machine missed” rather than “I cannot do this.” Keep failure local, short, silent, and unnamed, and bystanders may not even read it as failure, while the operator can still correct and go again. If success is also a full-screen firework, success and failure draw a crowd equally; relative humiliation may not fall, but the chance to retry quietly is still destroyed.

Studying it

Build the same failure as a local light cue versus a full-screen or audible broadcast, and compare post-failure retry and leave rates on a site with bystanders. In the field, code duration of the failure frame, presence of sound, whether bystanders stop because of it, and the operator's next move (immediate retry / withdraw / hand off to a companion).

Independent variables: area of the failure feedback, duration, sound, whether identifiable personal data or a ticket face is shown. Dependent variables: retry within five seconds, leave rate, bystander stops caused by the failure, rated “my failure was seen.”

Lab participants are asked to retry, so aversion barely appears. Do not bundle a low recognition rate with “failure is broadcast” into one independent variable—hold failure rate, then change only the display, or you cannot tell shame from an impossible task.

Where it stops holding

Safety alarms, gate refusals, and evacuation have to show failure to everyone nearby; this claim yields. Games and performative pieces treat failure as audience content, and the role may absorb the sting. With nobody present, a broadcast has no social audience and only the operator's own affect remains. If the failure already happened on a phone, a public “please look at your phone” does not cut the same way—the audience cannot see the phone. Payment or identity failures that must be public (“this card is invalid” to a whole queue) need an immediate next step, or aversion turns into conflict. A child failing beside a parent has an in-group audience, not the same grade as being watched by strangers.

Applying it

• Keep failure in a small patch in front of the operator: short copy, silent or very low sound, gone within two seconds; no full-screen red and sting.
• Do not show a name, ID, ticket face, or photo on the failure state; say “not read, please move closer,” not “you failed.”
• After failure, offer an actionable next move at once (scan again, switch to touch, try another card) and make sure retry does not play a louder animation.
• Verify on a live site: retry within five seconds versus leaving after failure; change full-screen errors to local ones and compare the same traffic—retry should rise, bystander stops caused by the error should fall.

Related

• Within the group: K7.08.1 Smaller first-move amplitude lowers spectator pressure · K7.08.2 Simultaneous entry points spread the pressure of being watched alone · K7.08.4 Private personal-device input moves sensitive actions out of public view
• Adjacent: K7.03 Social Embarrassment · K7.04 Simultaneous Multi-user Use
• Search terms: public error display · retry aversion · failure visibility