Skip to main content
View
project

Positivity — Mental Health Platform

Positivity needed more than new screens — it needed a design system, conflict-free scheduling, and a developer handoff process that could keep pace with the product. As a design consultant, I worked across all three, building a 25-component design system and redesigning scheduling logic across 45+ screens, guided by one question at every step: does this create or reduce anxiety?

View Figma File
Dashboard screenshot

Project Snapshot

Built as a design consultant at Positivity.

A look at the scope, team, and contributions that shaped a design system, scheduling logic, and handoff process for a mental health platform.

Role
Product Design Consultant
Timeline
Jul 2022 – Present
Team
Solo Designer · Engineering · Clinical Advisors
Contribution
Design System Architecture · Component Design · Scheduling UX · Developer Handoff · UI Design · Clinical UX Consultation
02At a Glance

Built for calm, conflict-free scheduling.

A single design system and conflict-detection logic now support every session booked, every handoff, and every screen shipped.

Zero
Scheduling
Conflicts
25
Design System
Components
45+
Screens
Covered
3↓ from 7
Handoff Cycle
Days
03The Challenge

Positivity had grown faster than its foundations.

No design system, scheduling conflicts causing double-bookings, and a slow developer handoff process were all blocking the product at once — in a product where every misstep carries more weight than usual.

Double-Booking Risk

Scheduling conflicts were slipping through, damaging trust in the platform with every repeat occurrence.

No Shared Design Language

Inconsistent UI patterns across screens made the product feel disjointed and harder to trust.

Handoff Gaps

Missing specifications meant shipped features regularly diverged from the original design intent.

Slow Screen Delivery

Without a component library, every new screen was built from scratch, slowing the whole team down.

Scaling Without a System

45+ screens needed consistent coverage, but there was no foundation to build from.

Anxiety-Inducing Errors

In a mental health context, a scheduling error isn't just inconvenient — it undermines the therapeutic relationship.

04Research Insights

Understanding what calm actually requires.

Research combined interviews with platform users and therapists, a root-cause analysis of scheduling conflicts, a handoff process audit, and consultation with clinical advisors.

Key Insight
Scheduling errors destroy trust completely

A double-booking in a mental health context doesn't just inconvenience — it damages the therapeutic relationship and the platform's credibility.

Confirmed
Pending
Checked-in
Cancelled
Conflicts surfaced too late
Calm is a design output, not a style choice

Inconsistent UI, unexpected animations, or cluttered screens create measurable anxiety. Visual consistency is therapeutic, not just aesthetic.

Visual noise adds up
Handoff quality determines build quality

The gap between design intent and shipped product tracked directly with how complete the specs were.

Roles need different specs
A design system pays forward

Every hour invested in the component library returned multiple hours on subsequent screens.

Reused components, fewer errors
Conflict-detection is a UX problem

The way scheduling conflicts were surfaced and resolved was as much a design responsibility as an engineering one.

Timelines need to resolve conflicts
RESEARCH METHODS

A mix of qualitative and quantitative approaches.

User & Therapist Interviews
18+
Conflict Root-Cause Sessions
10+
Handoff Process
Audits
3 Cycles
Clinical Advisor
Consultations
6+
Competitor Platforms
Reviewed
5 Platforms
05Design Principles

Principles that guided every design decision.

Four principles shaped every screen, every scheduling flow, and every line of specification — keeping the experience calm even as the product grew more complex.

Calm as a Design ValueSystem Before ScreenConflict-Detection is UXSpec for the Developer
01
Calm as a Design Value

In mental health contexts, visual noise is harmful. Every design decision must ask: does this create or reduce anxiety?

02
System Before Screen

A component library built upfront pays compound interest — every new screen is faster, more consistent, and cheaper to hand off.

03
Conflict-Detection is UX

Scheduling logic is not purely an engineering concern. The user experience of an error message is a design failure, not just a bug.

04
Spec for the Developer

Design handoff quality directly determines how faithfully the product gets built. Invest in documentation as much as in the design itself.

06The Solution

Building a calmer product from the ground up.

Rather than patching individual screens, the focus was on a system that made every future screen faster, safer, and more consistent to ship.

01
Conflict-Detection Scheduling

Scheduling logic that surfaces and resolves conflicts before they can be confirmed, eliminating double-bookings entirely.

Scheduling screenshot
02
A 25-Component Design System

Every screen now draws from a shared library of patterns, giving the whole product a calmer, more consistent feel.

Design system screenshot
03
Developer-Ready Specifications

Comprehensive handoff documentation — states, interactions, and edge cases — cut iteration cycles from seven to three.

Handoff documentation screenshot
Design System
Conflict Detection
Full Coverage
Dev Handoff
07Understanding the Ecosystem

Scheduling doesn't happen in isolation

Before redesigning the experience, I mapped how sessions, therapists, and clients moved through the platform — so conflict-detection logic could be built where it mattered most.

08Design System

Building better interfaces with design systems.

A scalable design language built for a sensitive product — color, typography, spacing, and 25 components designed for consistency, not just efficiency.

Design system applied — component library mockup
01Color System
Primary
#1C46F2
#8a9ff4
#859dff
#dde3fd
#111111
Semantic
Success
Warning
Error
Info
Neutral
Neutral Scale
02Typography — Manrope
AaManrope
Heading 1
34–56px / 1.15
Regular
Heading 2
28–42px / 1.3
Regular
Heading 3
18–22px / 1.3
Regular
Body
13.5–16px / 1.6
Regular
03Spacing & Layout
Spacing Scale
4
4px
8
8px
12
12px
16
16px
24
24px
32
32px
48
48px
64
64px
09 — IMPACT

Designed for calmer, more reliable operations.

The redesign eliminated scheduling errors entirely, while giving the product team a system built to scale carefully rather than quickly.

01
Zero

Scheduling errors — eliminated by conflict-detection logic

02
25

Components in the new design system

03
7 → 3

Developer handoff cycles reduced per feature

04
45+

Screens covered with developer-ready specs

10 — LESSONS LEARNED
01
Sensitive products need a different lens.

Every decision has to ask: does this create or reduce anxiety?

02
A design system is a first deliverable, not an afterthought.

Built early, it paid back multiple hours on every screen that followed.

03
Design is incomplete until it's built correctly.

Specification quality is the last mile of the design process, not overhead.

04
Scheduling errors are a trust problem.

A double-booking damages the therapeutic relationship, not just the calendar.

05
Consistency is therapeutic, not just aesthetic.

Visual noise and unpredictability create measurable anxiety for users.

06
Conflict-detection is a design responsibility.

How an error is surfaced and resolved matters as much as preventing it in engineering.

More work

Other case studies

View all →
Hospitality Technology

Reservation Management System

Enterprise UX / 2023

Hospitality Tech

Point of Sale — Restaurant Operations

Mobile App / 2023

Hospitality Tech

Central Reservation Office

Enterprise UX / 2023