I have to admit that my mind is a bit of a swirl right now. It’s hard to explain why yet, but perhaps I am dropping hints below. Or I am just summarizing three interesting reading materials that I recently pored through.
Tanya Golash-Boza. “Writing a Literature Review: Six Steps to Get You from Start to Finish” Wiley Exchanges (2015).
Golash-Boza lists steps to help dissertation writers organize and write their literature reviews. The post summarizes the literature review section of Sonja Foss and William Walters’ book Destination Dissertation: A Traveler’s Guide to a Done Dissertation.
Katherine Brown and Chris Hensman (editors). “Data Driven Public Diplomacy: Progress Towards Measuring the Impact of Public Diplomacy and International Broadcasting Activities (PDF)” U.S. Advisory Commission on Public Diplomacy: Reports (2014).
The U.S. Advisory Commission on Public Diplomacy report names five areas of public diplomacy evaluation at the U.S. Department of State and the Broadcasting Board of Governors that need to be changed and makes recommendations on how to modernize and systemize evaluation in those areas.
Kylie Hutchinson. “The Demise of the Lengthy Report.” AEA365 (2017).
Hutchinson describes how “layering” (her term) data into different types of reporting formats, such as newsletters, infographics, presentations, et cetera, can expland the value of data, extend its reach, and replace an ominous final report. The post is a bit of a promo of Hutchinson’s new book, but it also succinctly encourages you to think about different ways to present your data to different audiences.
Here is as clear a mission statement for this blog as you are going to get:
This blog will explore how librarians use data to understand audiences and improve services.
What does that specifically mean? I don’t know. We’ll see.
To start, I’ve written brief summaries of a few articles and reports that have been influential in my work over the past six months or so.
Pip Christie. “Are Librarians Becoming Data Analysts?” Vable (2016).
Christie points to potential opportunities librarians have to market themselves as data analysts and discusses ways to use data analysis tools to one’s advantage. Useful from the perspective of identifying ways librarians can put their skills to use in new ways.
Mahesh Kelkar, et al. “Data-driven Decision Making In Government.” Deloitte Center for Government Insights (2016).
A team from Deloitte Center for Government Insights describes best practices in U.S. government data-driven decision-making and outlines techniques government offices can use to improve their analytics capabilities. Really nice report that offers a thoughtful road map for building program evaluation capacity.
Bill Pardi. “If You Want to Be Creative, Don’t Be Data Driven.” Microsoft Design (2017).
Pardi discusses potential problems with being too reliant on data to drive decision-making. Reminiscent of Darrell Huff’s “How to Lie with Statistics.”
My duties at work have shifted a bit recently. I still have my old duties for now; I’m supposed to be handing them off, but so far I have been pretty terrible at delegation.
Anyway, I’ve been trying to wrap my ahead around what is now on my plate. I have a big project on my hands, and at first glance, I thought my main task would be to tie together seemingly disparate resources. Because of that, I got bogged down in a lot of legacy details and I gave myself a headache trying to sort them all out.
At some point this morning, though, I got fed up with looking at all the minutiae and went for a walk. I wanted to just go outside and dream for awhile. And also buy a crepe.
When I got back to the office, I wrote up a few paragraphs describing the ideal result of the project. I probably missed a few details here and there, but I figure my colleagues will fill them in for me. The point is, I got something down on paper to get the ball rolling and now my path is a bit more clear.
For a long time, I had the Cult of Done Manifesto pinned to a wall in my cube. I took it down because I’ve moved a couple of times in the last few months. I feel like it’s a good time to put it back up.
6. The point of being done is not to finish but
to get other things done.
Crochet that on a pillow.
When I began graduate school 10 years ago (‽‽), I started a blog to track my progress. It became a useful tool when I was working on my graduate thesis and when I participated in a tour of German federal and state libraries.
After I graduated, I didn’t do a particularly good job of maintaining the blog. Without anything specific to focus on, I wrote in fits and starts. I tore up pages and then taped them back together (metaphorically speaking). I laded myself with whims and side projects that were merely annoyances and distractions instead of fully realized concepts. I obsessively reviewed posts I wrote in the past, desperately trying to generate new ideas.
Basically, I was carrying a lot of baggage that I didn’t need to lug around anymore.
So I stashed everything I had written before into one location and locked it up (again, metaphorically speaking). Then I started a new blog!
To be honest, I am looking to my old stuff for one last idea: you see, I have a lot of work and a lot of research to do in the coming months, and I want to track my progress. I hope this blog will be useful.
I’ve been driving down this road holding a map to the beach. It seemed like a straightforward route and at a certain point, I hit a stretch of the road where I stopped consulting the map.
So I didn’t notice that the highway divided and I ended up on a parallel route. I can still see the road I intended to be on, but I can also see in the distance that the two roads are going to diverge and I will be heading away from the beach and towards the mountains instead.
I pull over. I check the map to figure out how to get to the beach from where I am. I spend a lot of time staring at that map. Then I look up and I see the mountains on the horizon. As I stare at them, I realize that I ended up on the right path despite myself.
Now I am trying to figure out how to get to where I want to go. I was packed for the beach, so I need provisions and sundries for the mountains. Really, though, the first thing I need is a map.
One of the things that I have always known about myself is that I don’t have a good grasp on time management. It has never really come back to bite me in my career, but as I take on more duties at work, I can see that I am in real danger of dropping balls if I don’t get a handle on that.
I use time management as a blanket term to mean productivity and personal organization and all sorts of other jargon like that. I don’t really mean that I am trying to transform myself into a slick engine of productive output. I’m just trying to manage tasks so that I am not feeling overwhelmed when I look at everything on my plate.
Here are three broad items that I am working on:
I use day-to-day tasks as an excuse to procrastinate on broader tasks.
In other words, I can’t work on this big project because I have all these little things that I’ve decided are more pressing.
I jump from task to task too quickly
Rather than completing or reaching a good stopping point on one task before moving onto the next, I work on three or four at the same time, bouncing between each.
I spread my to do lists across too many platforms.
So I am experimenting with a few different techniques and tools to improve my skills. I am starting small, making adjustments rather than going on a crash diet. This way whatever positive changes I make will more likely to be permanent.
Also, while I may post progress reports here, I’m not planning to write some sort of “10 Time Management Tips That Will Completely Change Your Life and Make You the Most Important Person at Your Place of Work and They Will Buy You Stuff” article. I’m just trying to figure out what works for me. Your mileage may vary.
Now… got to find a piece of paper.
Last month, in the introductory post to my Library Day In the Life series, I wrote, “The longer I have been at this job, the more I’ve struggled to do connect what I do with what librarians do in general … this is an opportunity for me to lay out what I do and then see where it all fits into the broader profession.”
Since then I went to Computers In Libraries, which came after a particularly intense stretch during which I was focused on one specific aspect of my job. I needed some time to decompress. (Sort of. I mean, I did check my BlackBerry a lot.)
Computers In Libraries gave me a chance to hear from and talk to my peers and learn about what they were doing. I recognized aspects of my job in these presentations and conversations and I could relate to a lot of what I saw.
And it wasn’t just the newfangled stuff (like makerspaces). It was also about the oldfangled stuff (like training). I realized that while I may feel like I am moving into new areas at work, I am still using a lot of my traditional skills. And I am expected to use them.
For better or worse these days, the word librarian means something. I wouldn’t say it’s a dirty word to people outside of the profession, but it is a word that carries some historical weight that some people think of as outdated. Yet those same people still value our ability to train, to research, to bring order out of chaos. They just don’t realize that’s a librarian thing.
And that’s okay. I need to communicate my value, and I think I can do it. Does it mean speaking two different languages, as it were, librarianish and bureaucratish or something like that? Sure, and it’s on me to do the simultaneous translation. I just need to make sure I understand how to translate one into the other.
During his Computers In Libraries presentation on podcasting, Maurice Coleman said of his podcast, “[T Is for Training] has been my professional development. It has been my advanced degree.”
I love that. It reminds me of a quote attributed to Southwest Airlines co-founder Herb Kelleher: “We have a strategic plan. It’s called doing things.” It also dovetails nicely on Stephanie Petruso‘s advice to her staff at Anne Arundel County Public Library that if they come across a new tool or service, they should try it out on their own first to figure out if it is a good fit for the library.
It seems odd to me that my biggest takeaway from a professional conference that the best professional development often comes from just trying stuff out. But I’ve been thinking a lot about alternatives to conferences. I overheard that attendance at Computers In Libraries was down this year. That and the continuing decline of SLA makes me wonder if the conference model is still viable.
(To be fair, a sample of two conference is by no means conclusive, but bear with me here.)
SLA made a big deal in recent years about how it is your own responsibility to tend to your professional development. In other words, you shouldn’t skip the conference just because your employer won’t pay for it. But a $500+ conference, plus transportation and lodging fees and meal costs make a serious dent in any librarian’s bank account. You’re only going to save so much money sharing hotel rooms and pigging out at receptions.
If my professional development truly is my own responsibility, then I am going tend to it responsibly and look for alternatives. I will get active in local associations and leverage my social media connections. I’m going to look for new things to do and play around with them to see what I can learn from them.
I don’t mean to sound so down on Computers In Libraries: it was a terrific conference this year and I learned a lot. (See: the first sentence of this post.) I would be missing out if I found myself in a position where I couldn’t go to it. (Versus just opting not to go to it.)
But my advanced degree curriculum is all around me, not just at conferences. I just need choose my electives wisely.
The first day of a conference usually feels like a family reunion because there are always a slew of people you only see when you go to a conference. So today was as much a day for catching up with old friends as it was a day for catching up on new trends.
Trendspotting wasn’t really on my agenda today anyway. What I really wanted to spot were ideas that I could bring back to my office. As I mentioned before, my job is not exactly a traditional library job, so I am hoping that I can bridge some gaps this week.
What I learned today is that it is easy to see my place of work as some kind of “special snowflake,” to borrow the words of Jeff Wisniewski during UX Practices & Patterns. But while I may face some unique challenges (“Shoot, when I said Macedonia, did I mean Montenegro?”), I am also facing a lot more challenges that my peers are already attacking head on.
I’ve found it is way too easy form me to dismiss stuff by saying it wouldn’t work where I work. But what would I be expecting, to implement an idea in the exact same way that a conference presenter did at their place of work? Of course not. So what am I really rejecting? Probably the work I would need to do to implement an idea, even though implementation is always the hardest part. I don’t want to say I’m too lazy or too scared, but there has to be some sort of fear-based laziness or laziness-based fear going on here.
So now I have a notepad filled with ideas. My challenge is to take those ideas and try to make them work. Some of them may come to fruition, some of them may die on the vine, but you can’t make an omelet without breaking a few eggs. Also, I may not have eaten enough for dinner. The point is, regardless of how out of touch with the library profession I’ve been feeling, what I am doing is not so unique that I can’t take inspiration from my fellow librarians and run with it.
I am going to be attending the Computers In Libraries conference next week and I’ve registered to be a conference blogger. It has been a while since I’ve actually attended the conference (versus just meet friends for lunch while they are in town for the conference) and I am really looking forward to it.
I packed my schedule with sessions, but I know from experience that I will probably not attend all of them. This is not meant as a slight to presenters, but sessions sometimes are not as interesting as network opportunities. If I get involved in a good conversation with someone, I am not likely to cut our discussion short to rush off to a session.
In the past when I’ve blogged at conference, I’ve usually taken a reporter’s approach: take notes, take pictures, write up a summary, and pray that the quotes are accurate. That’s not my plan for next week though. To be sure, I will be taking lots of notes as I am expected to report back to the office when Computers In Libraries is done. But I plan to take a more impressionistic approach to the conference, looking for themes and talking about the conversations I have while I’m there. I really just want to capture the vibe.
I have to admit that I’ve not been particularly enthusiastic about going to any conference for a while (PTPL Annual Meeting excepted). The expense and the planning had kind of worn me down. To be honest, I wasn’t planning to go to Computers In Libraries until just a few weeks ago. I knew that sales reps from two of the electronic resources providers we work with were going to be in town, so it made sense to attend.
But the more I thought about it, the more excited I was to go. Granted, daily access to Dolcezza had a lot to do with that excitement.
By coincidence, I happened upon an article by Abbie Digel on Syracuse’s Information Space blog called “Why you need to go to a library conference.” It’s addressing library school students, but it could also be targeted towards jaded old-timey librarian types like me. It helped me take a step back and remember why I liked going to conferences in the first place.
So if you happen to be at Computers In Libraries next week, I will see you there. Or at Bistrot Du Coin. I love that place too.