Noteworth

Building Noteworth from the ground up.

Year2016 - 2022
RoleDirector of Product Design
TypeFull-time
Skills
Product Design Design Systems Design Leadership Team Building

I joined Noteworth as its first designer when the product existed only as a pitch deck. Over the next several years, I shipped 25+ features, built the design system that scaled the product to enterprise health systems, and grew a design organization from a team of one to a multi-million-dollar ARR business unit.

The Journey

Noteworth journey: Phase 01 Founding and MVP, Phase 02 Growth and Feature Buildout, Phase 03 Enterprise and Org Scale

Spotlight 01

Building the system that made consistency possible.

As Noteworth scaled from MVP to enterprise, the product was growing faster than the design could hold together - components diverged across mobile and web, engineers were resolving UI decisions that should have been settled upstream, and every new feature added debt. I built a comprehensive design system covering both platforms to solve that: not just for visual consistency, but to give engineering a reliable foundation to move faster, and the design team a shared language that didn't depend on any one person holding it in their head.

Noteworth design system component documentation

Good component documentation answers the question before a developer has to ask it. Status, behavior, and edge cases in one place.

"Not only are their products aiding our patients, the process improvements have allowed our staff to see more patients in the same number of hours."

Chief Information Officer, CentraState Health System

Spotlight 02

The work of building the team behind the work.

For a long time, I was the only designer at Noteworth, carrying research, product strategy, visual design, prototyping, and stakeholder alignment simultaneously. Scaling to enterprise required more than one person could sustain, so I built the team - defining what great design looked like at Noteworth, recruiting people who could meet that standard, and creating processes that let multiple designers work in parallel without losing coherence. The most important work I did here wasn't any single screen. It was building an organization that could keep shipping after I left.

"Providing health care is no longer just about seeing a patient when they come to the office. Noteworth gives us a way to stay in continuous contact with our patients."

Vice President of Operations, Cedars-Sinai

SELECTED WORK

Care that meets patients where they are.

Noteworth video visits

Video visits, a key feature we developed, saw heavy use throughout the pandemic.

Noteworth clinician dashboard

SELECTED WORK

Growth & Features

Noteworth data collection

Noteworth handled data collection. Clinicians reviewed it, then worked with patients to act on it.

Noteworth clinician and patient workflows

Clinician and patient workflows mapped end to end, connected by the data systems that keep both sides in sync.

SELECTED WORK

Enterprise Scale

Noteworth collect layer

The collect layer: patient-reported data on mobile, surfaced as clinical-grade reporting on the provider side.

Noteworth Active Rules

Active Rules let clinicians define what out-of-bounds looks like. The moment it happens, the patient gets a clear next step.

Noteworth flagged responses

Flagged responses surface before the visit. By the time clinician and patient connect, the conversation is already focused on what matters.

The Takeaway

Ownership changes how you design.

Noteworth taught me what it means to truly own a product - the decisions, the tradeoffs, the organizational dynamics, and the long game. I left with a sharper instinct for when to move fast and when to slow down, and a belief that the best design work is systemic rather than individual.