AI-Driven Student Services and Prescriptive Pathways at UCLA Anderson School of Management
ucla · Education · 2024 · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.4 (schema v2)
Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.
Problem
Domain: MBA student services and career-path guidance
UCLA Anderson needed to give MBA students personalized, prescriptive guidance across courses, internships, clubs, and career goals while protecting sensitive student data.
Constraints:
- sensitive student records
- disparate campus systems
- institutional security review
- student-facing adoption
Architecture
UCLA Anderson and Kyndryl consolidated disparate student, career, club, and course data into a security-aligned AI application that recommends personalized MBA pathways while keeping institutional policy constraints explicit.
Diagram confidence: reconstructed (reconstructed from prose).
flowchart LR student-record-data["Student record data"] career-placement-data["Career placement data"] club-and-course-catalogs["Club and course catalogs"] security-aligned-environment["Security-aligned environment"] prescriptive-pathway-application["Prescriptive pathway application"] agentic-ai-framework["Agentic AI framework"] student-facing-guidance["Student-facing guidance"] student-record-data --> prescriptive-pathway-application career-placement-data --> prescriptive-pathway-application club-and-course-catalogs --> prescriptive-pathway-application security-aligned-environment --> prescriptive-pathway-application agentic-ai-framework --> prescriptive-pathway-application prescriptive-pathway-application --> student-facing-guidance
Components
| Component | Role | Interacts with |
|---|---|---|
Student record data |
Provides academic and profile context for personalized pathways. | Prescriptive pathway application |
Career placement data |
Connects student goals to employers, internships, and outcomes. | Prescriptive pathway application |
Club and course catalogs |
Supply recommendations for activities and coursework. | Prescriptive pathway application |
Security-aligned environment |
Mirrors UC information security policy for student-data handling. | Prescriptive pathway application |
Prescriptive pathway application |
Synthesizes records, career data, clubs, and courses into recommendations. | Student-facing guidance |
Agentic AI framework |
Supports future agent-to-agent handoffs and workflow orchestration. | Prescriptive pathway application |
Student-facing guidance |
Presents courses, companies, internships, and club recommendations. | Prescriptive pathway application |
Data flow
The pathway system pulls from student records, career placement, clubs, and course catalog data before generating career-aligned recommendations.
Why this architecture
The environment was designed around UC information-security policy because sensitive student data made this more than a casual AI pilot.
Models used: Kyndryl agentic AI framework
Scale
- The broader modernization effort included digitizing more than 2 million paper records as a foundation for AI-driven student services.“at UCLA, which we'll dig into deeper during our fireside chat, we have worked on digitizing over 2 million paper records and laying the foundation for AI-driven student services.”transcript, stated
- The AI-services foundation included digitizing over 2 million paper records.“at UCLA, which we'll dig into deeper during our fireside chat, we have worked on digitizing over 2 million paper records and laying the foundation for AI-driven student services.”transcript, stated
Alternatives considered (roads not taken)
Shipping quickly before architecture and policy review
Rejected because: The team spent substantial time getting the architecture right, even though the speaker later wished they had failed faster.
Point solution over one campus dataset
Rejected because: The system integrates student records, career placement, clubs, and course catalogs instead of relying on one data source.
Security review after product build
Rejected because: The environment mirrored UC information-security policy so student-data controls would pass audit.
Patterns
rag-retrieval (student-services)
The application combines student records, career placement, clubs, and course catalog data to recommend a personalized roadmap.
safety-policy-enforcement (governance)
The environment was architected to mirror UC information-security policy so sensitive student-data use could pass review.
Tradeoffs
How quickly to ship a student-data AI application.
Chose security-first architecture and consolidation over faster release with less governed data.
Rationale: The team later wished they had failed faster, but the chosen path reflected the sensitivity of student records and campus audit requirements.
Gotchas (what bit them)
Sensitive student data made the project harder than a quick AI pilot.
Root cause: The application required third-party risk management, privacy review, and data consolidation across multiple systems.
Resolution: Mirror UC security policy and build the application around governed student-data access.
Evaluation
The case reports delivery timeline, production-use-case progression, and student-pathway utility rather than a formal accuracy benchmark.
Metrics: 2 million paper records digitized · first two production use cases · approximately eight-month project timeline
Outcomes
- The application provides prescriptive student roadmaps tied to target roles and companies.
- UCLA established early production AI use cases while satisfying student-data governance requirements.
Education/government conference case; outcomes are qualitative and client-reported.