Why Beacon Health Pivoted From Symptom-First to Journey-First in 10 Weeks

Design · 5 min read

Beacon Health launched with a symptom-first design: users selected symptoms, then received triage paths and content. Early analytics showed high initial engagement but steep drop-offs during the second session, and interviews revealed users didn’t think in isolated symptoms — they thought in goals like “get back to work” or “sleep better.”

Product and design teams ran a rapid discovery sprint, mapping user goals across persona journeys and identifying seven high-value journeys to prototype. The new information architecture grouped content and tasks by outcome (e.g., recovery, management, prevention) and surfaced journey state across sessions so users could pick up where they left off.

The team also adjusted copy and micro-interactions to emphasize progress and milestones instead of symptom checklists, and introduced one-tap “continue journey” CTAs on the home screen. Over ten weeks, retention at 14 days rose 18% and completion of recommended actions increased 32%, validating the journey-first hypothesis.

Beacon’s case shows how aligning product structure with users’ mental models can be faster and cheaper than incremental feature additions, and how outcome-focused design decisions can turn short-term engagements into longitudinal relationships.