CareHarbor

Context

CareHarbor was built to solve a real and underserved problem: caregiving is fragmented. Care receivers, professional caregivers, and family members rarely operate from the same source of truth. Medications get missed. Appointments get forgotten. Responsibilities are unclear. When something goes wrong, no one has the full picture.

The app was designed as a single place to hold everything—pill management, doctor appointments, a shared schedule that assigned responsibilities to specific caregivers or family members, and the ability to transfer a care receiver’s file between caregivers without losing context. It included notifications for low pill counts, permission systems for family members in emergencies, and built-in communication through chat and video calls. The goal was simple: maximize care, minimize the chance that something critical falls through the cracks.

My Role

Product Manager and UX Designer. This was my first time wearing the PM hat formally—I owned the conversations with stakeholders and the team, scoped what was buildable, and translated the product vision into requirements the developers could execute. On the design side, I was solo. No other designer on the project. That meant every flow, every screen, every component decision came through me.

Process

The process was harder than it should have been. Stakeholders from CareHarbor were not deeply engaged. Meetings were postponed. Questions sat unanswered for days. The team was ready to move; the direction wasn’t. I felt the weight of pushing the project forward when the people who commissioned it weren’t pulling in the same direction.

Eventually we converged. The team aligned on a final vision, and from there we moved efficiently. Five months from final alignment to a launched product. That timeline was only possible because by the time we knew what we were building, the team trusted the plan.

Research

The user picture was clear without needing extensive formal research: care receivers were often elderly, sometimes with reduced motor function or vision. Professional caregivers needed efficiency and clarity—they manage multiple clients and can’t afford friction. Family members are often anxious and time-pressed, checking in between work and other responsibilities. Three audiences, three sets of needs, one app.

Accessibility wasn’t a feature to add later. It was the starting point.

Approach

I designed for clarity above all else. Flat design with flat illustrations—nothing decorative, nothing that competed with content. Large UI components and generous touch targets so the app worked for older users, users with reduced dexterity, and anyone using it in a hurry. High contrast. Simple hierarchies. Predictable navigation.

The structural logic mirrored the real-world caregiving relationship. The care receiver was the center. Caregivers and family members orbited that center with defined permissions and responsibilities. Schedules, medications, appointments—everything attached to the care receiver and was visible to the people who needed to see it.

Final Design

The launched product delivered on the original vision. A unified caregiving system: pill management with low-stock alerts, appointment scheduling with assigned responsibilities, file transfer between caregivers, family permissions for emergencies, integrated chat and video calls. The interface was accessible, calm, and easy to navigate.

Impact

The app launched. It did not find its audience. CareHarbor is no longer available on the App Store or Play Store.

I think about why often. The product was solid. The problem was real. But a product that ships into a market without strong stakeholder commitment to growing it rarely survives. Building something is only half the work. The other half is the sustained push to find users, listen to them, and iterate. That push didn’t come.

What I Learned

Stakeholder engagement is part of product success, not separate from it. A disengaged client doesn’t just slow down the build. It signals what will happen after launch. I learned to read those signals earlier. Now I look for stakeholder commitment as a leading indicator of whether a product will survive its first year.

Product management is making the room move. When stakeholders went quiet, the project still needed direction. Someone had to keep the team productive while waiting for answers. That responsibility taught me what product managers actually do—it’s not just specs and roadmaps. It’s holding momentum when nobody else is.

Accessibility as a starting point produces better design for everyone. When I designed for the most constrained user—an elderly care receiver with reduced dexterity—every other user benefited. Large touch targets, high contrast, and predictable navigation are not compromises. They’re improvements. I’ve designed differently ever since.

A product that doesn’t survive isn’t always a product that failed. CareHarbor solved the problem it set out to solve. It didn’t fail at design. It didn’t fail at execution. It didn’t reach the people who needed it because the conditions for that reach weren’t in place. Separating the quality of work from the outcome of the business is one of the harder lessons of building things.