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

D2L

What factors are contributing to the sudden 30% increase in support tickets related to D2L's Brightspace Portfolio tool in the last two weeks?

Prepared by NextSprints

15 mins
Report an error
Problem-Solving Data Analysis Product Strategy EdTech SaaS Higher Education User Experience Root Cause Analysis Edtech Product Troubleshooting Support Optimization
Product Management Root Cause Analysis Question: Investigating EdTech support ticket increase

Introduction

The sudden 30% increase in support tickets related to D2L's Brightspace Portfolio tool over the past two weeks is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term fixes and long-term implications for the product.

I'll approach this problem by first clarifying the context, then ruling out external factors before diving deep into the product itself. We'll break down the metric, gather relevant data, form hypotheses, and conduct a thorough root cause analysis. Finally, we'll develop a comprehensive plan to validate our findings and implement solutions.

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 update. Has there been any change to the Brightspace Portfolio tool in the last month?

Why it matters: Recent changes often correlate with support ticket spikes. Expected answer: Yes, a minor update was released three weeks ago. Impact on approach: If confirmed, we'd focus on the update's features and potential bugs.

  • Considering user segments, I'm curious about the distribution of these tickets. Are they coming from a specific user group, like new users or a particular institution?

Why it matters: Identifying affected segments helps narrow down potential causes. Expected answer: The increase is primarily from existing users across multiple institutions. Impact on approach: This would suggest a systemic issue rather than onboarding or institution-specific problems.

  • Given the nature of portfolio tools, I'm wondering about the academic calendar. Are we in a period of increased portfolio submissions or evaluations?

Why it matters: Usage patterns tied to academic cycles could explain increased support needs. Expected answer: It's mid-semester for most institutions using Brightspace. Impact on approach: If confirmed, we'd investigate whether the tool is struggling under higher load.

  • Thinking about support ticket categorization, I'm curious about the nature of these tickets. What are the top three issues being reported?

Why it matters: The types of issues reported can point directly to root causes. Expected answer: Slow loading times, missing files, and difficulty sharing portfolios. Impact on approach: This would guide our technical investigation and user journey analysis.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025