The situation
New parents were stitching together multiple apps to track feeding schedules, sleep patterns, diaper changes, vaccinations, and milestones, and none of those apps talked to each other. The information existed, scattered across phone notes, reminders, and memory, but there was no single place to manage it. For sleep-deprived parents in the first months of a child’s life, that kind of scatter is the last thing they need.
What I was brought in to do
I owned the product, defining what got built, in what order, and to what standard, working as Product Owner inside an Agile Scrum team.
What I built
I owned the backlog from day one, covering user stories, acceptance criteria, and sprint prioritization, and I held the roadmap against a defined product vision through four months of sprints.
The app shipped with tracking for feeding, sleep, diaper changes, growth metrics, and crying patterns, along with health appointment and vaccination reminders, milestone capture, community features for peer support, soothing sounds, and curated parenting guidelines.
Much of the work was in deciding what did not ship. With a product for new parents, every stakeholder had an idea about what would be useful, and my job was to protect the core use case of structured daily tracking from being buried under features. I worked closely with designers and engineers to validate usability at each sprint review, adapted the roadmap where user feedback pointed to real gaps, and held QA cycles to the same standard as the product itself.
The result
The result was a production-ready parenting companion delivered in four months. Parents could manage daily baby care in one place, consistently and without friction.