Suppose you're building a peer-to-peer money transfer product. You have a choice to pursue one of two projects: you can either add bill-splitting functionality or a feature to let users send money to charities. How would you choose which feature to build?

Introduction

Thank you for presenting this strategic challenge regarding our peer-to-peer money transfer product. We're faced with a choice between adding bill-splitting functionality or a feature to let users send money to charities. This decision is crucial as it will impact our product's growth trajectory, user engagement, and potentially our market positioning.

Our key business objectives likely include increasing user acquisition, improving retention, and expanding our market share in the competitive fintech space. To address this strategic problem, I'll walk you through a structured approach that includes:

1. Clarifying our strategic goals
2. Analyzing the market and competitive landscape
3. Defining our product vision and roadmap
4. Prioritizing strategic initiatives
5. Outlining an execution plan
6. Establishing key performance indicators
7. Managing risks and planning contingencies

Let's begin by aligning on our strategic goals to ensure our decision supports the company's overall direction.

Step 1

Clarify the Strategic Goals (3-4 minutes)

• Based on the nature of peer-to-peer money transfer products, I'm assuming we're in a growth phase, focusing on user acquisition and engagement. Could you confirm where we are in the product lifecycle and how this aligns with our company's current priorities?

Why it matters: This determines whether we prioritize rapid expansion or focus on deepening user engagement. Expected answer: Growth stage, emphasizing user acquisition while improving retention. Impact on approach: Would focus on features that drive both acquisition and engagement simultaneously.

• Looking at the two feature options, I'm curious about our target audience. Are we primarily serving a younger, tech-savvy demographic, or do we have a broader user base across different age groups?

Why it matters: Different demographics have varying needs and preferences for financial tools. Expected answer: Primarily younger, urban professionals but expanding to a broader audience. Impact on approach: Would tailor feature selection to appeal to our core users while considering expansion potential.

• Considering the competitive landscape, are we positioning ourselves as a utility-focused service or aiming to be more of a lifestyle platform integrating various financial aspects of our users' lives?

Why it matters: This influences whether we prioritize functional features or those that create a more comprehensive ecosystem. Expected answer: Moving towards a lifestyle platform to differentiate from competitors. Impact on approach: Would lean towards features that support a broader financial ecosystem and user engagement.

• Regarding our resource constraints, do we have any significant limitations in terms of development capacity or go-to-market resources that might impact our ability to execute on either of these features?

Why it matters: Resource availability affects the scope and timeline of feature implementation. Expected answer: Limited engineering resources but strong marketing capabilities. Impact on approach: Would consider the technical complexity and marketing potential of each feature.

Based on these strategic considerations, let's move forward with the following assumptions:

1. We're in a growth phase, focusing on both user acquisition and engagement.
2. Our target audience is primarily young professionals, but we're expanding to a broader demographic.
3. We're evolving towards a lifestyle platform to differentiate in the market.
4. We have some engineering constraints but strong marketing capabilities.

These assumptions will guide our approach as we analyze the market and evaluate our options.