# data[].attributes.body
Initial needs assessment to determine....

# data[].attributes.body
Review website analytics to learn about how page visitors are landing on that page as well as click through paths

# data[].attributes.headline
Completion (number of students who completed the course vs number of students who started it)

# data[].attributes.subject
Completion (number of students who completed the course vs number of students who started it)

# data[].attributes.body
Who was invited/How many attended/how many completed the series? ratio of intended engagement versus follow up.

# data[].attributes.body
ensure that the course learning outcomes relate to practice

# data[].attributes.body
Monitor questions being asked throughout course to ensure that course material is effective

# data[].attributes.body
some sort of pre-assessment to understand who is attending and their knowledge

# data[].attributes.headline
Written reflection documenting their journey

# data[].attributes.subject
Written reflection documenting their journey

# data[].attributes.headline
Grades (compared to historical average for the same course)

# data[].attributes.subject
Grades (compared to historical average for the same course)

# data[].attributes.body
Focus group - test users

# data[].attributes.body
post-assessment to see what the attendees thought of the session

# data[].attributes.body
Data on how long to navigate throughout website

# data[].attributes.headline
Time it takes to complete actions/click on buttons

# data[].attributes.subject
Time it takes to complete actions/click on buttons

# data[].attributes.body
expectations outlined at the beginning, needs assessment for participants. Reflection at the end if your needs were met.

# data[].attributes.body
Cost to benefits ratio. does it use time/money more effectively than what exists? What is the cost of not changing? (loss of attendance from a population not being supported/not applying)

# data[].attributes.headline
Mid point check in (what questions students have and what we'll do about it for the rest of the course)

# data[].attributes.subject
Mid point check in (what questions students have and what we'll do about it for the rest of the course)

# data[].attributes.body
use scenario based questions to assess how much is being internalized and if everyone is taking the same information from the workshops.

# data[].attributes.body
Look at registration numbers. Are people interested? Are people interested more or less in future training days?

# data[].attributes.headline
What are two things you've learned today

# data[].attributes.subject
What are two things you've learned today

# data[].attributes.body
Informal open-ended emails or group check ins with mentors to see how things are going.

# data[].attributes.body
this would be a good follow up for any workshops or programs

# data[].attributes.headline
"Two roses and a thorn": two positive things and one negative thing

# data[].attributes.subject
"Two roses and a thorn": two positive things and one negative thing

# data[].attributes.body
"mandatory" reflections at end of program on experience

# data[].attributes.body
Observe students as the go from start to finish through an administrative process, and determine if the outcome was as expected. Where did the process fail? Do students know what to do or where to go if there are ongoing issues?

# data[].attributes.body
data on how often logging in and for how long

# data[].attributes.body
if mentors would like to do this again, this is a good sign of the efficacy of the program

# data[].attributes.body
Encourage dialogue with online discussion forum for questions. Are there questions not being answered effectively in the module?

# data[].attributes.body
I liked Kathleen's example of eye tracking during its development.

# data[].attributes.body
track access to video to ensure all can access it, and ensure it is still relevent.

# data[].attributes.body
for online, how many people have accessed it, downloads.

# data[].attributes.body
Have UX professional look it over

# data[].attributes.headline
Ask for feedback: what's clear and what's not, suggested edits

# data[].attributes.subject
Ask for feedback: what's clear and what's not, suggested edits

# data[].attributes.body
Assessment throughout the study: checkpoints with students structured as interviews

# data[].attributes.body
Generated research report to share findings and assess the topic that was being studied

# data[].attributes.body
Focus group using the resources - can assess using likert scale comfortability/knowledge before and after using resource document

# data[].attributes.headline
surveying students before and after (assess their learning before the session and then again after to determine the change)

# data[].attributes.subject
surveying students before and after (assess their learning before the session and then again after to determine the change)

# data[].attributes.body
Ask "Communications" for the search history to see what keywords users are searching for

# data[].attributes.body
Data on most searched terms

# data[].attributes.body
what were you trying to illuminate (the problem) with your assessment and does the data prove it out?

# data[].attributes.headline
creation of a how to document for institutional memory by asking staff what resources to include, what would be helpful.

# data[].attributes.subject
creation of a how to document for institutional memory by asking staff what resources to include, what would be helpful.

# data[].attributes.body
reviewing the comment section - prompting discussion in the comments

# data[].attributes.body
Compare/benchmark best practices on what other institutions are doing.

# data[].attributes.body
encouraging feedback throughout the video

# data[].attributes.body
This piece can be very difficult depending on how the backend system is set up - My limited experience with the backend data for D2L revealed that it could not differentiate between a view or a download etc. So if you want to do this, you need to incorporate some user testing with dummy accounts to see what the output actually looks like. The same goes with email open rates etc. It's worth it to take the time to ensure you can read the data and know exactly what each action looks like in the data export, or else you'll be really ticked down the road.

# data[].attributes.body
After each session, there is a formative feedback piece they need to hand in before they can leave (e.g. most beneficial thing from today)

# data[].attributes.body
How will this come back to retention and helping students?

# data[].attributes.body
On a scale from 1-5... (distributed before a person joins the platform, and then once they are "done")

# data[].attributes.headline
CACUSS has a March meet up (Mar. 19) for how to assess Student Peer Programs as a community of practice ( join us to discuss program evaluation, exchange tips and best practices for conducting assessments and surveys, or seek support for your questions on this topic.) See meeting details below.

# data[].attributes.subject
CACUSS has a March meet up (Mar. 19) for how to assess Student Peer Programs as a community of practice ( join us to discuss program evaluation, exchange tips and best practices for conducting assessments and surveys, or seek support for your questions on this topic.) See meeting details below.

# data[].attributes.body
Date: Wednesday, March 19, 2025

Start Time: 9:00 am PST / 10:00 am MTN / 11:00 am CTL/ 12:00 pm EST / 1:00 pm ATL

Please register in advance here or copy and paste this link: https://us06web.zoom.us/meeting/register/ZaAF2qVURSmlmagXZo9XNA

Feel free to reach out if you have any questions by emailing Tiffany and Marisa at peer@cacuss.ca.