Patients think “jawline,” not “dermal filler”

Your menu speaks clinical. Your patients arrive speaking concern. Every translation you make them do is friction — and most clinics make them do all of it.

Your menu speaks clinical. Your patients arrive speaking concern. Every translation you make them do is friction — and most clinics make them do all of it.

Watch a first-time patient talk about why she's considering a medspa. She won't say "neuromodulators" or "biostimulatory filler." She'll say tired eyes, gummy smile, jawline, the lines here. Then she'll open a clinic website and find a menu organized by pharmaceutical category — and she's expected to already know that "tired eyes" maps to three different treatments across two menu sections.

Information architecture is deciding whose language the structure speaks. Concern-first architecture — Tired eyes · Jawline · Skin texture · Prevention — meets the patient where her vocabulary actually is, then teaches her the treatment names on the way. The clinical taxonomy can still exist underneath; it just shouldn't be the front door.

The other half of this lens is honesty about dead ends: pages that end without a next step, orphaned content nothing links to, and the question every architecture must answer on every page — where would a half-decided patient go from here?

What this lens checks: Organization · Categorization · Menu logic · Naming · Content hierarchy · User journeys · Dead ends

Go deeper: the full essay on concern-based navigation.