Student Success by DesignA practitioner’s guide to theory, data, and AI in student success

5.8 · Technology, Data, and AI Applications

From theory to enterprise architecture

Each theory names a mechanism. Each mechanism depends on specific campus capabilities, and those capabilities run on specific systems.

Short shows the summary, takeaway, and questions.

Student success plans usually start with a tool. Starting with the mechanism instead makes it clearer what the institution needs to be able to do, which offices own that work, and which systems and data it relies on. The Campus Enterprise Model, built on the CAUDIT Higher Education Reference Models (HERM), gives a shared map of those capabilities and systems.

Integration (Tinto)
Capabilities: advising, academic support, student engagement. Systems: student advising platform, LMS, CRM. Data: enrollment, course activity, advising notes.
Involvement (Astin)
Capabilities: co-curricular engagement, learning delivery. Systems: LMS, engagement and event platforms, campus recreation. Data: participation and activity records.
Belonging (Strayhorn)
Capabilities: student wellbeing, community and engagement, outreach. Systems: CRM, student mobile app, survey tools. Data: survey responses, contact history.
Validation (Rendón)
Capabilities: advising, teaching and learning, student communications. Systems: advising platform, CRM, LMS messaging. Data: outreach records and follow-up.
Basic needs
Capabilities: financial aid, student health and counseling, emergency support. Systems: financial aid system, health records, case management. Data: aid, need, and referral records, often highly sensitive.
Purpose and goal commitment
Capabilities: career services, curriculum and program planning. Systems: career services platform, degree planning and audit. Data: program maps, internships, outcomes.

Implications for practice

  • Map each student success initiative to the capabilities it depends on before choosing technology.
  • Use the capability map to find where two offices run overlapping tools for the same mechanism.

In the Campus Enterprise Model

Where this work sits in campus systems, capabilities, and data.