In Medable's TeleHealth module, should we focus on expanding features for remote patient monitoring or improving the video consultation experience?

Introduction

In Medable's TeleHealth module, we're faced with a critical decision: should we prioritize expanding features for remote patient monitoring or focus on improving the video consultation experience? This trade-off involves balancing the needs of patients, healthcare providers, and our business objectives. I'll analyze this decision through the lens of product strategy, user impact, technical feasibility, and business alignment.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking remote patient monitoring might be a growing segment. Could you share any data on the adoption rates of our remote monitoring features compared to video consultations?

Why it matters: Helps prioritize based on user demand and potential growth areas Expected answer: Remote monitoring showing higher growth but lower current usage Impact on approach: Would influence resource allocation between the two features

• Considering our revenue model, I assume we charge healthcare providers per feature or patient. Is this correct, and are there any differences in monetization between remote monitoring and video consultations?

Why it matters: Aligns decision with financial impact and business model Expected answer: Per-feature pricing with higher margins on remote monitoring Impact on approach: Would prioritize the more profitable feature if user value is comparable

• Looking at our user segments, I'm curious about the demographics and conditions of patients using these features. Do we see any significant differences between remote monitoring and video consultation users?

Why it matters: Ensures we're addressing the needs of key user segments Expected answer: Chronic condition patients prefer remote monitoring, acute cases favor video Impact on approach: Would tailor feature development to specific user needs and conditions

• From a technical perspective, I'm wondering about the scalability of our current infrastructure for both features. Are there any significant technical limitations or opportunities for either option?

Why it matters: Identifies potential technical constraints or advantages Expected answer: Video scaling is more challenging due to bandwidth requirements Impact on approach: Might prioritize improving video if it's a current bottleneck

• Regarding our development resources, how are our teams currently structured? Do we have specialized teams for each feature, or a shared resource pool?

Why it matters: Determines feasibility of parallel development or need for prioritization Expected answer: Shared resource pool with some specialization Impact on approach: Would influence how we allocate resources and prioritize development