Archive for the ‘CRM’ Category

Come and join us!

Thursday, February 2nd, 2012
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

Thursday, February 2nd, 2012
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

Friday, March 25th, 2011

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.

Modelling - How Do You Know When to Stop?

Tuesday, December 15th, 2009

I attended JISC CETIS’ Introduction to Modelling workshop in Birmingham last week to try and gain an understanding of issues and what one needs to consider, when attempting it for the first time.

So why bother with modelling? What value does it bring? Models are a way of communicating and sharing experiences. They are very visual and may have some narrative, but with some slight clarification of terminology used, they should be understandable by most stakeholders. This is key. Otherwise, how else can the whole system be shown to stakeholders who may only know a small part?

Whilst the workshop looked at both hard and soft models, it was the softer side that caught my attention. Hard models, such as UML (Unified Modelling Language) or BPM (Business Process Modelling) are ideal for defining technical specifications and describing business intelligence. Soft models, as one would expect, tend to be quite woolly and may include portfolios of evidence (documents, observational notes, video diaries, etc), scenarios and personas, and use SSM (Soft Sytems Methodologies).

There were two practical exercises that we all attempted. One of which was to produce a soft systems diagram showing how to respond to a JISC call for funding. I’d never done any modelling before, but something that had seemed so simple in the introduction, was unbelivably difficult when we sat down to try it for ourselves! We didn’t need any whizz bang technology - just a handful of coloured markers, multi-coloured post-its and a large sheet of paper. Here’s a model that one of the groups came up with.

Attempt at a Soft Systems Model

Attempt at a Soft Systems Model

Using diagrams like this can help tell a story by setting the scene (scenario) and describing the personas (not usually a real person but a ficticious description of a particular role that person might do) and the ways they interact. The main focus of a soft systems model is on the people or actors in the system.

People often have difficulties knowing how far they should go when modelling and when they should stop. However, the presenters were all unanimous in answering this question: the actual purpose for doing the modelling should set the boundaries for how far/deep one goes with it. But, as a newbie, the real key for me was that one should model just enough to achieve one’s aims (otherwise one could end up modelling for years!).

If you’d like to find out a little more about the event, there are notes and presentations from the workshop now available online. You might also be interested in the JISC Innovation Base (a repository of models for the Higher Education domain, which includes both formal and informal models) and the Agile Modeling Website (Agile Modeling is a practice-based methodology for effective modeling and documentation of software-based systems).

Happy modelling!