Showing posts with label technical services. Show all posts
Showing posts with label technical services. Show all posts

Monday, July 2, 2012

Ideas I hope will become trends: assessment

This series is, at its core, a recap of my trip to ALA's Annual Conference in Anaheim. But I prefer talking about the practical applications of what I learned to simply recapping programs.

The first installment was about user stories and the second was about communication.

The third installment is about assessment.

I was not planning on attending LITA's Top Tech Trends panel. But, I returned back from an off-campus lunch too late to attend the session I'd hoped to catch and too early for the next round of programs.Having found myself with a few minutes on my hand, I decided to catch a few minutes of the program.

Meredith Farkas was one of the panelists and I found myself nodding in agreement when she talked about how academic libraries can't really stand on the assertion that the library is the center of the academic community anymore. Instead, academic libraries are being asked to justify their impact on those they serve.

Farkas suggested that assessment tracking tools were a good way of managing data that would help libraries build stories of user impact.

But this isn't so much about what Farkas had to say as it is about what people had to say about what she had to say.

It seemed like the Twitter backchannel was musing about how difficult it was to cultivate the kind of organizational culture that breeds an interest in assessment. Basically--nobody teaches this kind of stuff in library school.

The thing is, I couldn't agree more with the notion that academic libraries are being asked to justify their impact on those they serve. It's no longer enough for them to say that they're the center of the academic community. Researchers, both novice and expert, are finding other sources for information than traditional library resources. And many academic libraries grapple with how to stay at the center of the campus community--a completely different challenge.

And I also couldn't agree more with the idea that data helps libraries build stories about their impact on the lives of users.

And, while we're at it, I also couldn't agree more with the idea that creating that kind of organizational culture is really, really hard.

But it's not impossible.

So, how do we do it? How do we create organizational cultures in our libraries that embrace assessment and the data it generates?

I think we start by shifting our focus toward things that are measurable. Which means that every project or program needs to have outcomes built into it during the design phase. How else will we know if the project is successful? And, in the case of programs, how will we know if the audience has learned what we'd like for them to learn?

Academic libraries need to think critically about how adopting this kind of culture could affect them for the better. What would it look like to have data supporting your assertions about how bibliographic instruction sessions have prepared student researchers for upper-level research? It's one thing to consider gate count (which is valuable data, indeed), but it's another to show how you've created good consumers and stewards of information.

I think it's equally important for user-centered back room folks to generate, synthesize, and store data as well. If it's true that academic libraries are being asked to justify their impact on the academic community, it's equally as true that many units performing back-room functions are being asked to do the same. And, when the day comes that you have to advocate for your job, it's much easier to do so using data.

So, try gathering some usage statistics after you finish a cataloging project. Did usage of a hidden collection go up after you added it to the catalog? Did analyzing that serial prompt more people to use it? This kind of data collection can help justify some of the most important work you're doing.

Alternately, though, data of this kind can help you decide what to let go of when budgets are tight and time is fleeting. You can see what your users value most and what they can live without and make decisions about resource allocation accordingly.

So...start with an outcome and measure your success accordingly. And let the data do the talking.

Be visible. Be proactive. Be awesome.

Friday, June 29, 2012

Ideas that I hope will become trends: communication

If you missed the first post in this short series, you can catch up here. The first post was about user stories and focused on a presentation that I saw at the Heads of Technical Services IG meeting.

The second idea that I hope becomes a trend is open dialogue between catalogers and, well, everyone else. The genesis of this was a bullet point from the presentation that Scott Piepenburg gave at the Competencies and Education for a Career in Cataloging IG meeting.Piepenburg's presentation was about what Catalogers would need to be able to do in a post-AACR2, post-MARC world. One thing that he suggested is a must is that Catalogers need to not only understand what their ILS can (and cannot) do, but they must also be able to communicate these limitations to others.

It took everything I had not to jump for joy or to stand on my chair and cheer. I didn't, though. It was a small room and kind of crowded.

I think that catalogers do a pretty decent job of understanding the limitations of our ILSs. We spend a lot of time working with them and, as a general rule, get what they do both well and poorly. Where it breaks down, sometimes, is communicating this information to our colleagues. Whether it's our colleagues in IT or our colleagues staffing the front lines, it is our job to communicate well with them.

Having a basic knowledge of coding can help us communicate more effectively with IT staff. We don't have to be coding wizards, but we should be able to talk about how our systems do parse out data in MARC records and, perhaps more importantly, how we wish they did.

Having a basic understanding of how users search for information can help us communicate more effectively with front line staff. We don't have to spend a lot of time on the Reference Desk (though it wouldn't hurt), but we should be able to talk about how users can do more effective searching.

So, how do we become better at communication with others? I have a couple of ideas:


  • If you want to learn the basics of coding, Codeacademy can help. They even have a program called Code Year which will walk you through the basics of languages like Javascript. And if you're looking for support, there's a CatCode wiki whose function is to support dialogue between coders and catalogers. In this case, I suspect it's a lot like learning the language when you visit another country. You don't have to be proficient in it, but the natives appreciate that you're trying to speak their language.
  • Attend (open) meetings in departments other than your own. At my former place of work, there was a monthly meeting of subject librarians that was open to all interested staff. I didn't go every month, but I tried to go fairly regularly. Attending this meeting helped me understand the challenges that subject specialists faced when helping users which, in turn, helped me think differently about the work I was doing. This meeting was also sometimes the only way that I learned about issues that I could help solve but that nobody thought to tell me about--not because they were trying to leave me out of the loop, but because they didn't realize that the problem could be solved.
  • Get your hands dirty in projects that involve other departments. Though the bulk of my job duties involved cataloging, I taught in my former place of work's Freshman Writing Seminar. I also worked with our Digital Library Services unit and our Web 2.0 initiatives. I made valuable contacts and learned a lot about what other people the organization do. 
I think the moral of the story is that it's all about relationships and empathy. Learn to speak the language of the people you work with. Be friendly and empathetic and take the time to answer questions that your colleagues have about the work that you do. 

What are your suggestions about developing rapport with other units? How have you opened the lines of communication?

Be visible. Be proactive. Be awesome.

Thursday, August 12, 2010

Gorman's "Drift down" theory and Good Enough

I was reading an article and came across the "drift down" theory which goes something like this:

Librarians shouldn't do a job that a paraprofessional can do. Paraprofessionals shouldn't do a job that a student can do. No person should do a job that a machine can do.

I was curious about the origins of this "drift down" theory, so I tracked it back to Michael Gorman. Apparently he debuted it in 1982 in a book chapter entitled "A good heart and an organized mind."

Consider for a moment how terror-inducing this is for modern-day Technical Services librarians and then consider how scary it must've been in 1982. Moreover, think about how forward-thinking that must've been.

It seems like everyone these days is preaching how Technical Services Units need to shape up, slim down, and streamline as much as possible. This time of turmoil is a perfect place for the "Drift down" theory to take hold, right? The best way to streamline your bulky Technical Services Unit is to examine everyone's daily tasks and workflows and see where projects and processes can be whittled down and passed on to someone further down the line to do.

In some ways, I am totally on board with this. Why do the costly double checking of reports when you rarely find errors?

There's part of me too, though, that worries that this zeal for streamlining our workflows and processes has the potential to be costly for users.

I am a big fan of Good Enough. I am a fan of considering what else you could be doing with the time you spend making that catalog record 'just so,' when very few people will notice the work you did. I am a fan of uncovering hidden collections and of doing special projects.

But I'm also in favor of not cutting corners when the trade off between staff time saved and value for the end user is too large. Sometimes it makes sense to have a Librarian do what a machine could could do.

The point is, when you're making decisions to streamline your workflows, slash with a pencil and not a red pen. And keep your users at the center of all of these cost-saving and time-saving measures.

Be proactive. Be visible. Be awesome.

Friday, August 6, 2010

Becoming more visible: a 3-step plan

I just finished reading Bradford Lee Eden's article entitled The New User Environment: The End of Technical Services?

You can read it here (you need a username and password): http://www.ala.org/ala/mgrps/divs/lita/ital/292010/2902jun/toc.cfm

This isn't actually a post about Eden's article, though. What really resonated with me was a quote that he used that came from a 2007 article by Sheila Intner.

She wrote:
Part of the trouble is that the rest of our colleagues don't really know what technical services librarians do. They only know that we do it behind closed door and talk about it in language that no one else understands. If it can't be seen, can't be understood, and can't be discussed, maybe it's all smoke and mirrors, lacking real substance.

I think that Intner points out a real weakness for people in Technical Services. We often end up sequestered in back rooms, removed from both library users and our colleagues. When we do get face time with our front-line colleagues, the burden is on us to show them the impact of our work. It's hard to do if, when we have the chance, we bore our colleagues to death with jargon.

For better or worse, I think it's the job of Technical Services Librarians to make their work seem relevant and important. We need to take away the smoke and mirrors and show the substance of what we do in a way that anyone can understand.

To that end, I offer you a three-point-plan:
1. Be more visible
Attend as many meetings as your schedule allows without neglecting your primary job duties. Does you library have an all-staff meeting? Go! A brown bag lunch series? Go! Use the opportunities to network with your colleagues, especially if your back-room office is at a remote part of the library where no one ever sees you.

Being more visible means that people know your name when you call or email them with a question. It also helps you seem more well-rounded, especially if you attend meetings on topics that don't seem to immediately connect with your work in Technical Services.

2. Create an 'elevator speech' about what you do
Say you sit down next to a Reference Librarian at one of those meetings and you have a few minutes before the meeting starts. If you've taken the time to craft a short explanation of what you do and how you can help that person, the time before that meeting will be more productive than any all-staff email or presentation you might give.

When you're coming up with your elevator speech, lose the jargon. Don't assume that the person you're talking to knows--or cares about--the acronyms that are second nature to you. Your elevator speech should be easy to understand and should focus on how you can make a difference in the life of the person you're talking to.

3. Find an front-line ally who is willing to help you raise your visibility with front-line staff.
In my experience, making a difference in the life of a front-life staff person is the easiest way to forge the kind of alliances that I'm talking about. If you can work a miracle for someone, they'll likely sing your praises to their colleagues.

I think that if you are willing to be visible and to forge relationships with front-line staff, the smoke and mirrors will dissipate and your true value to your organization will shine through.

Be proactive. Be visible. Be awesome.