Learning from Lukewarm Library Instruction

I said in my November post that it wouldn’t be the only one I wrote about library instruction. As someone who is still new to teaching and class instruction, learning how to be an engaging, fun, and informative teacher is one of my biggest learning curves as a first-year academic librarian. So, a few months later, I’m returning to this topic – specifically to talk about a library instruction session that didn’t go as well as the one that I prepared in 24 hours.

Teaching graduate students

In my role as a liaison librarian, I work with a specific department at Vanderbilt’s Peabody College. Within that department, I manage everything library-related for nine programs – five master’s degree programs, three Ed.D. (doctorate of education) programs, and one Ph.D. program. One thing you might notice from that list is that I only work with graduate students, which is something that I was both nervous and excited about when I accepted this position.

I was excited because I knew I would be able to relate to the students, having just finished two years of being a grad student myself. A lot of the programs I support are aimed at students who are coming back to school for a career change, or who want to further their current career by completing a degree while they continue to work full-time. As someone who worked for seven years before going back to school for my MSLS, I felt when I accepted the job like I would understand these students’ experiences, and working with them has confirmed this.

However, I was also nervous because I hadn’t worked with graduate students much before. I was a Graduate Assistant at a library at the university where I did my MSLS, but worked almost entirely with undergrads in that role. The only experience I had with teaching graduate students was one co-teaching experience with my supervisor.

The good news is that a lot of my nerves about teaching and working with graduate students dissipated during the fall semester. Most of what I was teaching was similar to what I had taught undergrads – the basics of Boolean and how to look beyond Google Scholar – usually with just a few more details or advanced database skills included. Although I knew I still had a lot to learn, I felt more confident in the content of my instruction sessions for graduate classes after a semester.

Teaching Ph.D. students – how different could it be?

Late in the fall, a professor asked me to teach a Ph.D. class of hers. She requested that I come for 10-15 minutes for a brief library overview, and if it went well, I could come back in the spring and teach the class again for a full session. I agreed, the fall session went well, and in December we scheduled a day for me to teach for an hour in mid-January.

Unlike most other lessons I had taught, this was a lesson that I needed to create from scratch. I had also never taught Ph.D. students, and had only a few vague ideas of what the professor wanted me to teach. However, I had worked with a lot of Ed.D. students one-on-one in the fall, so I decided to base the lesson on what I taught those students – the basics of Boolean, how to navigate a database, and an overview of the research-specific AI tools that we have. Both groups were doctoral students, I reasoned, so their needs were probably fairly similar.

I knew I was in trouble within the first five minutes of arriving at the classroom. I had prepared slides at the beginning of my presentation to explain who I was and give an overview of Vanderbilt Libraries’ resources – essentially a condensed version of what I had done in the fall. To my surprise, as I set up my computer at the front of the room, I realized that the group of students I was about to teach were the exact same students I had taught in the fall. Since this was the same class, I had figured the students would be different, because groups of students don’t usually take the exact same class in back-to-back semesters (or ever). But this was definitely the same group.

This made my first few slides obsolete, so I breezed through them like this was the plan all along, saying things like “since we covered this last semester, we’ll go ahead and move on!” I quickly reached my slides on Boolean. I cheerfully explained how databases speak a specific language, and that to be able to use them effectively, we needed to speak that same language. Then I asked how many people had heard of Boolean before.

Every hand in the room went up, and my heart sank. If all the students already knew Boolean, most of the rest of my lesson was also obsolete.

I pivoted as best I could, asking the students to generate terms for the example topic on my slide instead of explaining the terms I had already thought about. Then I used their terms to run some searches in the databases and talked about filters and peer reviewed articles. I was hoping to be able to move on to AI research tools and spend more of the lesson time there.

However, before I could change gears, the professor asked me to talk about searching by subject headings within a database. I hadn’t prepared anything on this topic but gamely pulled up the ERIC thesaurus and showed students how to use it for a search. No surprise that since it wasn’t a search I had prepared in advance, it didn’t return any results. My attempts to change the search or look for different subject headings didn’t help.

To make matters worse, by the time I moved on from subject headings, that conversation had taken up so much time that we only had 10 minutes left in the lesson to talk about AI tools – not nearly enough. Students had a lot of questions about the tools and there was no way I could answer them all. To finish off the fiasco, another event was taking place in the classroom right after the class ended, so as I wrapped up my presentation by telling everyone they could email me any time with questions, students were standing up and heading to the back of the room, where pizza was being set out in preparation for the event.

My hope from this lesson is that it will be one of the worst ones I’ll ever teach. If I only go up from here, I’ll be happy. I felt so awful about it all that when my friends and colleagues asked me how the class had gone, I mostly just said “It was okay” and left it at that. The only person I really talked to about it at the time was one of my former professors, S., who has become a mentor and friend over the last few years. I shared all the details with her and greatly appreciated how understanding she was. She didn’t try to sugarcoat it or to convince me that it probably hadn’t been so bad. Then, she gently moved the conversation to something even more helpful than empathizing with me – she started helping me think through what I could do differently to try to prevent a similar situation from happening in the future.

Lesson 1 – Ask the faculty member for details

S. asked how much I had known about the class and students before I walked into the classroom. When I said not much, she told me that it was okay to ask the professor for more details. I think one of the things I’ve struggled with this first year is not wanting to be a burden to professors. It’s often so hard to get them to invite us into their classrooms in the first place, that I haven’t wanted to ask them too many things or push too hard for information. S. helped me see that asking for clarification and details is actually a part of my job, and that I can’t worry (much) about frustrating professors with my questions.

Lesson 2 – Consider giving higher-level students a pre-test

One of S.’s suggestions that I liked the most was to give doctoral students a pre-test before I teach in their classes. While undergraduate or even master’s students might not be willing to take a pre-test, doctoral students might complete one. If the professor agreed to distribute it, the responses would help me understand what those students know and don’t know – and therefore would help me tailor my lesson to fit their needs.

Lesson 3 – It’s okay to be honest with professors

One of the things I said to S. was that I felt like I could do so much better with the lesson if I could do it a second time – but that I doubted the professor would ever invite me back. She encouraged me to be honest with the professor, reach out, and simply say that I know I could do much better and would appreciate another chance to come to the class next semester to prove it. I haven’t reached out yet, but plan to do so along with my other fall instruction outreach, and hope that being straightforward helps.

Lesson 4 – View professors as colleagues

Something that I thought about, and decided against, ahead of the lesson was sharing my slides with the professor and asking if what I was planning to teach was in line with expectations. Again, I chose not to do this because I didn’t want to burden the professor. I was also afraid that I would get edits at the last minute, and would have to scramble to make changes the morning of. However, viewing professors as colleagues instead of people that I’m working for changes the equation on this for me. The next time I create a lesson from scratch, I’ll definitely send it to the professor in advance and make sure it matches expectations.

Lesson 5 – Remember that I have colleagues and mentors who can (and want to) help me

I think this is actually the lesson that, in retrospect, makes me feel silliest. Librarians are some of the most helpful and giving people I’ve ever worked with, but I was so scared of looking dumb by admitting that I was unsure about how to approach a doctoral-level class that I forged ahead on my own and forgot how many times fellow librarians encouraged me to ask for help. During my entire conversation with S., I kept thinking how much better it would have been if I had reached out to her before I taught this class and asked for her advice – and if I had reached out to any of my other librarian friends, mentors, or colleagues as well. This is definitely one mistake that I’ll never make again.

Moving forward

As much as I wish I could, I can’t go back and change how the January class went. However, I can change what I do in the future, and hopefully I can even come back to this class in the fall and teach a successful lesson. After this experience, I also have a much better understanding of how much instruction is comprised of way more than just a lesson that’s taught in the classroom. It’s about working with the faculty and department, my colleagues, and the library system to make sure I’m setting students up for success. My hope is that a few years down the road, with a lot more instruction experience to rely on, I’ll be able to look back on this class not as a failure, but as a turning point in my library instruction journey.

5 thoughts on “Learning from Lukewarm Library Instruction”

  1. I can tell you have given this a lot of thought in the aftermath. I do think it may have been more beneficial to a majority of the PHD students present than you realized. They are likely not used to giving much feedback, especially with pizza waiting at the back of the room for another event on the heels of yours. Your helpful “lessons learned” can apply to other situations as well. For example, in the business world (a corporate setting). Thank you for sharing this and for your candid assessment of your teaching experiences.

  2. I’m sorry this happened, M! It sounds like S gave you great advice and you’ll be able to turn things around in the future. Don’t worry about being a bother to faculty–(in my opinion) if they didn’t want to invest a little bit of time coordinating the class with you, they should not have reached out to invite a guest instructor in the first place! I often start out by outright saying “I want to make sure I understand your expectations for this session so I can be sure to meet them” before diving into a bulleted list of my questions. If I have a lotttttttt of questions, I’ll instead offer to pop by their office for a 15-minute chat at a time convenient for them.

    In addition to the questions S suggested, I also always ask if the library instruction is tied to a particular assignment (which it usually is–annotated bib, final paper, poster presentation, etc). This is less necessary with graduate students, but I’ve found undergraduate students pay far more attention when I explicitly say “I AM HERE TO SHOW YOU HOW TO FIND INFORMATION FOR YOUR PRESENTATION WHICH IS DUE IN TWO WEEKS. YOU HAVE TO HAVE AT LEAST ONE NEWSPAPER SOURCE, SO FIRST, WE WILL LEARN ABOUT THE NEWSPAPER SEARCH TOOL” etc. [the all caps is me using my teacher voice, lol] I have also found that sometimes faculty descriptions of their own assignments are incomplete or otherwise unhelpful, so I often (politely) ask them to provide me with the actual assignment sheet that students are given. At the very least, I want to know when the assignment is due/how far along students ought to be when I see them and what kinds of sources they are supposed (and not supposed) to use.

    Once I figure out my lesson plan, I always send a final follow-up email laying out my lesson plan in 2-4 detailed sentences. Faculty don’t always respond to this, but that’s okay. I feel I’ve done my due diligence in sending the message, and having this record also provides me with a level of protection. If a faculty member were to take issue with my instruction (for example, Why didn’t she talk about this, or Why did she talk about that) and go to my supervisor about it, I would have the email to back me up in saying “I told them exactly what I was going to do with several business days’ notice, and they did not object.” A librarian I know was caught semi-recently in a situation where faculty objected to the content of their instruction and went directly to the librarian’s supervisor about it, and while this is very rare as far as I know, I still think it’s prudent to create a paper trail.

  3. I understand how frustrating it is when a lesson doesn’t go as planned, but the students may have gotten a better experience than you think. And that’s not sugar coating things! The students didn’t know what you had planned, so they don’t know where things went off track, and it sounds like you were able to improvise as needed.

    Your take-away lessons are great. But also, having a search go wrong and demonstrating how to adapt is a great lesson for the students. When we show up to demonstrate some perfect pre-planned searches, and then students run into roadblocks in their own searches, they can feel like it’s their failure. Like they’re just not good at this. By demonstrating how messy searching can be, we demonstrate that research is a messy, iterative process, and when you don’t get useful results, you brainstorm new keywords or try a different approach instead of giving up.

    Tip for those times when profs want you to talk about using subject headings to search – instead of starting from the controlled vocab list, I always demonstrated using the subject links from an article I found through a keyword search. In 12 years as an academic librarian, and as a PhD student before becoming a librarian, that’s the only way I’ve ever successfully searched by subject headings in my own research!
    And if that’s the only article with that heading, then that might be a research gap that someone should consider exploring! One of the biggest differences in working with PhD students is that it’s actually good for them if there are very few results that closely match their research topic!

  4. Hello! I am also in my first semester teaching as an adjunct. I would love to connect and chat.

  5. Eleanor and Angela – I apologize for how delayed this response is! Thank you both so much for sharing your thoughts on this experience and for your helpful tips.

    Angela, thank you especially for your reassurance that things may not have been as bad as they seemed in the moment! I really appreciate that. The suggestion of using subject links in an article is fantastic – I’ll definitely be doing that in the future. And that’s a great point about research gaps being good for PhD students!

    Eleanor, I love the reframing of “if professors aren’t willing to work with us at least a little, they shouldn’t have asked us to come to the class in the first place.” And, the point of creating a paper trail is a good one. I’ll definitely keep that in mind for the future.

    Laura – not sure how to get in touch with you directly, but if you see this comment, you can find my email at vu.edu/roberts and you’re welcome to reach out any time!

Comments are closed.