Should NYU Langone Health's patient portal prioritize ease of use for older patients or advanced features for tech-savvy users?

Introduction

The trade-off we're examining today is whether NYU Langone Health's patient portal should prioritize ease of use for older patients or advanced features for tech-savvy users. This scenario presents a classic product dilemma: balancing simplicity with functionality to serve diverse user needs. In my response, I'll walk through a structured analysis to arrive at a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming this patient portal is a critical touchpoint for NYU Langone's patient engagement strategy. Could you confirm if this is a new initiative or an update to an existing portal?

Why it matters: Helps determine if we're working with an established user base or starting fresh. Expected answer: Existing portal being updated. Impact: If new, we might have more flexibility; if existing, we need to consider migration and user expectations.

• Business Context: Based on healthcare trends, I'm thinking patient satisfaction scores might be a key performance indicator. How does portal usage tie into NYU Langone's broader patient experience metrics?

Why it matters: Aligns our solution with business objectives. Expected answer: Strong correlation between portal usage and patient satisfaction. Impact: High correlation would justify investing in usability for all demographics.

• User Impact: Considering the diverse patient population, what's the current age distribution of portal users?

Why it matters: Helps quantify the potential impact on different user segments. Expected answer: Skewed towards older patients, but growing younger user base. Impact: Even distribution might suggest a dual-interface approach; skew would prioritize one group.

• Technical: I'm curious about the current architecture. Is the portal built on a modular system that allows for personalized user experiences?

Why it matters: Determines the feasibility of serving different interfaces to different users. Expected answer: Somewhat modular, but significant changes would require substantial development. Impact: High modularity would enable us to consider a segmented approach more easily.

• Resource: Given the potential scope, what's our development team's capacity for this project over the next quarter?

Why it matters: Helps set realistic expectations for implementation timelines. Expected answer: Limited bandwidth due to other ongoing projects. Impact: Limited resources might push us towards a phased approach rather than a complete overhaul.