Pippa

A two-sided healthcare platform shaped by conversations with 200+ clinics. I owned scope, task breakdown, the release calendar, and the documentation clinics onboard with.

Pippa sits between outpatient clinics and their patients. I ran discovery, turned it into a backlog, and kept the release calendar. The product decision that defined it: clinicians need the numbers, patients must not see them, and a family member is a third audience with a shorter list.

Problem

Clinics were describing five products at once. Patients were describing a fear of being graded. If those landed in one backlog with no cuts, the first release would have been a dashboard nobody opened and a logger that felt like a test. We also had to onboard a clinic without putting an engineer on the phone.

Process

I ran calls with 229+ clinicians and wrote down the repeated jobs: know who logged, see the meal, leave a note, send a measure, keep a safety plan. Those became the chart. Everything else waited. Patient safety rules were product requirements, not a later polish pass. Consent, with a signature and a photo, is the gate to the chart. Releases ran in two-week slices. The file a clinic receives explains consent, plans, notes, and reporting in their language.

Solution

• One backlog, prioritized from the repeated clinical job, not from the loudest feature request.
• Three audiences written as product rules. Clinician sees intake and notes. Patient does not see calories. Family sees meals, mood, and the safety plan, and does not see the journal or the clinical note.
• A two-week cadence from first requirement to clinics in production.
• Onboarding docs so staff are not waiting on the core team to use the product.

Results

• 229+ Clinicians in discovery
• 200+ Clinic discovery & support calls
• 10K+ Daily users
• 2 weeks The release cycle

Justin Moran · Project Manager · Chicago, IL · LinkedIn · Resume (PDF)