top of page

Consumer Health Product Strategy: Improving Care Coordination with KinKeeper

KinKeeper is a consumer health application designed to help individuals and families manage medical records, notes, and care coordination across multiple providers. As Product Manager, I led user research, roadmap development, and feature launches that improved onboarding clarity and expanded the platform’s core medical record capabilities. The initiative focused on simplifying the user experience while strengthening the product’s ability to centralize health information.

Business Context

KinKeeper is a consumer health application designed to help individuals and families better manage medical information across multiple providers and care journeys. The platform aimed to centralize medical records, personal health notes, appointments, and care coordination in a single location that could be shared with trusted family members.

​

Many individuals managing complex health conditions—or supporting family members through illness—struggle with fragmented medical information spread across multiple Electronic Medical Record (EMR) portals, personal notes, and provider systems. KinKeeper sought to simplify this experience by providing a centralized platform for organizing health information and coordinating care.

​

As the product matured, the founders identified an opportunity to improve user onboarding, engagement, and feature clarity in order to increase adoption and retention.

​

Why This Mattered:

  • Patients and caregivers often manage health information across multiple provider portals and disconnected tools

  • Important health details, such as test results, notes, medications, and appointments, are difficult to consolidate

  • Caregivers frequently need to share health information with family members or support networks

  • Without clear onboarding guidance, new users struggled to understand how to effectively begin using the platform

 

What Triggered the Initiative:

  • User interviews and early customer feedback revealed confusion around how to start using the application

  • The product needed stronger feature clarity and onboarding guidance

  • The founders wanted to expand the platform’s ability to capture and organize key medical records, particularly test results

Problem Statement

Individuals managing personal or family healthcare often struggle to organize medical information across fragmented systems. Without a centralized platform to capture records, notes, and provider information, users must manually gather and share health data across multiple sources, creating friction in care coordination and health management.

​

KinKeeper needed to improve its onboarding experience and expand core features so users could more easily understand how to begin managing their health information within the platform.

Product Strategy

The product strategy focused on simplifying the user experience while strengthening the platform’s core record management capabilities.

​

Rather than expanding into many advanced features, the initiative prioritized improving the usability and clarity of the core product experience, helping users more quickly understand how to organize and manage their health information.

​

Key strategic pillars included:

  • Improving onboarding to guide users through their first meaningful actions in the product

  • Expanding the platform’s ability to capture and organize important medical records

  • Prioritizing the most valuable record types, such as test results

  • Focusing on features that reinforced existing user behavior and engagement patterns

My Role:

Scope of ownership:

  • Product roadmap development

  • Feature definition and prioritization

  • Product requirements documentation

  • User research and interviews

  • UX collaboration with the engineering team

 

Decision authority:

  • Influenced roadmap prioritization

  • Recommended feature tradeoffs based on user feedback and product strategy

​

Team size:

3–4 people, depending on development cycles

​

Cross-functional partners:

  • Co-founders

  • Offshore engineering team

​Key Actions I Led:

  • Conducted user interviews to identify pain points around onboarding and medical record organization

  • Defined the product roadmap for improving core health record management

  • Wrote product requirements and user stories for new feature development

  • Partnered with engineering to refine UX flows and improve homepage usability

  • Led the development and launch of new features focused on expanding supported medical record types

 
Product Strategy Decisions:

Tradeoffs Made:

Several strategic tradeoffs were made to ensure the team focused on improvements that would deliver the greatest user impact within a small development team.

​

  • Prioritized simplicity and usability over feature depth

  • Focused on improving the homepage experience to better highlight core product functionality

  • Prioritized test result integration as the most valuable medical record type for users

 

What I Said No To:

To maintain focus on core product improvements, several potential features were intentionally deferred, including:

​

  • Full integration across all EMR record types

  • Family medical history features

  • AI-powered chatbot support

  • Practitioner sharing across family profiles

  • Medication management and tracking

  • Ownership transfer between family members

 

How I Prioritized:

Prioritization decisions were guided by:

​

  • User interview insights

  • Founder feedback and product vision

  • Impact vs effort evaluation

  • Alignment with the product’s core goal of improving health information organization

​

Senior-Level Signals:

  • Introduced structured product practices including roadmap planning, user interviews, and sprint coordination

  • Influenced product strategy through direct collaboration with the founders

  • Applied personal healthcare experience as a cancer survivor to offer perspective on real-world patient needs

  • Balanced user needs, technical constraints, and product vision within a small startup environment

 
What I’d Do Differently:

If I were building KinKeeper again, I would:

  • Narrow the initial target audience to focus on a specific healthcare use case, such as chronic condition management or caregiver coordination

  • Invest earlier in refining the core feature set before expanding into additional record types

  • Implement stronger product analytics to better measure onboarding success and feature adoption

Metrics | Impact

While detailed product analytics were limited at this stage of the product, qualitative feedback and user responses indicated improvements in onboarding clarity and feature usability.

​

Revenue impact:

Freemium product model — focus on improving engagement and adoption

​

Efficiency gains:

  • Reduced onboarding confusion by providing clearer guidance for first-time users

​

Adoption:

  • Expanded product capabilities allowed users to store additional types of medical records

​

Risk mitigation:

  • Focused development efforts on the most impactful features for early product growth

​

Time savings:

  • Simplified process for organizing and reviewing medical records in a single location

bottom of page