T.I.P.S.
 FOR MANAGING TECH AND
  WORKFLOW CHANGES IN
       LIBRARIES

               Colleen S. Harris
Head of Access Services & Assistant Professor
   University of Tennessee at Chattanooga

                 @warmaiden
       http://guardienne.blogspot.com
Getting Started

 Who am I (and why am I here?)
   R&I to Access
   WMS
   ILL
   New building
   Reorg
 Who are you (and why are you here)?
 Agenda
ON FAILURE
Or, we’ve all been in Otto’s fur
AN EXERCISE IN CHANGE FAILURE

Think of an example of a failed
attempt at a tech implementation
      or workflow change.
Of the major factors that caused
  failure, which come to mind?
Ring Around the Rosie…

 Expensive Technology     Tech change can lead
 Tight Budgets             to workflow redesign
 High Demand              Cooperation can lead
 Improved Services
                            to workflow redesign
                           Workflow redesign can
 Increased Competition
                            lead to tech change
TECHNOLOGY
(THIS IS THE EASY PART)


http://www.flickr.com/photos/28478778@N05/5729009434/
ONE DOES NOT SIMPLY
 WALK INTO MORDOR
 FORM A COMMITTEE
TECHNOLOGY

 What problem are you solving?
 What do you want the technology to do?
 What equipment do you need?
 (We’ll get to “who” questions in a moment…)
INFRASTRUCTURE
“If you build it, they will come” presumes
        a foundation to build upon
                         http://www.flickr.com/photos/stefanochiarelli/6219871940/
INFRASTRUCTURE

 Capacity for            Example: the
 implementation           open source
   Budget                happy dance
   Space                  Staff time
    (physical/virtual)     Technical knowhow
   Staffing               Server space
Planning
(the messy part)




       http://www.flickr.com/photos/paparutzi/252726576/
PLANNING

 Timeline                       Communication
   Realistic? Broad &               Standing meetings; can
    component parts?                  also cancel, but you
    Reflecting in goal                know that time is
    setting, expectations             blocked
    and evaluations?               Success
 Inclusiveness                    Tracking
   Defining stakeholders
                                   Failpoint
   People you don’t think
    will be affected, will be      Evaluation
                                   Reorganization
SKILLS




         http://www.flickr.com/photos/usarmyafrica/5183773471
SKILLS

 What competencies do your staff have?
 What competences do your staff need?
 How big is the gap?
 What are you going to do about it?
   Skill assessments? Who? How?
   Training program? Who? How?
FRAMING
QUESTIONS
WHAT’S MISSING?




http://www.flickr.com/photos/magnus_akselvoll/4741056713/
CASES

TIPS for Managing Tech and Workflow Changes in Libraries

  • 1.
    T.I.P.S. FOR MANAGINGTECH AND WORKFLOW CHANGES IN LIBRARIES Colleen S. Harris Head of Access Services & Assistant Professor University of Tennessee at Chattanooga @warmaiden http://guardienne.blogspot.com
  • 2.
    Getting Started  Whoam I (and why am I here?)  R&I to Access  WMS  ILL  New building  Reorg  Who are you (and why are you here)?  Agenda
  • 3.
    ON FAILURE Or, we’veall been in Otto’s fur
  • 4.
    AN EXERCISE INCHANGE FAILURE Think of an example of a failed attempt at a tech implementation or workflow change. Of the major factors that caused failure, which come to mind?
  • 5.
    Ring Around theRosie…  Expensive Technology  Tech change can lead  Tight Budgets to workflow redesign  High Demand  Cooperation can lead  Improved Services to workflow redesign  Workflow redesign can  Increased Competition lead to tech change
  • 6.
    TECHNOLOGY (THIS IS THEEASY PART) http://www.flickr.com/photos/28478778@N05/5729009434/
  • 7.
    ONE DOES NOTSIMPLY WALK INTO MORDOR FORM A COMMITTEE
  • 8.
    TECHNOLOGY  What problemare you solving?  What do you want the technology to do?  What equipment do you need?  (We’ll get to “who” questions in a moment…)
  • 9.
    INFRASTRUCTURE “If you buildit, they will come” presumes a foundation to build upon http://www.flickr.com/photos/stefanochiarelli/6219871940/
  • 10.
    INFRASTRUCTURE  Capacity for  Example: the implementation open source  Budget happy dance  Space  Staff time (physical/virtual)  Technical knowhow  Staffing  Server space
  • 11.
    Planning (the messy part) http://www.flickr.com/photos/paparutzi/252726576/
  • 12.
    PLANNING  Timeline  Communication  Realistic? Broad &  Standing meetings; can component parts? also cancel, but you Reflecting in goal know that time is setting, expectations blocked and evaluations?  Success  Inclusiveness  Tracking  Defining stakeholders  Failpoint  People you don’t think will be affected, will be  Evaluation  Reorganization
  • 13.
    SKILLS http://www.flickr.com/photos/usarmyafrica/5183773471
  • 14.
    SKILLS  What competenciesdo your staff have?  What competences do your staff need?  How big is the gap?  What are you going to do about it?  Skill assessments? Who? How?  Training program? Who? How?
  • 15.
  • 16.
  • 17.