Molly guard in reverse – Unsung

Unsung
Software craft and qualityPosts by Marcin Wichary

Molly guard in reverse
Feb 12, 2026

Old-school computing has a term “molly guard”: it’s the little plastic safety cover you have to move out of the way before you press some button of significance.

Anecdotally, this is named after Molly, an engineer’s daughter who was invited to a datacenter and promptly pressed a big red button, as one would.
Then she did it again later the same day.

You might recognize molly guards from any aerial combat movie you ever watched:

And some vestigial forms of molly guards exist everywhere in civilian hardware, too: from recessed buttons, through plastic ridges around keys, to something like a SIM card ejection hole.

Of course, molly guards happen in software, too: from the cheapest “are you sure?” dialogs (which sometimes move buttons around or disable keyboard activation to slow you down), through extra modifier keys (in Ctrl+Alt+Del, the Ctrl and Alt keys are the guards), to more elaborate interactions that introduce friction in places where it’s needed:

But it’s also worth thinking of reverse molly guards: buttons that will press themselves if you don’t do anything after a while.
I see them sometimes, and always consider them very thoughtful. This is the first example that comes to my mind:

Here’s what became a standard mobile pattern:

These feel important to remember, particularly if your computer is about to embark on a long process to do something complex – like an OS update or a long render.
There is no worse feeling than waking up, walking up to the machine that was supposed to work through the night, and seeing it did absolutely nothing, stupidly waiting for hours for a response to a question that didn’t even matter.
It’s good to think about designing and signposting those flows so people know when they can walk away with confidence, and I sometimes think a reverse molly guard could serve an important purpose: in a well-designed flow, once you see it, you know things will now proceed to completion.

← “Problem solved, right? Well, not exactly.” / Home / How to make sure a designer never files a bug again →

© Marcin Wichary / Mastodon / Bluesky / Email
Subscribe via
RSS feed or

The article, penned by Marcin Wichary, explores the concept of “reverse molly guards” within the realm of software design, drawing an analogy from a familiar physical design element—the “molly guard” found on older computing devices. The molly guard, originally named after an engineer’s daughter who inadvertently triggered a critical function, represents a deliberate safety measure intended to prevent accidental activation of sensitive controls. Wichary observes that these guards, once prevalent in hardware like aerial combat simulations and modern consumer devices (including recessed buttons, SIM card ejection holes, and similar physical obstacles), have migrated to software. These software implementations manifest as preventative measures, such as intrusive “are you sure?” dialogs and the strategic use of modifier keys like Ctrl+Alt+Del, designed to slow down user interaction and impede accidental activation.

However, Wichary introduces the concept of “reverse molly guards,” which are distinct from traditional safeguards. Instead of actively preventing action, reverse molly guards trigger automatically after a period of inactivity. A prime example is the standard mobile pattern Wichary cites, which initiates an action upon extended dormancy. This particular design focuses on complex processes like operating system updates or lengthy rendering tasks, recognizing the frustration associated with systems appearing to stall without obvious indication of progress. The author argues for a deliberate design approach that provides users with clear signposting, enabling them to confidently withdraw from prolonged processes when completion is assured.

The core of Wichary’s argument centers on the importance of a well-defined user flow, particularly during lengthy operations. He emphasizes the negative user experience of encountering a system that silently awaits a response, rendering the user’s time and effort unproductive. This highlights the need for design choices to provide users with reassurance regarding the completion of tasks. The potential utility of reverse molly guards lies in their capacity to instill confidence by signaling a process's imminent conclusion once initiated, thereby eliminating the ambiguity that can lead to user frustration and a perception of system failure. The author suggests that such intuitive design elements contribute to a more positive and efficient user experience, particularly when dealing with potentially time-consuming processes.