Nylas

One place for businesses to set up and manage their scheduling pages: event info, availability, booking options, communications, booking forms and page styles.

Goal: an out-of-the-box editor developers could embed in their own apps, simple enough for their customers to use without help.

My role: I championed the UI/UX end to end, working with the PM, engineering and 5+ stakeholders to understand the key pain points and requests from customers and their end users. I reworked the information architecture and user flow so related settings are grouped logically, and designed for every edge case, error state and permutation.

Outcome: shipped as part of an update that addressed 125+ feature requests from customers and their end users.

The booking page our customers' end users see when picking a time: available days, time slots, time zone and language, delivered as a pre-built web component.

Goal: a booking experience that works out of the box and is easy for developers to customize to their own brand.

My role: I led the design end to end, working with the PM, engineering and stakeholders to shape the core booking flow. I designed for the details that make scheduling trustworthy, like flagging conflicting availability when an end user's calendar is connected, required fields, and error states such as cancelling a booking.

Outcome: shipped as part of the same update that addressed 125+ feature requests.

A new design system web component library for the entire Scheduler product, the shared foundation behind both the Scheduling Editor and the Scheduling Page.

What I did: I created the component library and documented its colour and naming system (primary, info, success, warning, error and a full range of base shades), with notes on where each token is used, so developers know exactly what to change when theming the Scheduler to match their brand.

Outcome: shipped with Scheduler v3. This sat alongside my wider work contributing to and maintaining the Nylas design system.