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 .

What factors are contributing to the increased customer support ticket volume for Tyler Technologies's EnerGov permitting software in the last 30 days?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Data Analysis Strategic Thinking Government Software Permitting Systems SaaS Root Cause Analysis Customer Support Product Management Software Troubleshooting Government Technology
Product Management Root Cause Analysis Question: Investigating increased support tickets for government permitting software

Introduction

The increased customer support ticket volume for Tyler Technologies's EnerGov permitting software in the last 30 days is a critical issue that requires immediate attention. To address this problem, 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 software update. Has there been any significant changes or updates to the EnerGov software in the past 30-45 days?

Why it matters: Recent changes often correlate with increased support tickets. Expected answer: Yes, there was a major update. Impact on approach: If yes, we'd focus on the update's features and potential bugs.

  • Considering user segments, I'm curious about the distribution of tickets. Are we seeing an 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: Increase is primarily in one user segment. Impact on approach: If segment-specific, we'd dive deeper into that segment's unique needs and usage patterns.

  • Thinking about the nature of the tickets, I'm wondering about the content. What are the top 3 issues being reported in these support tickets?

Why it matters: Identifies common themes or potential systemic issues. Expected answer: Specific feature malfunctions, UI confusion, and integration problems. Impact on approach: Would guide our focus on particular areas of the software for investigation.

  • Considering external factors, I'm curious about any recent regulatory changes. Have there been any new government regulations or changes in permitting processes that might affect our users?

Why it matters: External changes can drive increased support needs. Expected answer: No significant regulatory changes. Impact on approach: If yes, we'd need to consider how to better support users through these changes.

  • Thinking about system performance, I'm wondering about any backend issues. Have there been any server outages, slow response times, or other technical issues reported in the last 30 days?

Why it matters: Technical issues often lead to increased support tickets. Expected answer: Some intermittent server slowdowns reported. Impact on approach: If yes, we'd prioritize investigating and resolving these technical issues.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025