The user is drunk

"The User Is Drunk" is a design principle and mental model that encourages building interfaces so simple and forgiving that someone impaired could use them successfully. The principle gained popularity when developer Richard Littauer offered a service to test websites while literally intoxicated, but the underlying insight is serious: users rarely give your product their full attention. Design as if they're distracted, confused, or in a hurry - because they usually are.

Why it matters

Product teams often design and test their products under ideal conditions: focused attention, familiarity with the product, knowledge of how things work. Real users encounter products under very different conditions. They're multitasking, interrupted, stressed, unfamiliar with conventions, or simply not paying close attention.

The gap between these contexts explains why products that seem perfectly clear to their creators confuse actual users. The "drunk user" mental model reminds teams to design for realistic conditions, not ideal ones. If a drunk person could figure it out, a distracted or hurrying user probably can too.

The principle in practice

Designing for the drunk user means:

Obvious navigation. Users shouldn't need to think about where to click next. Primary actions should be visually prominent. Navigation should be predictable and consistent.

Forgiving interactions. Mistakes should be easy to recover from. Undo options, confirmation dialogs for destructive actions, and clear error messages that explain what went wrong.

Minimal cognitive load. Reduce the amount users need to remember or figure out. Show information rather than requiring recall. Use recognition over memory.

Clear language. Avoid jargon, cleverness, and ambiguity. Say exactly what you mean in words users understand. Labels should describe what happens when you click.

Sensible defaults. Pre-fill forms where possible. Choose default options that work for most users. Don't require decisions when good defaults exist.

Real-world user states

While the "drunk" metaphor is memorable, real users face many impairments:

Distraction. Users check your product while in meetings, waiting in line, or watching TV. You have partial attention at best.

Stress. Some products get used during stressful moments - finding urgent information, handling problems, making time-sensitive decisions.

Unfamiliarity. New users don't know your patterns and conventions. What's obvious to daily users is mysterious to newcomers.

Physical impairment. Small screens, bright sunlight, accessibility needs, and other environmental factors affect how users interact.

Time pressure. Users often want to complete tasks quickly. They don't have time to learn your interface.

Designing for impaired users serves everyone better, including your best users on their worst days.

Examples of drunk-friendly design

Good form design. Single-column layouts, clear labels, inline validation, helpful error messages, and progress indicators. Users can complete forms even when not fully focused.

Clear onboarding. Step-by-step guidance with obvious next actions. Users don't need to figure out where to start or what the product does.

Obvious calls to action. Primary buttons that stand out visually. Users don't need to hunt for how to proceed.

Contextual help. Information appears where users need it, not buried in documentation. Tooltips, inline explanations, and smart defaults reduce the need to search.

Undo and recovery. Accidentally deleted something? Undo immediately available. Submitted the wrong data? Easy path to correct it. Made a mistake? Clear explanation of what happened and how to fix it.

Testing for drunk-friendly design

Several approaches help evaluate whether designs meet this bar:

Five-second tests. Show users a design for five seconds, then ask what they remember. If they can't identify the main purpose and action, the design isn't clear enough.

Hallway testing. Grab random colleagues unfamiliar with the project and ask them to complete tasks. Their confusion reveals assumptions your team has internalized.

Think-aloud testing. Watch users attempt tasks while narrating their thoughts. "I'm not sure where to click..." signals design problems.

Stress testing. Test under difficult conditions: small screens, poor lighting, interruptions, time pressure. If the design works under stress, it works.

Actual impairment testing. Littauer's original service tested while literally intoxicated. While extreme, this approach reveals problems that normal testing misses.

Common design failures

Patterns that fail the drunk user test:

Mystery meat navigation. Icons without labels, clever names that don't explain function, navigation that requires learning.

Walls of text. Long explanations that users won't read. If it needs that much explanation, simplify the design.

Hidden actions. Important functions buried in menus, revealed only on hover, or requiring specific knowledge to access.

Technical language. Jargon, acronyms, and terminology that assumes domain knowledge. Users shouldn't need a glossary.

Unforgiving interactions. Permanent actions without confirmation, no undo, unclear error states, and confusing recovery paths.

Visual clutter. Too many options, inconsistent styling, and competing calls to action that make decision-making harder.

The accessibility connection

Drunk-user design overlaps significantly with accessibility. Many accessibility principles - clear navigation, readable text, forgiving interactions, keyboard support - also help impaired users of all kinds.

Designing for accessibility often improves usability for everyone:

The disability community's insight that "disability is a mismatch between ability and environment" applies broadly. Your design choices determine whether users' temporary impairments become barriers.

Balancing simplicity and power

The drunk user principle sometimes tensions with power user needs. The solution isn't dumbing everything down but layering complexity:

Progressive disclosure. Simple surfaces reveal complexity when needed. Basic options visible; advanced options available but not in the way.

Sensible defaults with options. Works out of the box for most users, configurable for those with specific needs.

Multiple paths. Simple guided flows for casual users, keyboard shortcuts and bulk actions for power users.

Contextual complexity. Show advanced features when users demonstrate they need them, not on first contact.

The product manager's role

Product managers influence drunk-friendly design through:

User understanding. Research that reveals the actual conditions under which users encounter your product. Not just who they are but what state they're in.

Prioritization. Insisting on simplicity even when adding features is tempting. Protecting users from complexity that serves edge cases.

Quality bar. Setting expectations that interfaces must work for impaired users, not just ideal ones.

Testing advocacy. Ensuring usability testing happens under realistic conditions, not just controlled lab settings.

The modern context

Modern digital products face increasing competition for attention. Users have endless alternatives and little patience for confusion. Products that require effort to understand lose to products that work effortlessly.

Mobile usage amplifies this dynamic. Small screens, one-handed use, and constant interruption make drunk-user design essential rather than aspirational.

Tools like Klero help teams understand where users struggle by capturing feedback about confusing experiences. When customers report that something was hard to figure out, that's a signal that the design failed the drunk user test. Connecting this feedback to product decisions helps prioritize simplicity where it matters most.