Context

The product surface spans scheduling, clinical documentation, imaging operations, and reporting. Teams move fast, but every change touches regulated workflows—so discovery, prototyping, and rollout had to stay tightly coupled with engineering and clinical stakeholders.

What I focused on

• End-to-end flows from triage through handoff, reducing ambiguity in high-stakes tasks
• Component patterns and documentation so new surfaces stayed consistent as the org grew
• Close iteration with engineering on states, errors, and performance in real clinics

Outcomes

Shorter time-to-confidence for new hires in core tools, fewer support escalations around “what happens next” in multi-step workflows, and a shared language between design, product, and clinical ops for prioritization.

Ayogo · Engagement systems

Reward loops, progress visualization, and content strategy for programs where motivation—not just usability—drove retention. Work included prototyping flows with clinical partners and tightening the feedback between design and measurement.

Plantiga · B2B monitoring

Dashboards and device-adjacent software for coaches and clinicians. Emphasis on legibility of time-series data, alerting that respects cognitive load, and flows that worked on the road as well as at a desk.

Agency & other collaborators

Shorter engagements with WestJet, Genentech, BC Hydro, and others: rapid discovery, design systems contributions, and shipping alongside client engineering teams.

Discovery & framing

I start by mapping who is affected, what “good” looks like for them, and which constraints are immovable (regulatory, technical, operational). That becomes a short written frame the team can react to—before pixels.

Design & validation

Low-fidelity flows for alignment; higher-fidelity prototypes when we need to test comprehension, task time, or edge cases. I prefer testing with real workflows and realistic data over polished decks.

Launch & learning

Instrumentation where it helps, design QA on production builds, and a clear loop for post-launch fixes. The goal is a system that gets better after release—not only at mockup stage.