For McKesson's RelayHealth pharmacy management software, should we prioritize adding advanced analytics features or focus on improving user interface simplicity for pharmacists?

Introduction

For McKesson's RelayHealth pharmacy management software, we're facing a critical trade-off between adding advanced analytics features or improving user interface simplicity for pharmacists. This decision will significantly impact our product's value proposition and user experience. I'll analyze this trade-off by examining the product context, stakeholder needs, potential impacts, and experimental approaches to inform our decision.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market position of RelayHealth. Could you provide more insight into our market share and primary competitors?

Why it matters: Helps determine if we need to differentiate or catch up to competitors Expected answer: Moderate market share with 2-3 major competitors Impact on approach: Would influence whether we prioritize innovation or parity features

• Business Context: Based on our revenue model, I assume we charge per pharmacy or per transaction. Is this correct, and are there any upcoming changes to our pricing strategy?

Why it matters: Aligns feature development with revenue generation Expected answer: Per-pharmacy licensing model with transaction-based add-ons Impact on approach: Would affect whether we focus on features that drive adoption or increase transaction volume

• User Impact: I'm considering the different pharmacy staff roles. Can you clarify which user segments (e.g., pharmacists, technicians, managers) are our primary focus for this decision?

Why it matters: Ensures we're addressing the needs of our most critical users Expected answer: Pharmacists are the primary users, but managers make purchasing decisions Impact on approach: Would guide UI simplification efforts and analytics feature set

• Technical: Regarding our current architecture, I'm assuming we have a cloud-based solution. Is this correct, and do we have any significant technical debt or upcoming platform changes?

Why it matters: Determines the feasibility and long-term sustainability of new features Expected answer: Cloud-based with some legacy components, planning a major update in 18 months Impact on approach: Would influence the scope and timing of new feature development

• Resource: Considering our development capacity, what's our current team size and structure for RelayHealth?

Why it matters: Helps assess our ability to execute on different feature sets Expected answer: 3-4 scrum teams with a mix of front-end, back-end, and data science expertise Impact on approach: Would impact the timeline and feasibility of implementing complex features