Overview

Picture a 74-year-old managing her own life: one app for rides, another for medication reminders, a third for booking help around the house, a portal for appointments, and a daughter three time zones away holding it all together over phone calls. Nobody designed this system. It just accumulated.

I led the end-to-end product thinking and design for HESS (Health, Emergency, Safety, Support), a concept for a unified elderly support platform that brings daily care, healthcare coordination, and safety into a single experience. The goal was to restore autonomy to seniors while giving caregivers peace of mind, with technology supporting the care relationship instead of straining it.

My role: Product Design Lead

Responsibilities: Problem Framing, User Research Synthesis, Product Strategy, UX & Visual Design, Prototyping

Timeline: 3 weeks

The Cost of Fragmentation

Through secondary research and stakeholder discussions, the scale of the problem became hard to ignore:

Behind each number is the same root cause: seniors and caregivers juggle 4 to 6 separate apps for transportation, medication, appointments, and home services. That fragmentation means repeated data entry, missed handoffs between services, and growing dependency on family members to hold the system together. Studies link fragmented care delivery to 20% higher hospital readmission rates. Poor coordination has a real clinical cost.

Understanding the Users

Designing HESS meant designing for the whole ecosystem of people who participate in care.

Independent Seniors (primary): cognitively capable and motivated to live on their own terms. They want dignity and autonomy, resist anything that feels intrusive or infantilizing, and respond far better to gentle nudges than to supervision.

Family Caregivers (primary): often adult children balancing jobs, families, and invisible coordination labor. They carry burnout and anxiety, and want reassurance without micromanaging a parent's life.

Service Providers (secondary): caregivers, drivers, and healthcare professionals who need reliable schedules, accurate context, and less back-and-forth.

Across all three, one shared failure point emerged: there is no single surface for coordination and action.

The Directions I Didn't Take

Before defining the MVP, I explored several directions and deliberately set them aside:

• A caregiver-first dashboard focused on oversight. It eased the caregiver's anxiety at the senior's expense: constant monitoring increased dependency and eroded the dignity we were designing for.
• A health-records-centric experience. Clinically thorough, yet it felt cold and overwhelming. Seniors described this direction as feeling "like a hospital in my pocket."
• A service marketplace with add-on safety features. Flexible, yet it lacked the trust and continuity that care relationships demand.

Solution Space Explorations

The strongest direction balanced autonomy for seniors with visibility for caregivers, without forcing constant involvement from either side. Each rejected path sharpened that conviction.

Defining the MVP

I scoped the MVP around three integrated pillars. Each one is a promise to the user.

Daily Care

One request for every daily need

Housekeeping, personal care, companionship, transportation, and medication reminders all live in a single place. No app-switching, no re-entering the same information, no coordination overhead falling back on family.

Healthcare Coordination

Healthcare made actionable

HESS focuses on what a senior can act on today: medication lists, appointment history, emergency contacts, and gentle reminders. It supports continuity of care while avoiding the clinical complexity that makes health tools feel like hospitals.

Urgent Support

Help that arrives without a struggle

One-tap emergency alerts, automatic GPS sharing, and instant updates to caregivers and responders. Safety features are designed for speed and clarity first, because no senior should have to navigate a complex flow under stress.

Design Style Guide

To ensure accessibility and trust, I prioritized a high-contrast color palette, clear typography, and intuitive iconography. The visual language does quiet work: it makes complex healthcare management feel safe and straightforward, which is what builds the confidence to actually use it.

Design Style Guide

Validation and Early Feedback

I tested the prototype with 5 participants across seniors and caregivers using moderated walkthroughs.

Seniors consistently responded positively to language that emphasized independence rather than assistance, which validated the reframing at the heart of the product.

Where This Goes Next

HESS is a concept-stage product, and early validation suggests the unified model holds: reduced cognitive load for seniors, lower coordination stress for caregivers, better adherence through gentle nudges, and faster emergency response through shared context.

If I took this further, three things would come first:

• Validate the provider side. The MVP centers seniors and family caregivers, while service providers were researched and never tested. Their adoption makes or breaks the coordination promise.
• Test long-term trust beyond first impressions. Walkthroughs measure intuitiveness. Whether a senior still trusts the SOS flow after three months of daily use is a different and more important question.
• Pressure-test the independence framing. It resonated in research, and the line between "gentle nudge" and "surveillance" will shift as families actually use it. That tension deserves ongoing design attention.