top of page

We had no system.
So we built one.

A pharma marketing operations platform designed from scratch replacing scattered emails, Jira tickets, and lost project details with a single source of truth.

UX Designer & Researcher
Built 0 - 1

Note: Due to NDA constraints, I’ve modified majority of details.

image.png

The Context

A project manager ran every marketing project through scattered emails, Teams threads, and Jira tickets. Nothing was structured. Nothing was reusable. Every new project started from zero even when 80% of the details already existed somewhere else.

0

The Problem

Four breakdowns.
One root cause.

01

No defined project initiation

Teams created projects ad hoc, with no consistent structure making handoffs slow and error-prone.

03

Zero reusability between projects

Teams created projects ad hoc, with no consistent structure making handoffs slow and error-prone.

02

No visibility into billing

Costs sat in email threads and spreadsheets. No one had a single view of budget status.

04

Tooling was expensive and wrong-fit

Existing tools weren't built for pharma ops. They introduced friction, not focus.

Role & Scope

I led design end-to-end research, interaction design, developers, working directly with the leadership, product owner and engineering.

Research
Designing
Presenting
Prototyping

The Solution

One dashboard. Every project, visible.

Instead of chasing status updates over email, every active project its brand, region, asset type, and status lives in one filterable table. KPI cards surface what needs attention before anyone has to ask.

Personal Portfolio Homepage Design-6_.png

From blank page to
submitted in four steps.

The old version asked for twelve fields at once. The new
flow only asks what's relevant, when it's relevant fields
adapt to the asset type you're creating.

image.png
image.png

Details

Brand & Asset

image.png
image.png

Requirement

Review

image.png
Personal Portfolio Homepage Design-6_.png

Signature Feature

Why repeat what already exists?

Teams asked for the same project details over email, every time. Now duplicating a project takes one click with full visibility into exactly what's being carried over.

Screenshot 2026-06-19 124811.png

What I learned

● Systems compound. Solve the right primitive once, and ten downstream problems disappear with it.

● Done in phases, not all at once, momentum matters more than completeness.

● The brief is rarely the problem. The shape of the brief usually is.

Impact

21%

● increase in duplicate-project usage

39%

● increase in client interaction with the tool

67%

● increase in client interaction with the tool

bottom of page