Gilead
Canadian Pharmaceutical Website
Designing a More Human Experience for Biktarvy & Descovy
I co-designed one experience that skins cleanly for Biktarvy and Descovy without rebuilding. I led the rules, components, and handoff so the same flow adapts to each brand with minimal dev effort. The old tool felt sterile; this version feels more human while being compliant with prescription advertising laws.
Services
UI/UX Design Creative Direction Mobile App Design
tech
Figma Figjam Zeplin
Timeline
8 weeks
Team
Me & Carlos TLC Gilead
Problem
The legacy page was a flat list. It asked people to click boxes but never felt like it was talking to them. Copy and visuals were tightly restricted by Canadian prescription advertising rules, so the page drifted into sterile and forgettable. Meanwhile, the brand team needed an experience that could align with the renewed direction while avoiding duplicating development across Biktarvy and Descovy.
Solution
We reframed the tool as a short conversation written from the user’s point of view. New to treatment and On treatment each see prompts that match their reality. The answers turn into a doctor-discussion guide you can save, send, or set as a reminder. Under the hood, it is one lean mobile responsive design system so the devs only needed to implement it once, then edit colors and copy to align with each brand.
Impact
A conversation, not a checklist
We rebuilt the tool as a short questionnaire that speaks in the user’s voice and keeps only what matters now. The pace is light, progress is clear, and you can skip straight to the resource and take pre made doctor prompts with you. The old page felt clinical and disconnected. We turned it into a modular tool Gilead can update, so people leave with clear questions for their doctor and feel confident starting the conversation about treatment.
One Build, Two Brands
We were hired for Biktarvy and saw Descovy was next, so I shaped one system that could wear both voices without changing structure. Tokens drive color, type, spacing, and states, while approved copy and imagery swap per brand. We shipped Biktarvy first, then delivered a second Zeplin spec for Descovy with token swaps and sequence notes. Engineering focused on the new questionnaire logic instead of rebuilding layouts, which gave speed, consistency, and a reusable foundation.
Build Day One, Leave With A Plan
I package specs so devs can start coding and users get something useful. In Zeplin I delivered end to end flows with token maps and clear mobile and desktop shifts, while TLC edited copy in both English and French while legal approved final language. The same system turns answers into custom questions for a doctor. Save a PDF, set a reminder, or both. People walk in more confident about what to ask and why.
My Process
Finished Product
What I learned
Start scrappy in FigJam to get legal, product, and dev aligned fast.
Design with tokens and small components so one build can wear many brands.
Focus on the user's perspective and make it as accessible as possible.
Results
We replaced a cold checklist with a short conversation people actually finish. I led the system rules, tokens, components, accessibility, and the dual Zeplin specs so one build could wear two brands without forks. We shipped Biktarvy first, then delivered Descovy from the same structure. Editors swap approved copy and assets while layouts stay stable. The flow now ends in real action.
Next steps
No further work was scoped.