proudP is a personal urinary health monitor that analyzes the sounds of urination to provide clinical indicators of prostate and bladder health. As a Software as a Medical Device (SaMD), proudP offers clinical accuracy and feasible interaction. Endorsed by urologists and embraced by patients, proudP enables remote monitoring in clinical practices, comprehensive data collection for clinical studies, and convenient at-home self-monitoring.
Product Designer
Conducted user interviews.
Led UX & UI design through 3 major updates.
Feature development.
Product Management team
1 Front-end Engineer
1 Back-end Engineer
Business Team
Figma
Jira
Apple App Store Analytics
Adobe Photoshop / Illustrator / After Effects
With a diverse user base that includes clinicians, clinic-referred patients, and self-directed individuals who discover proudP independently, it was crucial to identify and prioritize the needs specific to each group. Understanding these distinct user segments helped us tailor the platform to accommodate the varying levels of familiarity and requirements with the uroflow test, ensuring an intuitive experience for all.
With the Healthcare Innovation Park of Bundang Seoul National University Hospital, We recruited four middle-aged men and observed the process of downloading the app, signing up, and how they would use the product based on the instructions. We assessed the app quantitatively through questionnaires and qualitatively identified areas for improvement through interviews.
Based on in-depth interviews, we identified that patients frequently struggle to properly integrate and transmit their uroflometry data and related health questionnaires to clinical dashboards. This failure leads to significant gaps in urological health insights, which in turn hinders effective treatment and monitoring. The renewed design approach focuses on two main objectives.
How might we encourage users to measure more frequently and answer additional questionnaires?
Instead of organizing data strictly by dates, we divided sections by their input data to allow users to focus on completing one section at a time.
To spark curiosity, we had previews with a subtle blur to sections that were undone, inviting users to tap or hover to reveal more information, thus motivating them to engage further.
How could we make data more meaningful beyond just numbers?
Patients complete various symptom questionnaires alongside the uroflow test, including IPSS, IIEF, and others. As these results tend to be forgotten after initial checking, there was a need to consolidate them into one platform for monitoring.
Additionally, interpreting the results of uroflow tests without the doctor's explanation could be challenging for patients with only graphs given. Test scores often remain just numbers unless actively sought, providing limited insight. To enhance understanding each test result had a result card created with visual indicators and additional explanation.
How do we decrease missed connections between patients and clinicians?‘
Connect to Doctor’ played a crucial role in our service since it linked the patients’ data to the clinicians’ dashboard. Often there were users skipping this part which resulted in patient data not appearing on the doctor's dashboard. Instead of QR code and clinic code, we refined the onboarding process and implemented doctor searching feature allowing patients to easily find and connect with their doctor by name or clinic.
How could we deliver insightful information from multiple real-time data?
We have transformed the Activity tab into an Insights tab, providing a comprehensive view of bladder diaries, trends in voiding records, and educational materials. Previously, there might have been confusion between the contents that the Dashboard and Activity tabs contain. Now, all test records are neatly organized in the form of result cards on the Home tab, while the right tab serves as a dedicated space for in-depth information.
Collaboration Between Business and Product Teams in proudP
In our journey developing proudP, all team members were united in their commitment to improve our product's user experience that positively influenced our collaboration. However, the development process faced challenges due to alternating leadership between the business and product teams. This shift in leadership caused some inconsistencies in the direction of our product development. As we explored various market positioning strategies for our product, the emphasized features frequently changed, which may have caused confusion from a user perspective.
In retrospect, establishing a single North Star metric in line beforehand would have been beneficial. This unified direction could have ensured that both the business and product teams were aligned, facilitating smoother and more coherent product development.
