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

Poshmark

Why has Poshmark's "Make an Offer" feature seen a 15% decrease in usage over the past month?

Prepared by NextSprints

12 mins
Report an error
Data Analysis Problem-Solving User Experience E-commerce Fashion Resale Marketplace User Engagement E-Commerce Data Analysis Root Cause Analysis Feature Optimization
Product Management Root Cause Analysis Question: Investigating decline in Poshmark's 'Make an Offer' feature usage

Introduction

Poshmark's "Make an Offer" feature has experienced a 15% decrease in usage over the past month, raising concerns about user engagement and potential revenue impact. This analysis will systematically investigate the root cause, considering both internal and external factors that could be influencing this metric. We'll follow a structured approach to identify, validate, and address the underlying issues while keeping in mind both immediate fixes and long-term strategic implications.

Framework overview

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

Step 1

Clarifying Questions (3 minutes)

  • I'm noticing the timing of this decrease. Has there been any recent platform-wide update or change in the last 1-2 months?

Why it matters: Recent changes could directly impact feature usage. Expected answer: Yes, a UI refresh was implemented 6 weeks ago. Impact on approach: If confirmed, we'd focus on UI/UX-related hypotheses.

  • Considering user segments, has the decrease been uniform across all user types, or is it more pronounced in certain groups?

Why it matters: Helps identify if the issue is global or segment-specific. Expected answer: The decrease is more significant among new users. Impact on approach: We'd investigate onboarding and new user experience.

  • Looking at the broader context, have other related features like "Buy Now" seen any changes in usage?

Why it matters: Indicates whether this is an isolated issue or part of a larger trend. Expected answer: "Buy Now" usage has remained stable. Impact on approach: We'd focus specifically on the "Make an Offer" feature and its unique attributes.

  • Regarding data integrity, has there been any change in how we track or define "Make an Offer" usage in the last month?

Why it matters: Ensures we're not dealing with a data anomaly rather than a real issue. Expected answer: No changes in tracking or definition. Impact on approach: We'd proceed with confidence in the data's accuracy.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025