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

Clever Devices

What factors are contributing to the 30% increase in customer support tickets related to Clever Devices's BusTime real-time passenger information system in the last quarter?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Customer Experience Public Transportation Smart Cities IoT Product Improvement Data Analysis Root Cause Analysis Customer Support Public Transit
Product Management Root Cause Analysis Question: Investigating increased support tickets for a real-time transit information system

Introduction

The recent 30% increase in customer support tickets related to Clever Devices's BusTime real-time passenger information system is a critical issue that demands immediate attention. This surge in support requests not only impacts customer satisfaction but also strains our support resources and potentially undermines the core value proposition of our product. To address this challenge, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term 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)

  • Looking at the timing, I'm thinking there might be a recent system update. Has there been any significant changes or updates to the BusTime system in the last quarter?

Why it matters: System changes often correlate with increased support tickets. Expected answer: Yes, a major update was rolled out. Impact on approach: If confirmed, we'd focus on post-update issues and rollback considerations.

  • Considering user segments, I'm curious about the distribution of these tickets. Are we seeing an even increase across all user types, or is it concentrated in specific segments?

Why it matters: Helps identify if the issue is universal or segment-specific. Expected answer: The increase is primarily from new users. Impact on approach: If true, we'd focus on onboarding and user education strategies.

  • Thinking about the nature of support tickets, I'm wondering about the most common issues reported. What are the top 3 categories of problems users are experiencing?

Why it matters: Identifies specific areas of the product causing issues. Expected answer: App crashes, inaccurate arrival times, and login problems. Impact on approach: Would guide our technical investigation and prioritization.

  • Considering external factors, has there been any significant change in the number of transit agencies or routes covered by BusTime in the last quarter?

Why it matters: Rapid expansion could explain increased support needs. Expected answer: Yes, we've added 20% more agencies. Impact on approach: If true, we'd examine scalability and onboarding processes.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025