Technical Services Workflow Analysis OLC Technical Services Retreat Mohican Resort & Conference Center April 1, 2008 Morag Boyd and Connie Strait.

Slides:



Advertisements
Similar presentations
Quantitative and Scientific Reasoning Standard n Students must demonstrate the math skills needed to enter the working world right out of high school or.
Advertisements

1 of 18 Information Dissemination New Digital Opportunities IMARK Investing in Information for Development Information Dissemination New Digital Opportunities.
PROJECT RISK MANAGEMENT
Collaborative Technical Services Team Report GUGM May 15, 2014 Cathy Jeffrey.
ICASAS305A Provide Advice to Clients
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Title I Needs Assessment and Program Evaluation
Lecture Nine Database Planning, Design, and Administration
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
10 Stages Of the Engineering Design Process
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Chapter 17 Acquiring and Implementing Accounting Information Systems
1 Qualitative Evaluation Terms Coding/categorization The process of condensing qualitative data through the identification of common themes. Data Matrix.
SYSTEM ANALYSIS AND DESIGN
Needs Analysis Session Scottish Community Development Centre November 2007.
The Center for IDEA Early Childhood Data Systems 2014 Improving Data, Improving Outcomes Conference September 9, 2014 Developing or Enhancing Business.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
ISTEP: Technology Field Research in Developing Communities Instructor: M. Bernardine Dias CAs: Sarah Belousov and Ermine Teves Spring 2009.
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
CS499 Use Cases References From Alistair Cockburn Writing Effective Use Cases (Book) - Use Case.
1 Shawlands Academy Higher Computing Software Development Unit.
Research methodology Data Collection tools and Techniques.
ODINCINDIO Marine Information Management Training Course February 2006 Evaluating the need for an Information Centre Murari P Tapaswi National Institute.
The Evaluation Plan.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
1 CMPT 275 Software Engineering Requirements Gathering Activity Janice Regan,
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
The Analysis Phase Objective: To study the current system, organization, and problems to determine what changes need to be made in order to achieve the.
The Wisconsin RtI Center (CFDA #84.027) acknowledges the support of the Wisconsin Department of Public Instruction in the development of this presentation.
M4 - 1 BU ILDING STRONG SM Multi-Purpose Projects Module M4: Telling the Plan Formulation Story.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
The Software Development Process
Information Management and Market Research. Marketing Research Links…. Consumer, Customer, and Public Marketer through information Marketing Research:
Requirement Engineering
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Observing the Current System Benefits Can see how the system actually works in practice Can ask people to explain what they are doing – to gain a clear.
Research Methodology II Term review. Theoretical framework  What is meant by a theory? It is a set of interrelated constructs, definitions and propositions.
User-Centered Design (UCD) Overview
CCT 333: Imagining the Audience in a Wired World Class 6: Intro to Research Methods – Qualitative Methods.
IMPLEMENTING LEAPS IN CENTRAL AND EASTERN EUROPE: TRAINERS’ HANDBOOK Monitoring and Evaluating Results.
Unit 1. Introduction Creativity: The production of an idea, concept, creation or discovery that is new or original to its creator or a new combination.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
Team Up! How to Turn Problems into Solutions PRESENTERS MARJUYUA LARTEY-ROWSER, PHD, RD MARY FRANCES NETTLES, PHD, RD.
 Is it a struggle to keep on top of program or donor information?  Are you wasting postage and effort mailing to your entire list rather than tailoring.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
How Can Non-Profit Evaluators Best Support Field Staff in Data Collection? American Evaluation Association Annual Conference October 19 th, 2013 Kelly.
OH NO!!! Quality Improvement. Objectives Define a Quality Improvement Program Identify how to get started Identify who should be involved Identify how.
10 Stages Of the Engineering Design Process
Monitoring and Evaluation Systems for NARS Organisations in Papua New Guinea Day 3. Session 9. Periodic data collection methods.
Fundamentals of Information Systems, Sixth Edition
Requirements Analysis Scenes
Monitoring and Evaluation Systems for NARS Organisations in Papua New Guinea Day 3. Session 8. Routine monitoring.
Cleaning up the catalog: getting your data in order
THE FEASIBILTY STUDY LECTURE-5.
Engineering Design Process
Monitoring and Evaluation using the
10 Stages Of the Engineering Design Process
10 Stages Of the Engineering Design Process
10 Stages Of the Engineering Design Process
Dr. Ron Atwell Ms. Kathleen Connelly
AICT5 – eProject Project Planning for ICT
Presentation transcript:

Technical Services Workflow Analysis OLC Technical Services Retreat Mohican Resort & Conference Center April 1, 2008 Morag Boyd and Connie Strait

Workflow Analysis: Why and How Morag Boyd The Ohio State University Libraries

Definitions  Workflow is the process, progress, or "flow" of work within a system and the rate at which that happens  Workflow analysis refers to observing how this process takes place. The analysis also involves evaluating the process and improving it for efficiency and effectiveness.

What is is not It is all about the PROCESS, it is NOT:  Individual performance evaluation  Satisfaction measurement

What are we trying to study  Goal achievement  Resource usage All necessary tasks are being performed No unnecessary tasks are being performed Tasks are being performed effectively and efficiently  Causes of known problems  Opportunities to respond to changes

Efficiency  “measured by a comparison of production with cost” Merriam-Webster  Rate of work Time to shelf Minimizing repeated handling of materials  Resources needed to do the work Correctly matching skills and tasks Utilization of software to maximum benefit

Effectiveness  “producing a decided, decisive, or desired effect” Merriam-Webster  Quality of work Error rates Following appropriate rules and policy  Choice of work Aligning work with library priorities Meeting short and long term needs

Planning a Study  Invest in planning  Clarify goals and expectations Be sure to include all staff Try to reassure that purpose is not to target staff  Define your scope and stick to it  Informal or formal study?  Internal or external?

Steps in a Study  Clarify the environment you work in  Define the goals of the department  Examine existing data  Gather new data  Document existing workflow  Identify potential changes  Implement  Repeat

Environmental Factors  Staff changes  More electronic, still have print  Different library user needs and expectation  Different internal library needs and expectations  New technology or software

Data and Sources  Need a variety of data from multiple sources. Draw your conclusions from the totality of the data  Quantitative: Things that you count  Qualitative: Things that you observe  Internal  External

Data You Probably Have  Statistics on orders, cataloging, processing, catalog maintenance, etc. Manually collected Generated from ILS, OCLC, vendors, as appropriate Again, multiple sources can be helpful  Materials budget and its breakdown  Number of FTE staff  Job descriptions

Gather New Data  Interviews  Time and task logging Cost study, particularly if considering outsourcing  Investigate other options  External data

External Data  Literature Review  Select and investigate comparator libraries Comparable Aspiration Different  Site visits to other libraries  Conversations with other libraries about their workflows

Map Existing Workflows  Different people need information in different ways  Diagramming can make it very clear how straightforward your processes are (or not) Detailed, but not exhaustive  Narrative can help explain the workflow  An actual map of the flow of material Will help analyze speed, space or repeated physical handling type problems

Graves & Arthur, 2006

Dragon & Barricella, 2006: 11

Backlogs  Identify any backlogs Remember the invisible backlogs too  Characteristics of backlog  Size is secondary to nature

Evaluation  Step back and look at your workflow Where is your diagram confusing? Where are the bottlenecks?  What ideas did staff have?  What did you learn about other services?  What was surprising?  What did you already know?

Characteristics of Optimal Workflow  Workflow is built for the mainstream, not the exceptions  Each function handles material once  Rush materials can be processed in specified time period  Overall time to shelf meets library needs  Quality of work meets needs  Job descriptions and time allocation represent all responsibilities of the unit  No duplication of data or effort

Outcomes  Identify strengths and troublespots  Tasks not done efficiently and effectively  Tasks that could be dropped  Tasks that are not getting done  Solutions to these problems  Recommendation: Written report

Implementation  Pick your battles  Make those quick and easy fixes Small things can have big impacts  Reallocate existing resources (staff, space, software, services, etc.)  Allocate new resources  Work with others towards external change

It’s Not Over Yet! Iterative Process:  Implement new workflow  Assess new workflow Important to collect comparable data in initial and post-adjustment study  Identify any continuing or new workflow problems  Repeat as needed

Technical Services Workflow Analysis : a local saga Connie Strait Greene County Public Library

Internal vs. External A real life story at GCPL

Internal Workflow Analysis  Short history  Staff changes  New location  Backlog

Internal  What problems? What routines? What to do?  Talk to your people.  Visit your friends.  Count and observe.  Eliminate the unnecessary - tasks, labels, paper copies, etc.

Prior to making changes  Get buy-in  Plan the implementation  Do it  Go back and assess.

External Workflow Analysis  Why do it?

If your boss suggests it…  This is a good place to start.  1. Make the phone call.  2. Tell your staff and all other departments. No vacation please.  3. Allow plenty of TIME.  4. Buy food.  5. After the interview sessions, relax.

Suggestions from consultants  Remember that they are suggestions and not decision. Your team makes the decisions.  Those that can be implemented right away, should be.  If money is a problem, talk to the purse string holders.  Use your ILS to the max, given your local constraints!

Each day is a new day!  You can and should assess the new routines every few months in your Technical Services department.  Those items on the “wish list” should also be addressed at the same time.

THANK YOU! Morag Boyd Special Collections Metadata Librarian The Ohio State University Libraries Connie Strait Head of Technical Services Greene County Public Library Ext 6301