Migraine affects 1 billion people worldwide, but existing treatments often fail to address the daily challenges patients face.
As one of the founding designers, I took initiative on hypothesis-driven research and end-to-end design for core features, working alongside our Design Lead, Vanessa Jimenez.
Together we collaborated across clinical and engineering teams to create the first FDA-authorized digital therapeutic for migraine.
Over 39 million Americans affected by migraine. Many of them experienced inadequate relief or side effects from existing migraine medications.
People are looking for options, but there's a lack of non-pharmaceutical treatments available on the market.
Existing migraine apps on the market mostly focused on data tracking instead of solving actual pain points.
Great opportunities lie in evidence-based solutions like CT-132. Our treatment framework is designed by clinical scientists to deliver real efficacy with validated interventions and therapies.
We had to build the product while content, requirements, and timelines were constantly changing.
Instead of waiting for perfect requirements, we worked in parallelβstarting design while defining what to build.
The roadmap you thought would be
The reality
Migraine sufferers managed complex symptoms, and the app shouldn't add more burden to them.
That's why we gave patients small doses of treatment daily, not overwhelming sessions.
Visualizing the daily engagement flow with a patient-centered approach. Allowed teams to dive into potential scenarios and align on the experience.
While waiting for finalized therapeutic content, we proactively designed modular interface templates based on anticipated content patterns.
This kept engineering moving and gave us flexible building blocks to quickly structure lessons once clinical teams delivered the materials.
I designed and documented UI layout and flows so developers could start building.
I worked closely with teams throughout content creation, reviewing proposed materials and ensuring they fit seamlessly within our established UX framework and lesson structure.
I worked with Clinical Science and Content to create a lo-fi prototype to test the content design draft in an early stage clinical learning study.
As the project progressed, we realized that formal UX research wasn't happening, because of the following reasons:
We need to develop the MVP version for the imminent clinical trial.
Regulatory constraints forbidden us from testing efficacious treatment elements with patients.
We can't bear the risk of revealing the app content to public before the trial.
While features and content were locked in, we needed to discover what type of app experience would resonate with migraine patients.
We created three concepts that balanced visual style, tone, and narrative differently to test what would feel supportive vs. overwhelming:
β’ There are many ways to achieve great design. Be adaptive. Choose the design approach that can provide the most actionable insights or data under the constraints.
β’ Design is about communication. Designers should help the team connect the dots and be more effective.
β’ Be comfortable with managing unknowns and constant reprioritization, especially when things are moving in parallel.