For NYU Langone Health's mobile app, should we focus on expanding health tracking features or improving appointment scheduling functionality?

Introduction

For NYU Langone Health's mobile app, we're facing a critical trade-off between expanding health tracking features and improving appointment scheduling functionality. This decision will significantly impact user engagement, patient care, and operational efficiency. I'll analyze this trade-off by examining user needs, business goals, technical considerations, and potential outcomes to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming NYU Langone Health is looking to enhance its mobile app to improve patient engagement and streamline operations. Could you provide more context on the current app usage and any specific pain points that led to considering these two features?

Why it matters: Helps prioritize features based on current user needs and pain points. Expected answer: Low engagement with existing features, user complaints about appointment scheduling. Impact on approach: Would focus on addressing immediate user needs first.

• Business Context: Based on healthcare industry trends, I'm thinking improved appointment scheduling might directly impact revenue and operational efficiency. How does this align with NYU Langone's current strategic priorities and revenue model?

Why it matters: Ensures alignment with overall business strategy. Expected answer: High priority, directly impacts patient satisfaction and operational efficiency. Impact on approach: Would justify prioritizing appointment scheduling if it's a key revenue driver.

• User Impact: Considering the diverse patient population, I'm curious about the user segments most affected by these potential improvements. Can you share insights on which user groups are most active on the app and their primary use cases?

Why it matters: Helps tailor features to meet the needs of key user segments. Expected answer: Chronic condition patients use health tracking more, while general patients struggle with appointment scheduling. Impact on approach: Would inform feature prioritization based on user segment needs.

• Technical Feasibility: Given the complexity of healthcare systems, I'm wondering about the technical challenges involved in expanding these features. What are the current limitations or integration issues with existing systems?

Why it matters: Assesses the feasibility and resource requirements for each option. Expected answer: Appointment scheduling requires complex integration with multiple systems. Impact on approach: Would consider technical constraints in feature prioritization and implementation timeline.

• Resource Allocation: Considering the scope of both features, I'm thinking about team capacity and budget constraints. What resources are currently available for this project, and are there any limitations we should be aware of?

Why it matters: Helps determine the feasibility of implementing both features simultaneously or sequentially. Expected answer: Limited development resources available, need to prioritize one feature. Impact on approach: Would influence the recommendation to focus on one feature or a phased approach.