Skip to content

PATTERN Cited by 1 source

Familiar UI borrowed from adjacent flow

Problem

A product team building a new UX flow needs the user to complete an unfamiliar task — here, share a gate code with a driver they haven't met. New UI + new task = double learning cost: the user is simultaneously learning what to do and how to do it. The failure mode is users abandoning the new flow because the unfamiliarity of the UI compounds the unfamiliarity of the task.

Solution

Make the UI itself familiar by borrowing it from:

  1. A real-world physical interaction the user already knows — something they've done outside the app many times.
  2. An adjacent in-app flow the user has already completed before.

The user then only has to learn the new task; the UI feels already-understood. Learning cost drops to the minimum.

Canonical instance — Lyft gate-instruction sharing

Per the 2026-04-23 Lyft write-up (sources/2026-04-23-lyft-smarter-pickup-experience-for-gated-communities):

"Our Design team drew inspiration from the intercom panels riders use every day: a familiar numpad for gate codes, and a short list of plain-language options for everything else."

And:

"We also designed the new UI to feel familiar, borrowing patterns from our existing Venues pickup flow so our riders wouldn't have to learn something from scratch."

Lyft uses both forms of familiarity:

  1. Physical borrow — the numpad mirrors the apartment intercom the rider has used dozens of times to buzz in visitors.
  2. In-app borrow — the overall "gates mode" pickup flow reuses the structure of the pre-existing Venues pickup flow.

Why this shape works

  • Zero explanation needed. A rider sees the numpad and immediately knows to enter digits. No tooltip, no onboarding.
  • Reduces anxiety on a sensitive task. Sharing a gate code is a privacy-adjacent action; an unfamiliar-looking input heightens anxiety. A familiar numpad normalises it.
  • Faster task completion → less abandonment. Especially important right after ride request, when riders are expecting imminent pickup.

Supporting discipline — content tuning

Lyft explicitly pairs the visual familiarity with content tuning by a Content team:

"Our Content team worked to make each option feel conversational and specific enough to be useful, without being so wordy that riders would skip past them."

The combination matters: a familiar UI with wrong copy still feels alien.

When not to use

  • When no familiar analog exists — a genuinely novel task may require a genuinely new UI, and borrowing from something tangentially similar misleads more than it helps.
  • When the physical analog is misleading — e.g. borrowing a dial-pad UI for an entirely non-numeric input is actively confusing.
Last updated · 550 distilled / 1,221 read