GE Healthcarea case study
Health Harmony · Connect 2.X · via Synchronistic Solutions

GE
Healthcare

One care-coordination system across three surfaces, told as two stories.

Health Harmony’s Connect 2.X was a role-aware platform spanning a tablet caregiver portal, a native iOS bedside appliance, and admin web tools, 3 very different surfaces that had to feel like one product. I co-led the design and solely led the production that got it built. Those are 2 different jobs, so this is 2 case studies with one overview.

one system · three surfaces
tablet · caregiver portal
iOS · bedside
web · admin
one role-aware system
Senior product designProduction leadRole-based UXiOS + tablet + responsive webDesign opsGE Healthcare · via Synchronistic Solutions
01The problem

Why was care coordination so hard to unify?

Because coordinating care means 4 kinds of people, professional caregivers, family caregivers, patients and admins, touching the same information from very different places and needs. Connect 2.X had to replace a patchwork with a single, role-aware experience that spanned a tablet portal, a bedside iOS appliance, and admin tools and still read as one system.

Getting there took 2 distinct jobs, designing the cross-platform experience, and leading it through to a faithful build. They tell different stories, so they get different pages.

STORY 1The design work

One idea, three form factors, one language.

The role-aware experience across all 3 surfaces, built once as interaction logic, then designed for each surface and reconciled into a shared system. Shown honestly, screen by screen, from wireframe to shipped UI: the dashboard, vital signs, medications, the Health Center, and the admin web tool.

Role-based UXiOS bedside applianceMedication managementShared design systemWireframe → hi-fi

Every screen, wireframe next to the production comp it became:

Read the design work
STORY 2The leadership work

Owning the seam between design and build.

I was sole lead on production, the design-to-development pipeline that turns comps into shipped software across 3 surfaces and 2 parallel sprint tracks. The approved user-story scope engineering built from, 86 FCG stories across 16 functional areas, the designer redlines that answered edge cases before they became guesswork, and directing the build to keep what shipped faithful to what was designed.

Design-to-dev pipelineUser-story scope (FCG01-86)Redlines & edge-case docsDirecting the build

The pipeline I owned, the spec, the redlines, and how fidelity survived the build:

Read the leadership work
Where it landed

Connect 2.X launched on schedule and under budget, a unified, role-aware experience, designed and led to a faithful build.