EngagedMD
I grew EngagedMD’s patient app from e-signatures and learning modules into a mobile-first set of care activities that show patients what to do next, built to work with the staff app.
- Role
- Lead Product Designer
- Team
- 2 Co-CEOs, 10 Engineers & Me
- Engagement Length
- 3 years
- Tools
- Miro, Figma, Coda, Hotjar, Jira
- EngagedMD
- EngagedMD is a healthcare technology company that specializes in providing patient education and informed consent solutions for fertility clinics and healthcare providers. Their platform streamlines the patient onboarding process, offering personalized, easy-to-understand educational content and digital consent workflows. By automating and simplifying complex medical procedures, EngagedMD enhances the patient experience while improving clinic efficiency and ensuring compliance with regulatory requirements.
Problem
Patients could only sign documents and complete learning modules. They couldn’t tell which tasks mattered most, and the app didn’t work well on every device.
Outcome
The new app puts priority tasks first, so patients know what to finish before their visit. Reworked activity types connect to the staff app, work the same on every device, and leave room to grow.
Why are we doing this?
Business Side
Rebuild the patient app as the foundation for managing the complete patient journey.
Customer Side
Fertility patients are short on time and often under real emotional stress. A simple, easy-to-follow app that shows what to finish before the next visit takes some of that weight off.
Discovery
With the co-CEOs, I audited the whole app, then defined the patients’ mindset and needs. I added Hotjar for anonymized usage data, UX bottlenecks, and surveys at critical points in the journey.
Evaluation
Mapping the patient journey showed how patients and staff interact in the real world, so the app could match it. The staff app’s breadboarding had already defined the features and architecture to build on.
Ideate and Iterate
Early wireframes and prototypes, tested with internal and external users, exposed gaps in our first hypothesis, which we fixed. I designed every activity type mobile first, and the first visuals used MUI to speed up development.
Building out the application
Then I laid out the whole app: every screen, device, interaction, and state.
Consistent Design Language
Each component went into the design system once it was stable. The patient app was simpler than the staff app, so its system stayed small while leaving room to grow, and it kept ideation fast and handoff consistent.
Handoff and Launch
Handoff was user stories with Figma assets in JIRA. The whole product team planned capacity a full quarter ahead, not only the next few sprints.