UX Director | Strategy & Experience Design | Healthcare · Pharma · HealthTech | Designing experiences at scale

Most UX problems in
regulated healthcare are
structural, not visual.

↓ 20%
Patient drop-off reduction via UX audit & experience redesign · Abbott FreeStyle Libre
15+
Years leading UX strategy across healthcare, pharma & regulated enterprise

Selected work across healthcare, pharma, and regulated enterprise — each starting with a diagnostic question, not a design assumption.

Capabilities

Define · Research · Deliver · Scale

From upstream diagnosis through execution — the full arc of UX strategy in regulated environments.

01
Define
Shape the UX vision and secure organizational buy-in. Experience assessment, compliance gap analysis, and the upstream diagnosis that determines whether the brief is asking the right question.
02
Research
AI-augmented competitive intelligence, heuristic audits, and cross-market pattern analysis — surfacing structural failures and white space before design work begins.
03
Deliver
Journey architecture, IA, and experience frameworks from discovery through compliance and stakeholder review — exec-ready, without a separate translation layer.
04
Scale
Global IA frameworks, cross-market deployment, and the research infrastructure that compounds in value across projects — built to run without rebuilding from scratch each time.
Leadership

Leading in partnership —
setting every team up for success.

They know the why, not just the what.

Every decision has a defensible rationale — built into the brief before anyone opens a design tool. When teams understand the structural reasoning behind an architecture decision, they can defend it in stakeholder review without me in the room.

They're comfortable with ambiguity.

Regulated engagements rarely arrive with clean briefs. Strong framing at the start — the right diagnostic question, the right structural model — is what keeps cross-market and multi-stakeholder work from fracturing mid-execution.

They can represent the work without me.

The deliverable isn't just the design — it's the brief that carries it. When audit findings are structured to hold up through executive, medical, and regulatory review, the work advances on its own logic, not on my presence in the room.

They align stakeholders across disciplines.

In regulated environments, UX decisions that can't survive medical, regulatory, and legal review simultaneously don't ship. I build teams that understand this isn't a compliance problem — it's a design problem. The rationale gets baked in from the start.

Writing

What I'm thinking about.

Complexity and Constraint
LinkedIn Article · UX Strategy & CX Design
Why the Hardest CX Problems Live at the Intersection of Complexity and Constraint

"Complexity and constraint are the brief, not the obstacle."

Organizations that treat complexity as a content problem and constraint as a legal problem produce the same failure — every time. A structural reframe for getting both right from the start.

Read ↗
The Design System Has Left the Building
LinkedIn Article · Experience Design
The Design System Has Left the Building

"Consistency without judgment is institutional distance at scale."

AI is accelerating the disconnection between the component and the patient. An argument for bringing experience judgment back into the room alongside the system.

Read ↗
The Audit Is the Strategy
LinkedIn Article · CI & UX Strategy
The Audit Is the Strategy: How AI-Driven Competitive Intelligence Has Taken Over UX and CX

"The audit isn't informing the strategy anymore. It's becoming it."

AI has made competitive intelligence a live strategic layer — running continuously, surfacing patterns at scale, and changing when in the process key decisions get made.

Read ↗
The Interface Is Not the Problem
LinkedIn Article · AI & UX Strategy
The Interface Is Not the Problem

"The interface is usually the last place the problem lives."

When a healthcare experience fails, the instinct is to redesign the interface. A case for upstream diagnosis — and what changes when you treat the interface as a symptom, not the cause.

Read ↗