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 — three 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 two different jobs, so this is two case studies with one overview.
Care coordination was fragmented across systems and roles.
Coordinating care means different people — professional caregivers, family caregivers, patients, 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 two distinct jobs — designing the cross-platform experience, and leading it through to a faithful build. They tell different stories, so they get different pages.
One idea, three form factors, one language.
The role-aware experience across all three 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.
Every screen, wireframe next to the production comp it became:
Read the design workOwning the seam between design and build.
I was sole lead on production — the design-to-development pipeline that turns comps into shipped software across three surfaces and parallel sprint tracks. The approved user-story scope engineering built from, the designer redlines that answered edge cases before they became guesswork, and directing the build to keep what shipped faithful to what was designed.
The pipeline I owned — the spec, the redlines, and how fidelity survived the build:
Read the leadership workConnect 2.X launched on schedule and under budget — a unified, role-aware experience, designed and led to a faithful build.
Outcomes here are qualitative — on schedule, under budget, systems unified. No adoption or task-completion figures were captured, so I don’t quote any.