For Interac's Online Payment service, should we emphasize broader merchant adoption or invest in developing more advanced features for existing users?

Introduction

The trade-off we're examining today is whether Interac's Online Payment service should focus on broader merchant adoption or invest in developing more advanced features for existing users. This scenario touches on the classic product management challenge of growth versus depth. I'll analyze this trade-off by considering the current market position, user needs, technical feasibility, and business objectives.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market landscape, I'm thinking Interac might be facing increased competition. Could you share insights on our market share and the competitive landscape for online payment services in Canada?

Why it matters: Helps determine if growth or retention should be prioritized Expected answer: Moderate market share with increasing competition Impact on approach: Would influence whether to focus on acquisition or retention

• Considering our revenue model, I assume we charge merchants a per-transaction fee. Is this correct, and are there any other significant revenue streams for the Online Payment service?

Why it matters: Clarifies the financial implications of focusing on merchant adoption vs. user features Expected answer: Primarily transaction-based revenue model Impact on approach: Would affect the potential ROI of each strategy

• Regarding user behavior, I'm curious about the adoption rate and usage frequency among our current merchants. Do we have data on how often they use our service compared to alternatives?

Why it matters: Indicates whether we need to focus on activation or engagement Expected answer: Varied adoption rates with room for improvement in usage frequency Impact on approach: Could suggest a need for better onboarding or more compelling features

• From a technical standpoint, I'm wondering about the current state of our API and integration capabilities. How easily can we onboard new merchants, and what's our capacity for developing new features?

Why it matters: Assesses the feasibility and resource requirements for each option Expected answer: Solid API with some room for improvement in integration ease Impact on approach: Would influence the timeline and resource allocation for either strategy

• Regarding our product roadmap, are there any major initiatives or partnerships in the pipeline that could impact this decision?

Why it matters: Ensures alignment with broader company strategy Expected answer: Potential partnerships with e-commerce platforms Impact on approach: Might favor merchant adoption if significant partnerships are imminent