How can NerdWallet balance showing more credit card offers versus simplifying user choice?

Introduction

Balancing the number of credit card offers shown on NerdWallet with the need to simplify user choice is a critical trade-off that impacts both user experience and business outcomes. This scenario touches on core aspects of product strategy, user behavior, and revenue generation. I'll approach this analysis by examining the current product landscape, identifying key metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming NerdWallet's primary revenue comes from credit card affiliate partnerships. Could you confirm if this is still the case, or if there have been significant changes to the business model?

Why it matters: Impacts the weight we give to increasing offer visibility vs. user experience. Expected answer: Yes, credit card partnerships are still a major revenue source. Impact on approach: If confirmed, we'd need to carefully balance revenue potential with user satisfaction.

• User Impact: Based on our user data, I'm thinking we might have distinct user segments with varying levels of financial literacy. Can you share insights on how our user base breaks down in terms of financial expertise and decision-making confidence?

Why it matters: Helps tailor the solution to different user needs and preferences. Expected answer: Mix of novice and experienced users, with a growing segment of millennials. Impact on approach: Would inform personalization strategies and UI complexity levels.

• Technical Feasibility: I'm considering the potential for dynamic offer presentation. What's our current capability for real-time personalization of credit card offers based on user behavior and preferences?

Why it matters: Determines the sophistication of solutions we can implement. Expected answer: Basic personalization in place, with plans for more advanced systems. Impact on approach: Would influence the complexity of proposed solutions and timeline.

• Resource Allocation: Given the potential impact on core revenue, I'm assuming this project would be high priority. Can you give me an idea of the resources (engineering, design, data science) we could allocate to this initiative?

Why it matters: Helps scope the solution and implementation timeline. Expected answer: Moderate to high resource availability due to strategic importance. Impact on approach: Would determine the scale and complexity of proposed changes.

• Timeline Pressure: Considering market dynamics, I'm wondering about the urgency of this initiative. Are we facing any immediate competitive pressures or upcoming seasonal peaks (like holiday spending) that would influence our timeline?

Why it matters: Affects the balance between thorough testing and speed to market. Expected answer: Moderate urgency, aiming for implementation before Q4 shopping season. Impact on approach: Would influence the depth of testing and phased rollout strategy.