Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Credible

How can we explain the unexpected 25% increase in customer support inquiries related to Credible's mortgage marketplace in the last two weeks?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem Solving User Journey Mapping Fintech Mortgage Lending Personal Finance User Experience Fintech Root Cause Analysis Customer Support Mortgage Industry
Product Management Root Cause Analysis Question: Investigating spike in mortgage marketplace support inquiries

Introduction

The unexpected 25% increase in customer support inquiries related to Credible's mortgage marketplace over the past two weeks signals a significant shift in user experience. To address this issue, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both immediate and long-term implications for our product and users.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Given the sudden spike, I'm wondering about recent changes. Have there been any updates to the mortgage marketplace in the last month?

Why it matters: Recent changes often correlate with support inquiries. Expected answer: Yes, a new feature was launched. Impact on approach: If true, we'd focus on the new feature's implementation and user education.

  • Considering user segments, are these inquiries coming from a specific demographic or loan type?

Why it matters: Helps identify if the issue is localized or widespread. Expected answer: Primarily from first-time homebuyers seeking fixed-rate mortgages. Impact on approach: We'd tailor our investigation to this user segment and loan type.

  • Thinking about external factors, has there been any significant change in interest rates or lending policies recently?

Why it matters: External market changes can drive increased user confusion. Expected answer: Yes, the Federal Reserve announced a rate hike last week. Impact on approach: We'd examine how we communicate market changes to users.

  • Reflecting on support capacity, has there been any change in our customer support team or processes?

Why it matters: Internal changes could affect how inquiries are logged or handled. Expected answer: No significant changes to the support team or processes. Impact on approach: We'd focus more on product-related issues rather than support team capacity.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025