Signals
Interest, history, and course context
Oracle · Product and program delivery
A student course recommendation experience designed around relevance, trust, and a difficult cold start.
THE BRIEF
Students needed relevant course paths before the system had enough personal history to learn from.
AT A GLANCE
I designed and launched a course recommendation and personalization system that helped students discover relevant courses during catalog browsing and enrollment checkout. The work addressed weak discovery and invalid course choices that created frustration and drop-off.
I led product definition and cross-functional delivery across data science, machine learning, architecture, user experience, security, legal, and university stakeholders. The product combined recommendation ranking with course prerequisites and repeat-avoidance rules so relevance did not come at the cost of an unusable recommendation.
Students browsing a large course catalog were not consistently finding relevant next steps. Low satisfaction and drop-offs affected enrollment, while universities needed more value from the platform and better visibility into recommendation performance.
The product goal was larger than showing a ranked list. Students needed a useful path through the catalog, advisors needed enough context to support those choices, and the platform needed measurable evidence that recommendations were improving the enrollment experience.
I treated drop-offs after recommendation-driven enrollment as a counter-signal. Higher clicks alone would not prove value if students abandoned the course later, so the product scorecard connected discovery, selection, enrollment, satisfaction, and retention.
As Principal Product Manager, I shaped the goals, requirements, roadmap, and evaluation approach across academic product, data science, machine learning, architecture, UX, legal, security, and university stakeholders. I turned a broad AI opportunity into a staged system with product and program gates.
We started with trust and precision. The initial experience showed fewer, higher-confidence recommendations rather than maximizing the number of items. For new students and sparse histories, we used safe rules and richer signals rather than waiting for a perfect behavioral history. As the data foundation improved, the design could use richer model signals without losing the fallback path.
The work covered data readiness, model design, offline evaluation, human review, online evaluation, telemetry, and release gates. I partnered with data science and ML to improve offline precision by 50% and recall by 30%. We used A/B testing and interleaving to compare model behavior and improve relevance.
Human review and responsible AI checks were part of the lifecycle, with privacy and compliance treated as product requirements. The recommendation flow also enforced practical guardrails: eligibility prerequisites, no repeat courses, a rule-based fallback when model output was unavailable, and monitoring for enrollment behavior and model drift. Those controls made the user experience safer while giving the delivery team clear release criteria.
The recommendation and personalization system increased engagement by 35%, reduced drop-offs by 50%, and increased conversion by 15%. Model relevance improved by 20% through online evaluation. The work also gave administrators a way to understand recommendation performance and gave the product a stronger value story for university customers.
The lesson is that AI product management is a system of decisions. A useful recommendation is only one part of the outcome; the experience must also be explainable enough to trust, safe enough to deploy, measurable enough to improve, and economical enough to support.
DECISION CONTEXT
This is a retrospective portfolio brief, not an original Oracle project artifact.
Build trust first by prioritizing precision in the initial recommendation experience while retaining coverage as a monitored concern. A small set of strong recommendations is more useful than a larger set that creates doubt.
Precision improves confidence that a recommended course fits; coverage and recall help ensure that eligible students still receive useful options. I worked with data science to make this tradeoff explicit instead of treating a single model score as the outcome. Offline evaluation included precision, recall, ranking quality, and hit rate. Human review focused on relevance, usefulness, and trust. Online measurement considered interaction with recommendations, enrollment, course-page time, drop-off, and latency.
New students and courses have limited behavioral history. The approach used available student and course attributes, including academic context and course metadata, to improve cold-start recommendations. Separate rules enforced prerequisite chains and avoided repeated recommendations. If the model path was unavailable, rule-based recommendations provided a fallback.
The operating approach included versioned data, privacy and compliance review, staged release, monitoring, and feedback loops. A later model should be compared through controlled evaluation before broader rollout. The evaluation details explain the decision framework that supported the experience.
PRODUCT SYSTEM
Interest, history, and course context
Prerequisites and fallback rules
Relevant paths, evaluated in use
THE OUTCOME
more engagement
fewer drop-offs
higher conversion
WHAT STAYED WITH ME
“For AI products, a model metric is only useful when the customer can feel the difference.”
MORE TO EXPLORE
See all work ↗