What factors led to the 20% drop in student completion rates for Lambda School's Web Development track last quarter?

Introduction

The 20% drop in student completion rates for Lambda School's Web Development track last quarter is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for Lambda School's program effectiveness and student success.

I'll approach this problem by first clarifying key details, ruling out external factors, and then diving deep into the product, user journey, and metrics. From there, I'll form data-driven hypotheses, conduct root cause analysis, and propose validation methods and solutions.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might be seasonal factors at play. Has this 20% drop been compared to the same quarter in previous years?

Why it matters: Seasonal trends could explain fluctuations in completion rates. Expected answer: No significant seasonal patterns observed in previous years. Impact on approach: If seasonal, we'd focus on adapting the program to accommodate these patterns.

• Considering the specificity of the Web Development track, I'm curious about other tracks. Have completion rates changed in other Lambda School programs during the same period?

Why it matters: Helps determine if this is a Web Development-specific issue or a broader trend. Expected answer: Other tracks maintained stable completion rates. Impact on approach: If isolated to Web Development, we'd focus on curriculum and support specific to this track.

• Given the substantial drop, I'm wondering about any recent changes to the program. Were there any significant updates to the Web Development curriculum or teaching methods in the preceding quarter?

Why it matters: Recent changes could directly impact student performance and completion rates. Expected answer: A new project-based learning module was introduced. Impact on approach: We'd evaluate the effectiveness of this new module and its implementation.

• Thinking about student demographics, has there been any shift in the profile of students enrolling in the Web Development track?

Why it matters: Changes in student demographics could affect overall completion rates. Expected answer: No significant changes in student demographics noted. Impact on approach: If demographics shifted, we'd tailor support systems to meet the needs of the new student profile.

• Considering the importance of accurate data, I'm curious about our measurement methods. Has there been any change in how completion rates are calculated or tracked?

Why it matters: Ensures we're comparing apples to apples and not facing a data anomaly. Expected answer: No changes in calculation methods or tracking systems. Impact on approach: If measurement changes occurred, we'd need to recalibrate our analysis based on consistent metrics.