It’s the 8th week of the semester, and we’re pulling together a mid-term evaluation of the Early Alert system. Again, keep in mind that this is a pilot project and that we’re piloting the software and the process. I am going to provide my impressions of what I’ve seen and heard, and what Bobbe and I have discussed. But what is critical is your input. We really need to get your thoughts and impressions so that as we move forward with this initiative, we are making it work for EVERYONE. With that said, here are some Week-8 notes that I’d like to highlight:
One: From what I’ve seen, the software is working. It has some glitches, but it’s a new piece of software, and we knew that we would be massaging it along the way (see list of tweaks below). A number of things that need to be updated are only relevant on the administrative side of the software…I’m very keen on hearing comments from your side (the input side) of the software.
Two: We’ve had some success with the process, but we have a ways to go. Particularly if we’re going to roll this out to the whole college. This is the piece that will probably need the most attention. I’m adding comments on this below.
Before analyzing product and process, let’s look at some numbers:
- 40 students in EA cohort group
- 39 faculty
- 120 reports submitted (all faculty were required to submit a report on each of their cohort students in week 4)
- 79 reports indicated that no intervention was required.
- 33 required intervention
- 6 had been resolved
- Primary issues reported: Grades (23), Other problem (15), Test Taking Skills (8), Participation (7), Excessive Absences (6), & Preparation (6).
Here are my reviews on the Process and the Product:
- Communication: With faculty to use the system needs to be strengthened. There were instances where faculty (part-time) did not know they were to use the system
- Communication: Between Bobbe and those who will intervene. Need to ensure that those who will be intervening understand the process and have access to the administrative version of the software.
- Communication: Between those intervening and Bobbe. The feedback loop needs to be solidified.
- Communication: Between Bobbe & students. There are about 6 cases where emailing and calling have not worked when trying to connect with student.
- Whatever is written in the “proposed intervention” box needs to be specific. It can’t be an action point, such as “emailed student”
- When prompted to enter a student number to look up a student, only that student’s records should be viewable (currently, it’s a mixed bag of what appears)
- More space for actual interventions; perhaps set it up so that interventions are listed in chronological order
- A way of indicating (in the email announcement) that the attached alert is: a notice, a call to action, an action completed, etc… This would allow Bobbe to focus more on those that need attention.
These are just a few of the key items.
Again, we are looking for your feedback. Let us know what you think about the process and the product by posting a comment below.