Using Data to Improve Student Retention: More Questions than Answers?

March 14th, 2012 by Sharon

The “Issues around Using Data to Improve Student Retention” session at the JISC CETIS Conference 2012 examined some of the issues around using data to predict students at risk of failure and provide some examples of possible solutions to ensure that the institution does not fail such students.

The session was divided into five mini-sessions run by some of the JISC Relationship Management Programme projects. Here is an overview of some of the solutions being trialled by the projects and the challenges they face.

Loughborough University’s Pedestal for Progression project is using Co-Tutor to collect attendance data. Student attendance at lectures and personal tutor meetings is recorded, so it’s possible to see at a glance whether a student is turning up or if they dislike Monday mornings. The system gives automatic flags and provides a personal tutor with a red, amber or green visual of attendance (traffic lighting). As a result of introducing registers, attendance has gone up from 65.54% in 2004/5 to 70.26% in 2010/11.

Roehampton University’s fulCRM project is being run in parallel with attendance data recording within the Psychology Department. Fingerprint readers have been installed in all lecture theatres to record student attendance. Although there have been debates by staff about the “big brother” aspects of this approach, it would appear that students aree less worried as many are already used to doing this in school and in any case, fingerprint attendance seems to make students think that it (and they) really count and that someone is taking an interest in them. As the Department is fairly small, data was being kept on an Excel spreadsheet and a traffic light system used. The fulCRM project is now in the process of pulling automated data feeds from the attendance monitoring system into a student performance module.

Using a traffic light system, 18 students were identified as “red” just after the first semester (mostly male or part-time students with personal problems, or who had to travel long distances, etc) so extra support was put in for these students. In 2010, 8.3% of at risk students terminated and 19.8% didn’t have enough credits to go to Year 2. In 2011, since the traffic lighting system was put in place, this was reduced to 5.2% of at risk students terminating and 9.34% without enough credits to go on to Year 2. Of the 19 students with red flags, 16 have now gone on to Year 2 following retakes and extra support (only 3 actually left). In the past, a lot of students would have just drifted off course.

During the course of their project, the Southampton Student Dashboard at the University of Southampton project team has met with resistance from data owners, service providers, ethics authorities and faculty administrators, who cite a number of reasons why various types of data (from photos to student grades) can’t be used. They currently have a simple dashboard that shows picture of tutees, directory info, whether coursework has been handed in, and attendance. This particularly helps staff who need to let the Borders Agency know that foreign students have been seen and have attended classes. However, most information isn’t available in the rest of the University because of data protection, which is seen as protecting staff from doing any work or taking any risks.

The University of Derby’s SETL (Student Engagement Traffic Lighting) project is also using a traffic lighting approach and has been looking at some of the softer areas off engagement analytics. The team has produced a dartboard diagram showing the primary (e.g. attendance monitoring), secondary (e.g. sickness) and tertiary (e.g. student complaints) indicators of risk. They have also produced a “Withdrawal Calendar” to ascertain whether there are any key dates for withdrawal – there are. At Derby, a Progress Board meets twice a year to decide whether students are meeting the academic requirements and can progress on their course. These key times when students are likely to withdraw.

The ESCAPES (Enhancing Student Centred Administration for Placement ExperienceS) project at the University of Nottingham is exploring how an ePortfolio can enhance student engagement whilst students are on placement. Previous project work has already shown that both students on placement and staff found that ePortfolio tools, such as Mahara, have helped them to keep in touch with each other. Students have also valued the feedback aspect as it helps them to feel more motivated.

Some of the challenges, questions, and issues that have arisen during these projects can be grouped into the following areas:

Technical

  • Using the relationship management systems, such as Co-Tutor, may result in a bigger workload for staff, which may then manifest as a lack of engagement with the system.
  • There may not be any integration with other systems, such as e-mail, so staff have to copy and paste any e-mail from students into the system, or it may be difficult to exchange data between systems.
  • Not all data may be captured electronically but may still be paper-based.
  • It can be expensive to roll out pilot data monitoring solutions across the whole institution.

Human Aspects

  • Where interactions are recorded, such as personal tutor meetings, staff may feel that they have less freedom about where that interaction takes place, i.e. it may now have to take place in the tutor’s office rather than a neutral space such as a café.
  • Institutions need to make it clear to students that such systems are there to help them.
  • Should students be forced to attend classes?
  • The behaviour of departments who hold such data can be difficult. Data owners may be distributed. People hold their data very close to their chests and don’t want to share. Perhaps the most difficult bit is managing the soft human interface.

Data Privacy/Ethics

  • Who should be allowed to see staff data?
  • Who monitors the monitors?
  • Can use of data in this way be seen as “Big Brotherish”?
  • How quickly should staff intervene if a student is “red-flagged”?
  • Is it ethical to pre-load a system with at-risk demographics, e.g. part-time, male students?
  • What directory information should be available to everyone on a university intranet? Should photos be included (it can be useful for staff to add a name to a face)? What information shouldn’t be included?
  • Should grade history be confidential?
  • Students already share their data informally on Facebook, so why should the institution get involved?
  • Is it OK to use student data for research?
  • Who are the stakeholders involved in holding the data? What about contracts with work based learning students?
  • Sensitive handling of data and how it’s being collected is necessary.
  • Who should access what data? Should whoever needs the data be able to access it? What is legitimate? Data access needs to be considered before any opt-in box is checked. Explicit permission is needed from the student. Should anyone have access to depersonalised data as long as it’s properly depersonalised?
  • What about control of access for student? Student might be overwhelmed with information if everyone has access to the student’s data.
  • What about access by parents or other interested parties?
  • What is the “right data” to collect and analyse? For example, a student might have patchy attendance but may interact very well with the tutor and have a good assessment. Whoever acts on the data provided needs to know the student well.
  • What are the softer engagement analytics? What aspects of the student lifecycle can be harnessed? How do we capture this soft data? It needs to be about the social life as well as the academic life.
  • How early do we need the data and what would those data sources be? The data might come too late, i.e. the predisposing factors may already be in place before the student starts.

The session brought a lot of issues to light, along with some real privacy/ethical concerns, but it also highlighted that even a small change (such as keeping a register) can make a difference to student retention. However, we need to remember that students are not just collections of bits and bytes to be analysed and examined for trends. We are human with all the foibles, idiosyncrasies and circumstances that make us unique.

Accessibility of e-Textbook Readers

February 10th, 2012 by Sharon

Last night, I sat in on an EASI (Equal Access to Softtware and Information) webinar about the accessibility of e-textbook readers by Ken Petri from Ohio State University. It seems as though the device designers are really trying hard to get it right, although there’s still some way to go.

Photo of a paperback book.

After a short introduction to the legal context (Advocates for the Blind sued Arizona State University over their use of Kindle resulting in Amazon making changes to its software), Ken gave an overview of the current e-book formats on offer, which are mostly based on XML (eXtensible Meta-Language):

  • PDF (Portable Document Format) – common, but mostly inaccessible unless tagged correctly.
  • MOBI (Adobe).
  • AZW (Amazon) – ePub-like format for the Kindle, but lacks its rich structure.
  • XPS (XML Paper Specification) – designed to look like the original paper copy; only used by Blio.
  • DAISY (Digital Accessible Information System) – accessible standard for digital talking books; not much control over formatting.
  • ePub v3 – read by most readers (except Kindle); has a lot of DAISY’s accessibility features; rich formatting control, including video/audio embedding; full support for MathML (although no readers can read it just yet). It’s basically XHTML (eXtensible HyperText Markup Language) with super styling, i.e. CSS3 (Cascading StyleSheets) with SVG (Scalable Vector Graphics) and JavaScript.

He then followed this with an overview of e-book reader accessibility:

  • Kindle – has a free accessibility plug-in for PC; uses its own text-to-speech engine, so won’t work with screenreaders; not possible to copy and paste text; the finest grain of movement through the book is sentence by sentence; allows synching of different platforms so notes made using Kindle on the iPad can also be viewed on a PC. (Apparently it’s very easy to bypass the digital rights management and convert both MOBI (Adobe) and AZW (Kindle) formats to ePub and read the book on another device!)
  • iBooks 2 (Textbooks) on iPad – proprietary version of ePub v3, although authoring software, iBooks Author, is free; good for embedded graphics; can only be used on the iPad, not on the iPhone/iPod nor any other device; limited textbooks in the iBooks Store; possible to read ePub books using iBooks 2, but the fine-grained reading experience isn’t there; words highlighted as played; full typographic control (e.g. enlargeable text, high contrast, etc).
  • Blio – has incremental zoom for focussing on a small section of text and back out again.
  • ReadHear – a downloadable app for Mac or PC; uses DAISY; accessible maths equations; words highlighted as played; full typographic control (e.g. enlargeable text, high contrast, etc); rich screen reader access (for DAISY books only).
  • NookStudy – cross-referencing; synchronised highlighting for comparison purposes, where several books (or different pages of the same book) can be open at the same time; cut and paste; look-up using Wolfram Alpha.

For further information, see Ken Petri’s e-Book Reader Accessibility and Comparison Matrix (under development).

Although the presentation focussed on the accessibility of readers rather than on the content, some mention was made of authoring tools. For example, Calibre is a free, open-source tool that will convert across formats using RTF (Rich Text Format), e.g. from Word to DAISY (although it doesn’t do MathML). There is also a plugin for creating DAISY books from Word itself.

To sum up the importance of e-textbooks, Ken’s presentation included a quote from Eve Hill, Senior Counsellor to the Assistant Attorney General at the Department of Justice:

“In education, the current transition from print materials to digital materials creates and incredible opportunity for people with print disabilities to finally use the same products as their peers and to gain the same benefits as their peers who do not have disabilities.”

Of course, there are negatives, such as affordability of devices, proprietary formats, limited storage capabilities on some readers, possible short shelf-life as device OS’ (Operating Systems) move on, etc; and authors and publishers still need to be made aware that they need to make the content accessible. However, I think e-textbooks have much to offer everyone, not least the opportunity to present information in an interactive and engaging way in a format that almost everyone can access.

Come and join us!

February 2nd, 2012 by Sharon
Paper cut-outs of people in a circle

Are you interested in improving your BCE CRM (Business and Community Engagement Customer Relationship Management) processes to help increase revenue streams? Do you want to find out about SLRM (Student Lifecycle Relationship Management) and putting the student at the heart of the process?

If so, come and join our RM in HE/FE Community of Practice discussion list, which is open to anyone who wants like to share their experiences of improving their relationship management in the tertiary education sector. We’d love you to ask questions, comment, suggest resources etc, or just follow the conversation.

We’ll be sharing our findings from the current JISC Relationship Management Programme, which is looking at three different areas:

  • Good Practice in CRM - delivering a comprehensive online handbook of good practice in CRM processes for HE and FE.
  • Student progression, retention and non-completion - using service desing to improve the quality of the student experience.
  • Alumni engagement - using web technologies to support mutally beneficial alumni engagement.

We have a range of resources available at both the JISC CETIS RMSAS (Relationship Management Support, Analysis and Synthesis) project website and at the Just Enough RM (Relationship Management (a dynamic resource to try and help anyone starting out on the RM path). We also have documents on using Service Design in HE and FE and an overview to RM in HE and FE to get you started.

So what are you waiting for? Come and join the RM in HE and FE Community - we’d love to see you there!

Relationship Management in UK HE and FE Report Now Available

February 2nd, 2012 by Sharon
Photo of a handshake

Relationship management is becoming increasingly important in the tertiary education sector as education institutions try to meet the challenges of funding cuts and increased student and community expectations. Customer relationships, if handled effectively, will bring benefits to both the organisation and the sector as a whole and it is in this area that JISC developed the Relationship Management Programme.

The first phase of the JISC Relationship Management Programme ran from July 2009 to April 2010. The Programme, supported by the JISC CETIS RMSAS (Relationship Management Support, Analysis and Synthesis) project, was divided into two strands and was :

  • BCE CRM (Business and Community Engagement Customer Relationship Management) Strand - aimed to improve business processes and to pilot and extend the BCE CRM SAF (Self-Analysis Framework). Twelve universities and one FE college used the SAF to examine factors affecting the people and processes that could affect the implementation or uptake of CRM (both as an approach and as a technology). BCE CRM includes employers and other external customers, who may have the potential to help the sector navigate through the current choppy waters of tertiary education sector funding. Good customer relationship management is vital in order to maintain and develop such relationships.
  • SLRM (Student Lifecycle Relationship Management) - focussed on improving the student experience by putting the student at the heart of the process. Six universities and one FE college trialled service design techniques at different stages of the student lifecycle in order to identify areas for improvement. As students clearly exhibit certain customer attributes, such as paying for a service and expecting higher levels of choice, quality and experience, it therefore seems appropriate to apply such commercial techniques, in order to improve the student experience, the institution’s efficiency and retention.

Whilst the two strands can be viewed as focusing on two different types of institutional stakeholder – external business contacts in the case of the BCE CRM strand and students in the SLRM strand – many of the issues regarding the way in which the relationship is managed by the institution are similar. For example:

  • BCE CRM
    • Ensure that an effective CRM strategy is in place, and that is disseminated to and understood by staff.
    • Use a framework to help your institution ask fundamental questions about the people, processes and systems currently in place, prior to making any decisions regarding improvements or attempting to purchase or implement a technical CRM system, because this will go a long way to help avoid potential pitfalls and dangerous assumptions.
    • Strong commitment from senior management is vital if CRM is to succeed.
  • SLRM
    • The institution should not assume that it knows what students want, need and expect.
    • Service improvements do not have to cover the whole service, e.g. enrolment, in one go - small adjustments can be made that can actually make a huge difference to the student experience.
    • Improving the effectiveness of a process can also improve efficiencies.

The current funding situation means that institutions need to become more cost-effective. Therefore, making the most of the systems already in place, improving processes, and ensuring that the student or BCE customer has a valuable experience may help achieve this goal.

This findings from this Programme are now available in PDF format: Relationship Management in UK Higher and Further Education - An Overview (Perry, S., Corley, L., and Hollins, P 2011). Phase 2 of the JISC Relationship Management Programme is now in full swing.

New JISC Relationship Management Programme Projects Up and Running

March 25th, 2011 by Sharon

The next phase of the JISC Relationship Management Programme has just got underway and will be supported again by JISC CETIS. It follows on from the previous Programme which ran two strands: BCE CRM (Business Community Engagement Customer Relationship Management) Process Improvement (13 projects) and SLRM (Student Lifecycle Relationship Management) Pilots (7 projects).

This latest round of projects, which will run until July 2012, is split into three different strands:
* Strand 1: Good practice in CRM (Customer Relationship Management) - projects yet to be confirmed. A project to deliver a comprehensive online handbook of good practice in CRM processes for HE (Higher Education) and FE (Further Education).
* Strand 2: Student progression, retention and non-completion (8 projects). Demonstrator projects delivering service innovations that improve the quality of the student experience, specifically to enhance progression and retention to minimise non-completion.
* Strand 3: Alumni engagement (7 projects). Demonstrator projects developing and validating innovative processes and harnessing web technologies to support mutally beneficial alumni engagement.

The projects in Strands 2 and 3 follow on from the SLRM projects in the last Programme, but focus on different stages of the student lifecycle.

If you are interested in the progress of the projects, you can find further information from the JISC CETIS RMSAS (Relationship Management Support, Analysis and Synthesis) website or follow the Twitter tag: #rminhe.

If the last projects from the last Programme are anything to go by, the level of expertise in relationship management in the institutions involved will increase considerably, so we wish all the projects in this latest Programme every success.