02
Eli Lilly · Verzenio

Experience Architecture & Competitive Intelligence

Designing oncology experience architecture to support informed treatment understanding across complex, multi-pathway disease management — backed by competitive landscape analysis.

Experience Design UX Architecture Competitive Intelligence Oncology Breast Cancer FDA · MLR
Eli Lilly · Verzenio · EBC + MBC · FDA MLR
Two patient journeys.
One platform.
Single MLR cycle.
Dual-audience UX · 6 MLR watch items sequenced
Challenge
Problem reframe
UX approach
Decision log
Research → insight
Deliverables
Hindsight
The challenge

Verzenio serves patients across meaningfully different disease stages — early and metastatic breast cancer — each with distinct treatment goals, support needs, and emotional contexts. A single UX model couldn't serve both without creating confusion or clinical risk.

The brief came in anchored to a measurable failure: MBC pages had a high bounce rate. The brand team's ask was framed around their named patient persona — "Pam" — and the specific problem of Pam not being able to find the efficacy data she was looking for. The tabs and anchors weren't informative. The navigation structure made the MBC clinical evidence hard to reach from any entry point. Performance data pointed to the structural problem; the brief asked for a data-driven diagnosis and recommendation, not a redesign.

The experience design gap wasn't informational — it was architectural. Content existed but the UX structure didn't reflect where different patients actually were in their journey. A single undifferentiated model created confusion and clinical risk for EBC patients who didn't yet identify as having a serious disease, and failed MBC patients who needed evidence and context before emotional support.

My role: I led experience design and UX architecture across the full Verzenio DTC ecosystem — a sustained engagement from Q1 2023 through February 2024 handoff covering the full dual-audience site across EBC and MBC indications.

Working across teams

Led agency-side across 13 months — aligning UX, strategy, and account internally before bringing the dual-sequencing architecture to Lilly's clinical, regulatory, and brand teams. Every decision arrived at Lilly with the rationale already made. By handoff, the architecture was documented well enough that both teams could own it independently.

From brief to reframed problem

The brief described a content problem. The real issue was a structural one that content alone couldn't solve.

Client brief

"Redesign the Verzenio DTC platform to better serve both early breast cancer and metastatic breast cancer patients — currently the experience isn't differentiated enough between the two audiences."

Reframed UX problem

The problem isn't insufficient differentiation — it's that both audiences are running through the same UX sequencing model. EBC and MBC patients don't just need different content; they need fundamentally different information architectures. EBC patients need emotion first — validation before evidence. MBC patients are further along their disease journey and need evidence first — clinical credibility before emotional support. Two sequencing models, not one with variations.

This reframe produced the EBC model (Emotion→Evidence→Action) and the MBC model (Evidence→Context→Support) as structurally distinct sequencing architectures served from one platform infrastructure.

Transferable to

Multi-condition health platforms & chronic disease management apps. Designing structurally distinct experience flows for audiences at different disease stages applies to any health platform where user states differ meaningfully — diabetes management, mental health, and chronic condition apps often collapse these differences into one model, creating the same structural failure.

UX approach

Two UX sequencing models were designed: EBC — Emotion→Evidence→Action; MBC — Evidence→Context→Support. I mapped the full patient experience ecosystem across both disease stages, identifying where UX could share infrastructure and where experience design needed to diverge.

Five UX design recommendations per audience across six content areas, with six MLR watch items sequenced for regulatory review alignment. MBC was identified as the source-of-truth UX navigation pattern, with EBC adapting the structural foundation to its distinct emotional sequencing requirements.

Key design decisions
Decision point Alternatives considered What we chose & why
Platform model — one site vs. two experiences
Two separate DTC platforms — one for EBC, one for MBC. Cleanest audience separation.
Single platform with distinct UX sequencing per audience. Two platforms doubled MLR overhead and maintenance cost; bifurcated sequencing was viable within one submission.
EBC sequencing — evidence-first vs. emotion-first
Lead EBC with clinical efficacy data — aligned with regulatory preference for clinical accuracy at the top of the hierarchy.
Emotion-first for EBC. Patients recently diagnosed with early breast cancer often don't identify as seriously ill. Leading with evidence before validating emotional experience created cognitive dissonance.
Side Effects page — linear scroll vs. tab-reveal architecture
Linear scroll: existing layout with all content stacked vertically. Simpler to build, no interaction layer to approve through MLR.
Expect → Plan → Act tab-reveal structure. The existing layout buried the "ACT" content — the immediate 24-hour action plan — below the fold. Patients experiencing diarrhea needed the most urgent clinical action at the first viewport, not after scrolling past two explanatory sections. Tab structure surfaced it without adding page length.
Research → insight → recommendation
Research input
Oncology DTC competitive audit + patient journey literature

Heuristic evaluation of breast cancer DTC platforms — Kisqali and Ibrance named in the brief as primary benchmarks, with broader oncology DTC architecture (including Talzenna) audited for structural patterns. AI-augmented IA analysis. EBC vs. MBC disease-stage emotional differences and treatment decision-making research.

Key insight
All competitors used identical sequencing for both disease stages

Every platform audited applied a single IA across EBC and MBC — efficacy first, then mechanism, then support. No platform accounted for the fundamentally different information needs and emotional contexts between disease stages.

UX recommendation
Two sequencing models derived from disease-stage emotional arc research

EBC: validate the emotional reality of diagnosis before introducing clinical evidence. MBC: lead with clinical credibility — these patients have been through treatment and evaluate support against a high standard.

Transferable to

Multi-condition health platforms & chronic disease management apps. Designing structurally distinct experience flows for audiences at different disease stages applies to any health platform where user states differ meaningfully — diabetes management, mental health, and chronic condition apps often collapse these differences into one model, creating the same structural failure.

Figure 01 · Process DeliverableMLR alignment — dual-audience UX through a single review cycle
Stage Process
01Discovery & Competitive Audit
02UX Strategy & Sequencing Logic
03Content & Claim Architecture
04Regulatory Preparation
05MLR Submission
06Clearance
Key friction
Two patient audiences with opposing information needs shared one platform — emotional orientation vs. clinical evidence hierarchy. Six MLR watch items spanned both content streams, each with distinct claim registers and hard deadlines.
Outcome
EBC & MBC DTC platform cleared MLR in a single review cycle. Dual-audience architecture approved without structural revision; CB55 deadline met across English and Spanish.
1
MLR review cycle
2
Patient audiences · one architecture
6
MLR watch items sequenced
6
Process stages

MLR alignment process map — six-stage process showing how a dual-audience UX architecture (EBC and MBC) was brought through a single MLR review cycle. Specific stakeholder roles not disclosed per NDA; process structure illustrative of methodology.

This process map shortened internal alignment time — teams entered MLR review with agreed sequencing logic, not competing interpretations, enabling the single-cycle clearance.

Figure 02 · UX Recommendations DeliverablePage architecture & navigation optimization
Area Recommendation Priority
Side Effects Three-tab reveal (Expect → Plan → Act) replacing a three-block linear scroll — Act content was buried 3–4 scrolls deep. Critical
Patient Stories Nav Elevated to primary navigation between Common Questions and Savings & Support — was 3 clicks deep, invisible to most users. Critical
Savings & Support Two-column layout above fold; full-width hero with copy overlay; mobile jump-link navigation. High
Header Optimization Full-width image with copy/CTA overlay; reduced module spacing; in-page jump links as alternate navigation. High
Side effects — before / after
3–4 scrolls to reach action content → all three stages visible within first viewport
Patient stories — before / after
3 clicks deep via indication dropdown → 1 click from any page
4
Optimization areas
2
Critical priority fixes
1
MLR review cycle target

UX optimization recommendations — four page-level UX improvements delivered as a client-facing strategy document. Each recommendation presented as before/after schematic with UX rationale. Specific brand assets not disclosed per NDA; structure and methodology illustrative.

Each before/after schematic was built to survive clinical and legal review without verbal explanation — the UX rationale was embedded in the artifact itself.

Figure 03 · UX Wireframe Comp
Side Effects Page — Tab Architecture Wireframe Comp

Side Effects page tab architecture — mid-fidelity wireframe comp showing the Expect → Plan → Act tab reveal structure across three states. Left: existing linear scroll layout with action content below fold. Centre: Expect tab active with annotation callouts. Right: Act tab active showing the immediate 24-hour action content surfaced within first viewport. Accordion format for side effects by treatment type shown in lower right. Client review deliverable prior to full asset development.

The tab architecture surfaced the 24-hour action plan at first viewport — resolving the most urgent patient need without adding page length or triggering a new MLR line item.

Figure 04 · UX Wireframe Comp
MBC Patient Stories — Navigation Restructure Wireframe

MBC Patient Stories navigation restructure — four-state wireframe showing the existing click path (3 levels deep through indication dropdown → About → Patient Stories) against the proposed primary navigation placement. Blue connector arrows trace the existing buried path. Proposed structure places Patient Stories between Common Questions and Savings & Support — one click from any page, reflecting the patient decision arc from clinical questions to peer validation to support enrollment.

Patient Stories moved from three clicks deep to one click from any page — the structural change that addressed the MBC bounce rate without requiring a content rewrite.

Figure 05 · DeliverableUX alignment — early & metastatic breast cancer
EBC
Build confidence in a newly diagnosed patientPrimary need is reassurance and emotional validation before clinical proof. The site lacked a patient stories page; the savings journey was buried. UX priority: Testimonials → Efficacy → Savings.
MBC
Resolve a high-bounce, data-hungry experiencePatients arrive with specific clinical questions and high intent to find efficacy data — non-descriptive tab/anchor structure was the barrier, not the data itself. UX priority: efficacy first.
Core tension
One site. Two opposing needs. EBC and MBC patients arrive at the same domain with fundamentally different readiness states — requiring distinct content hierarchies within a shared navigation structure.
EBC sequencing logic
Emotion → Evidence → Action
MBC sequencing logic
Evidence → Context → Support
2
Content hierarchies · one architecture
5
Net-new UX recs per audience
6
MLR watch items sequenced
Q3
2023 go-live with CB55 deadline

UX alignment framework — the primary UX strategy tool used to align clinical messaging, experience design priorities, and sequencing logic across two distinct patient audiences within a single DTC web experience.

This framework cleared both EBC and MBC architectures in a single MLR cycle — the sequencing logic was embedded in the document, not explained separately in the submission.

Figure 06 · DeliverableAudit scorecard — recommendations by content area
Content area Pri. EBC decision MBC decision MLR
Efficacy & Clinical Data P1 Secondary — supports emotional narrative already established by testimonials. Primary driver — full navigation restructure required. MLR watch
Patient Testimonials P1 Net-new page required — StoryLab testimonials under EBC dropdown. 6 existing videos moved from hidden anchor to dedicated dropdown. Shared
Savings, Support & VCC P1 Two-column layout essential — new patient must understand benefit immediately. Ongoing support messaging prominent — longer treatment horizon. MLR watch
Compliance & Regulatory P2 Mandatory — Spanish translated, all video transcripts updated. Mandatory — hard deadline Aug 31, 2023 blocks other updates. Aug 31 hard
UX & Navigation P2 EBC mirrors MBC structure — patients with both indications navigate equivalently. MBC is the source-of-truth pattern — reduces cross-indication confusion. Shared

Audit scorecard — five UX recommendations sequenced across six content areas, weighted independently for EBC and MBC audiences, with MLR watch status and deadline flags carried at the row level for regulatory review alignment.

Mobile-first review of this same structure surfaced labeling and hero-visibility failures invisible on desktop — directly informing the decision to use MBC as the source-of-truth navigation pattern.

Figure 07 · MLR-approved artifact
Produced Site Experience Design

MLR submission artifacts — fully produced Verzenio DTC platform delivered following MLR review and approval across both EBC and MBC indications. Visual hierarchy and CTA design carry the audience distinction at the page level, while photography direction and color tone shift between the two patient journeys — quieter, more grounded imagery for EBC; more clinical confidence in tone for MBC — within a single shared brand system.

Final MLR-approved platform reflecting both sequencing models in production — EBC and MBC distinguished by information hierarchy, CTA design, and tonal art direction working together, not any one lever alone.

Role
Experience design and UX architecture lead
Deliverables
Full-site UX audit, competitive analysis (Kisqali, Ibrance, broader oncology DTC), MLR alignment process map, UX recommendations, wireframe comps, UX alignment framework, mobile audit, MLR-approved DTC site (EBC + MBC, English + Spanish)
Regulatory context
FDA · MLR · Medical, Regulatory, Legal, Privacy SME review
Engagement
Q1 2023 — February 2024 · Pharmaceuticals · Oncology
If I ran this again

The dual-sequencing architecture was well-supported by the evidence. The one thing I'd shift: build the stakeholder case for structural divergence from the competitive audit outputs — before entering the design phase. When brand, clinical, and MLR teams can see that every competitor is running a single undifferentiated model, the argument for two sequencing architectures lands faster. I'd also bring more MBC patient voice into the evidence validation earlier; the disease-stage literature was strong, but lived experience data would have strengthened the MLR submission case for the Evidence→Context→Support sequence.