Our team had the task of improving WellWave, a med-tech wearable product. When we first approached this task, we were overwhelmed by the number of directions we could possibly take to innovate. During our early team meetings, we had listed over ten possible new features – everything from advanced sleep tracking to medication reminders – and found ourselves grappling with the critical task of prioritization.
Throughout this project, I gained deep insights into the delicate balance product managers must strike between innovation and practicality. I learned that having abundant resources and several features doesn’t necessarily translate to product success – it’s about making strategic choices that align with both market needs and business capabilities. This became particularly evident when our team was strongly considering the inclusion of continuous glucose monitoring. While the technology was promising and demanded by potential users, our analysis of WellWave’s existing capabilities and the regulatory timeline made it clear we needed to push this to a later phase. Those kinds of decisions taught me that being a PM often means making tough choices based on both data and intuition.
Our pivot to purely focus on the elderly care sector was a turning point in our project. This decision was not just about finding a new market – it was about discovering where WellWave’s strengths could create the most value. What initially seemed like product limitations in the broader wearables market became advantages in the elderly care space, where simplicity and reliability were paramount. This realization demonstrated to me how product management isn’t just about building new features, but about finding the right problem to solve. Our team’s work on financial modeling and risk assessment brought another layer of reality to our product planning. We had to justify every feature not just in terms of user value but also in terms of development costs and market potential.
Overall, I had a great experience collaborating with my team to work on this product. We established an efficient workflow by dividing responsibilities, provided valuable feedback to another, and maintained a laser focus on creating genuine value for our users. This project undoubtedly taught me a lot about the different considerations PMs have to be mindful of, and my main takeaway is that success as a PM is not always about having innovative ideas or new technical capabilities – rather, it is about finding the right market fit and executing with a clear understanding of both user needs and business constraints.
