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

Everlaw

Why has Everlaw's StoryBuilder feature seen a 30% drop in user engagement over the past month?

Prepared by NextSprints

15 mins
Report an error
Data Analysis Problem Solving User Experience Legal Technology SaaS Enterprise Software User Engagement Product Analytics Root Cause Analysis UI/UX Legal Tech
Product Management Root Cause Analysis Question: Investigating sudden drop in legal software feature engagement

Introduction

The recent 30% drop in user engagement for Everlaw's StoryBuilder feature is a critical issue that demands immediate attention and a thorough root cause analysis. As we delve into this problem, we'll employ a systematic approach to identify, validate, and address the underlying factors contributing to this significant decline in usage.

Framework overview

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

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking there might have been a recent product update. Has there been any significant change to StoryBuilder's functionality or user interface in the past month?

Why it matters: Recent changes could directly impact user behavior. Expected answer: Yes, there was a UI refresh. Impact on approach: If confirmed, we'd focus on UI/UX issues and user adaptation.

  • Considering user segments, I'm wondering if this drop is uniform across all user types. Are we seeing a more pronounced decrease in engagement among any particular user group, such as new users versus power users?

Why it matters: Helps identify if the issue is widespread or specific to certain users. Expected answer: The drop is more significant among newer users. Impact on approach: We'd prioritize onboarding and user education strategies.

  • Given the nature of legal work, I'm curious about seasonality. Is there typically any fluctuation in StoryBuilder usage during this time of year due to court schedules or other legal industry patterns?

Why it matters: Helps distinguish between normal seasonal variations and actual problems. Expected answer: No significant seasonal patterns in previous years. Impact on approach: We'd focus on recent changes rather than cyclical factors.

  • Thinking about the broader ecosystem, have there been any changes in related features or integrations that might indirectly affect StoryBuilder usage?

Why it matters: Interconnected features can have cascading effects on user behavior. Expected answer: Some updates to document review features were implemented. Impact on approach: We'd investigate potential workflow disruptions across the platform.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Mar 29, 2025