Reading Lists - End to End Gary Brewerton

Transcript:Reading Lists - End to End Gary Brewerton:
Reading Lists - End to End Gary Brewerton Middleware and Library Systems Manager https://www.linkedin.com/pub/gary-brewerton/84/1a/40b Contents Setting the Context What is a reading list/RLMS Reading lists at Loughborough An ongoing issue Process review Methodology used Following the workflow Mapping the process What next? Setting the context What is a reading list/RLMS Reading list A list of resources (books, journals, AV material, websites, etc.) compiled by an academic to support students in their studies Reading List Management System (RLMS) enables students to access their reading list online and check availability of recommended resources allows appropriate staff to create and maintain the reading lists provides the Library with information to support its collection development Reading lists at Loughborough We’ve had our own in-house RLMS (called LORLS) at Loughborough since June 2000 Initially we hired students to pump prime the system Thereafter academics took on responsible for maintaining their own reading lists New academics trained by library staff to use the system In February 2011 we introduced significant new version of the system Included multiple methods of creating/updating reading lists An ongoing issue We’ve had a lot of success with reading lists but we still have an ongoing issue with backlogs in processing them at key times of the year this can lead to delays in getting books on the shelves when needed Process review Process review methodology DEFINE the process that we are seeking to improve and their purpose. But define from the customer’s perspective rather than from our own organisational structure. CHECK – collect information and data on the current process from the perspective of the customer. This could be email, phone calls or observing front line drop-ins. Do this by FOLLOWing the flow of the process around the organisation – literally. Speak to front-line staff – not just their managers. And most importantly gather information on their interactions with customers. CATEGORISE that data into “Value” and “Failure” demand. The first is where in responding to the request we are genuinely adding value and the latter is where we are correcting something we should have ideally got right first time MAP the current flow of the process at a high level – again from the customer’s perspective ANALYSE the demand patterns and current flow. Identify where we have waste, hand-offs and duplication. DESIGN a new, simpler flow at a high level. EXPERIMENT with a sub-set of customers by taking them through the