Sometimes when I think about LibGuides (or subject guides) this is how I feel:
My goal in this post is to tell you a little bit about why.
Let me first say something about what I mean by “skepticism” about LibGuides, because I mean something very precise. All I mean when I say that I’m a bit “skeptical” about LibGuides is that I don’t take it for granted that creating LibGuides is just something librarians obviously should do. But sometimes this is the feeling that I get. If you were to ask someone why they make LibGuides I often think that they’d respond like you were crazy, and say “Um, because I’m a librarian, Kevin. And librarians create LibGuides.” So when I say I’m skeptical about LibGuides, all I mean is that I don’t necessary take it as axiomatic of what we do that the best way to achieve our goals is to spend as much time as we do creating things called LibGuides.
Because, as a profession, it seems like we spend an awful lot of time creating some really intricate LibGuides. Me, I don’t spend too much time doing this. There are a couple exceptions to this. I, of course, have something of a LibGuide for the general subject I’m responsible for, but it’s super simple. There are a few basic links to get you started with research if you had a philosophy paper, and that’s about it. My reasons for doing this aren’t amazingly well-worked out, but, upon reflecting on it, here are a few tentative ones: (1) it seems to me that LibGuides shouldn’t really be much more than that: a basic place to get you started with your research. (2) We shouldn’t spend enormous amounts of time on stuff that’s just supposed to get you started with your research. (iii) Our time would be better spent figuring out ways to make in-person connections with students and faculty. (4) The more complicated you make them, the less useful they are going to be.
Another exception is that, sometimes, when I have a particular class where there may be a lot of unusual or complex resources, I’ll sometimes just make a private guide specifically for that class. When I was a grad student I’d just make handouts; now, I’ll just make a quick guide. The major purpose of this is just to give the students a list of places they can take a look at so they don’t forget them later (since, by definition, I’m only making the guide when the students have a lot of stuff to remember). In effect, I’m just taking into account the limitations of working memory, and that’s the reason for creating the guide. Sometimes I will teach off the guide, but mostly, in these cases, I’ll just show it at the end as a resource they can follow up with (so they don’t dismiss the class session, the way many students do, since, e.g., “The class isn’t important, all the info is on the PowerPoint).
And there you have it: that’s the extent that I use LibGuides. It’s really not very much. The reactions I’ve gotten on this range from “But you have to make them, you’re a librarian” (someone really said that) to “Thank God someone else thinks this!”
So what do I do instead of spending lots of time on guides? Everything I do, I guess: make serious efforts to make in person connections with faculty and students (e.g., much of last week was spend meeting with students who’d taken me up on a general offer I always give at the beginning of my sessions to email me for research help if they should ever need it). Try to think about how to connect with students and faculty in a personal way. Read stuff about education and information literacy and psychology that I try to use to make classes interesting and useful. Write stuff. Teach classes. Offer workshops. Serve on committees. And so forth.
Guides, to me, can be useful things, for reasons noted above, but they’re nowhere near as important to me as that other stuff I mentioned Hence, my “skepticism” about LibGuides being super-central to librarianship.
I already know what some of you think!*: (be sure to check out all the interesting comments – which seem to me quite representative of the cases usually made for/against).
– curious what others have to say.
(Thanks, (as always!), to my friend Alex Carroll for the pointer).