The fastest way to reduce hesitation is not more guidance — it’s a predictable interaction that fits the user’s mental model.
Concept of the week - Familiarity Reduces Verification Burden
Calm interfaces borrow what people have already learned elsewhere—especially when they’re busy, tired, or working in a critical context.
When we designed a new transport patient monitor, we wanted a modern touch UI: swipe, scroll, and gesture-based navigation. The concern was predictable: “What if nurses can’t use it?” The proposed safety net was a fallback setting for the old paging UI. The fear of removing the legacy mode was valid. But that “option” would have exported work into the product and the organization: extra configuration paths, more verification combinations, more training permutations, and a bigger support surface.
We opted for a calm approach: we checked for fail-safe familiarity rather than adding a second UI. We interviewed nurses, asked about smartphone and tablet use, and tested early gesture prototypes. The result was reassuringly ordinary: In our interview sample, 95% of nurses use smartphones or tablets daily and navigated the gesture prototypes fluently—scrolling, swiping, and locating functions without coaching.
That evidence gave us the confidence to commit to a single interaction model, which we validated through iterative testing as the design matured.
Jakob’s Law says people feel more at ease when interfaces behave like the tools they already use every day. Under pressure, unfamiliar patterns show up as hesitation, manual double-checks, and “just to be safe” workarounds.
Microsoft kept “Windows Classic” alongside Windows XP—sometimes for real constraints (performance, older hardware)—but it’s still a cautionary tale: parallel modes tend to linger and multiply maintenance, so prove familiarity early and ship a single behavioral path.
We default to established conventions and only deviate when the benefit justifies the added verification and training burden.
One thing to remember: every fallback UI multiplies state, test cases, training paths, and “which mode am I in?” support calls.
Implementation note: release behind a feature flag, log gesture success/abort rates, and define a removal date for any transitional affordance so it doesn’t become “permanent by accident.”
Asset
Familiarity Evidence Sheet (one page)
Use this checklist before anyone suggests a “classic mode.”
What pattern are we reusing? (e.g., vertical scroll list, swipe between tabs)
Where is it learned already? (consumer apps/devices your users actually use)
What’s different in this context? (gloves, time pressure, lighting, motion, interruptions)
Fast proof: 5–8 interviews + 15-min clickable prototype task
Decision: commit to one UI / transitional onboarding / redesign the pattern (not a parallel UI)
Light wisdom & reflection
“The word ‘intuitive,’ in my opinion, is the most harmful and misleading word in User Interface Design.”
If you’re calling something “intuitive,” ask: Is it truly intuitive—or just familiar to the people we happened to test?
Mindful practice
Think of one place you keep a ‘backup way’ of doing something (work or life) and write down the answers to the following questions:
What anxiety is that fallback soothing?
What additional checks or switches does it require?
What single commitment would remove the need for it?
Best,
Andreas Walden
Share this with someone designing for clarity.