Frequently Asked Questions

A Student Learning Outcome is a statement of what students will be able to do as a result of instruction: a specific, observable skill or competency demonstrated through a product or behavior. An SLO is written with an observable, measurable verb, so students can analyze a text, design an experiment, or repair a circuit, rather than merely “understand” or “appreciate” something that cannot be observed.

A grade compresses everything that happened in a course, attendance, participation, deadlines, extra credit, into one letter or number. SLO assessment asks a narrower and more useful question: can the student demonstrate this specific skill? A grade of B+ cannot tell you whether a student is stronger in theory or in practice; assessment of a well-written outcome can. The two work best together, with SLO evidence collected through the same assignments faculty already grade.

Because observation is the only access anyone has to another person's learning. Faculty cannot see what is stored in a student's mind; they can only observe what students demonstrate: every answer, every essay, every presentation is a demonstration of skill. Focusing on observable behavior keeps assessment honest, grounded in direct evidence rather than inferred from indirect measures like attendance, persistence, or engagement.

Objectives describe the smaller steps of instruction along the way; outcomes describe the destination, what students can do when instruction is complete. A course may pursue many objectives during the semester, but its outcomes are the handful of demonstrable skills and competencies that remain with the student afterward.

The same idea at larger scales. Program Learning Outcomes (PLOs) describe what students can do upon completing a program of study, and Institutional Learning Outcomes (ILOs) describe what any graduate of the institution can do. Well-designed course SLOs align upward: demonstrating course outcomes contributes evidence toward program outcomes, which in turn support institutional ones.

There is no single rule, but fewer and sharper beats many and vague. A small number of outcomes, commonly two to four per course, keeps assessment focused on the competencies that define the course, and keeps the evidence meaningful rather than bureaucratic. Faculty, as the subject experts, decide which competencies matter most.

Direct evidence: student performances, products, demonstrations, projects, portfolios, essays, presentations, anything a student actually does that can be evaluated against clear criteria, typically with a rubric. Indirect measures such as satisfaction surveys, attendance, or course completion can add context, but they do not show what a student can do.

It should not be, and when it feels that way, the design is the problem. The assignments faculty already grade are demonstrations of student skill; well-designed SLO assessment captures that evidence as a byproduct of grading rather than a separate task. Tools like rubrics built into the learning management system can record outcome data at the moment of grading, with no second pass required.

Using what the evidence shows. After assessing an outcome, faculty and programs ask what the results suggest about teaching, curriculum, or support, make a change, and then look again. Assessment that ends with a filed report has not closed anything; the loop closes when results influence what happens next in the classroom.

Start with the Guide to SLO Assessment, a step-by-step foundation from writing outcome statements to using results. Try the SLO App Creator to build an assessment instrument, join a community of practice to compare notes with colleagues, and drop into a Friday SLO Talk to see how others do this work.