Heart Disease Risk Tool
Professional Cardiology Association
6 Years
Washington D.C
PROJECT SUMMARY |
My Challenge
As product manager for a heart disease management tool for cardiologists, part of my job was to plan and manager updates to the tool based on frequent changes in science and research. This tool was openly available in the app store and as a web version, and thus the changes need to be quick to make sure the medical advice stayed up-to-date, careful to make sure the tool remained clear and accurate, and thoughtful to make sure the tool remained usable in busy clinical settings. |
In one particular instance, a large change in the tool led to a misinterpretation of information within the app, and a large decrease in usage. The challenge was to use product monitoring to detect the change in the first place, and use smart research and design to determine why it had occurred, implement a solution, make sure it was effective, and update our overall processes to avoid a similar issue in the future.
|
|
My Methods
|
Key Findings
|
Solutions & Outcome
As product manager, I implemented two solutions: Design Solution: In addition to adding careful clarifying language, I led the team through developing a feature that allowed users to enter a minimum set of data for a "light" output, or choose to continue entering full data for a "full" output. Lesson Learned: I directed the team in revising our user testing recruiting plans to make sure that all necessary perspectives were covered. As a result of the implementation of the solution about, we regained more than half of the lost users and sessions within the tool, and avoided any similar plunge in usage from future updates. |
Project Details
Problem Discovery |
The app in question was originally launched in 2014 and had, over the years build a strong and regular repeat user base. In 2017, the science behind the app was updates, and as the product manager, developed a plan for a major overhaul and update in partnership with a clinical working group, collaboration with the design and engineering teams, and a schedule of usability testing.
|
We launched the app update in mid-August. My monitoring and reporting of the post-launch analytics revealed a quick and sharp drop in app users and sessions.
|
My first step was to turn to our immediately-accessible data collection to sources - app stores comments, in-app survey results - to see if they provided any clue to what the issue might be. I then compared common user complaints with event rates via Google Analytics to see if user behavior supported them and revealed anything news.
Some key findings were:
|
|
|
Outcome &
|