Decide what to cut from a delayed learning platform launch

Problem Statement Description

You are the PM for a new learning platform aimed at privacy-conscious users who want to enroll in courses, track progress, complete lessons, and receive proof of completion without feeling over-profiled or exposed. The launch is running late, and the team must reduce scope while still shipping a credible first version that supports course completion and preserves user trust.

The interview asks you to make an execution decision: determine what to cut, what to keep, and how to manage the launch plan under time pressure. You should frame the product workflow, identify the minimum experience needed for learners and internal teams, and reason through trade-offs between speed, quality, privacy, compliance, and completion outcomes.

Assume there are multiple competing features across onboarding, course discovery, lesson playback, progress tracking, assessments, certificates, personalization, analytics, notifications, admin tooling, and privacy controls. Engineering, design, legal/privacy, content operations, support, and leadership all have dependencies, and the launch date matters for business, partner, or seasonal reasons.

The experience should consider:

- The core learner journey from account creation to course completion, including where delays or missing features would block progress.

- Which features are launch-critical versus deferrable, especially for privacy-conscious users.

- Owners, dependencies, sequencing, and decision-making across product, engineering, design, legal, data, content, and support.

- Go/no-go criteria for launch readiness, including privacy, reliability, accessibility, and learner completion safeguards.

- Risks created by cutting scope, such as reduced trust, lower completion, support burden, or inability to measure outcomes.

- Rollback, fallback, or phased-launch options if critical systems are not ready.

- Communication plans for internal stakeholders, beta users, partners, and support teams.

- Post-launch monitoring needed to confirm users can start, continue, and complete learning successfully.

Your goal is to present a clear operating plan for making scope cuts on a delayed launch while protecting the essential learning experience, maintaining privacy expectations, and enabling the team to ship responsibly with measurable completion outcomes.