Where’s the Brewin’ Librarian? (or, No… I did not fall off the face of the Earth)

Matt Hamilton | June 30, 2009
http://www.flickr.com/photos/margolove/1810357551/

http://www.flickr.com/photos/margolove/1810357551/

It is a very interesting time. As I gear up for another ALA conference, in the very rare spare moments I encounter I’ve been reflecting a bit on my life, my career, and inevitably… this blog.

I’ve seen the signs– blogging is dead. Well, no it’s not. But I’m certainly not the only one I know who’s taken a hiatus. I know the arguments– Friendfeed and/or Twitter have killed blogs. However, in my case that’s really not it. I remain semi-active on Twitter, but I’ve rarely spent any time at all on Friendfeed.

I have a lot going on right now. The transition from Library School student to full-fledged MLS’d librarian happened in mid-April, when I gave my final capstone presentation. I thought, “Ah-ha! Now I will blog again.”

But I did not. I spent evenings with my daughter. We went for bike rides, we read aloud together, we went to the park, and we spent many, many hours on the swing in the front yard.

And I don’t regret a minute of it.

However, by late May I began to feel antsy again and I started putting together presentations, trainings, reading a few blogs here and there, etc. But I just haven’t had the extra time to blog. As you can see from my last “post”, I had intended on live-blogging the Rocky Mountain Innovative Users Group summer workshop—but I ended up needing to come back up to Boulder after our patron network crashed for most of the day.

Which leads me to why I’m really not blogging. It turns out that moving from a position where you have little power (and therefore little responsibility) to one of great responsibility is a huge shift in many different ways.

Before, I could spend the evening on a whim staying up late coding a cool website or mashup just because I thought it would be fun. I could head off to pretty much any meeting, conference, or committee that I could drive to and afford. I could spend my time exploring and playing with ideas and writing rants about what needs to change.

But now I actually have to *do it*.

There’s no one to blame anymore if things don’t turn out well. There’s no “administration” that won’t let me implement something cool for our department. There’s no lack of ability to control the purse-strings or to delegate the tasks. Now I have to figure out how to be the one to get buy-in. I have to figure out how to take ideas from conception to reality not just in my own little office sphere—but across an entire organization.

I have to manage people. Granted—I managed work-study students at the University Libraries, and I managed all kinds of folks in the past in restaurants, sales jobs, etc. But it’s very different managing people who are mostly older than you, who are highly skilled, and who just plain have a whole lot more experience than you. Let me say this—I am ever more grateful *every day* that I had a management class in library school and that the Colorado Association of Libraries Leadership Institute has been so fantastic. It has really taught me a lot and helped me through some pretty intense challenges.

I also have spent a lot of time adjusting to my new role as professional. It’s no longer my job to do all of the nuts and bolts of coding up some new web tool or bringing online a new gadget. That’s something I have to remember. Now it’s time to trust and, when necessary, coach my staff and let them go do it. I need to keep my head in the clouds for strategic visioning and future casting. I need to participate, contribute to, and help shape policy development. I need to empower others.

I have to remind myself of this every once in a while. I almost spent this last weekend at DrupalCamp Colorado because it was “cool”. But I would have come home and played with Drupal all night, and not paid attention to caring for myself, my house, my pets, or getting ready for ALA—not to mention handling my management responsibilities for the week. I had to step back and remember, “things are different now”.

And that’s just fine. It’s tough to be stretched in many directions. However, I prefer to think that’s just a process of expanding myself. Expanding who I am and what I’m capable of. I only hope I remain malleable like silly putty—and don’t crack like old rubber band. :)

See you in Chicago!

CIL2009: web design pitfalls to avoid

Matt Hamilton | April 6, 2009

Website Redesign Pitfalls
10:30 AM – 11:15 AM
Jeff Wisniewski, Web Services Librarian, University of Pittsburgh

Redesign or Redevelop?

Redesign if just asked, old, boring

Redevelop if code is poor, usability poor, hard to update

Redesign is cheap (director won’t know difference)

Redevelop is $$$ more like triplebypass

Get off the major redesign cycle. Disruptive to users

Users dislike redesigns

Redesign w/ evidence based

Usability tests, usage logs, feedback show a need

Pitfall 1: not accounting time for assessment

Redesign where the biggest ROI in terms of content, services

Look where people are going

Google Analytics
Clicky
Usability studies
Find and document page rank

Plan for time to get consensus:
Need for change
Desired outcomes

Data is good here

Pitfall: death by committee
Make committee SMALL

Data+evidence based practice

Pitfall: being experts
Don’t design to make librarians happy, design for your users

Pitfall: thinking outside box
Cms
Blog
Wiki
Rather traditional page based

Pitfall spending too much time designing
Why be original when so many choices already?

spend time on content, services rather than arguing design minutia

Pitfall only looking other Library websites

User expectations formed on other sites, not libs

Pitfall use SMART goals

Increase page rank, improve content update times, improve usability x percent, increase in resource usage

Pitfall: not communicating enough
Consider blog or wiki, tool manage user expectations

Execution

Pitfall communicating too much
Redesign by committee
Look to evidence to avoid tedious discussions

Pitfall not providing clear path for users
Define primary functions and these paths are clear

Connecting people / materials get prime real estate

Pitfall reinventing the wheel
Use free stuff

Spent time money on remarkable content, engagement

Librarians are smart provide good content

Remarkable content is rewritten content for the web don’t cut and paste
Improvements in usability in hundreds of percent

Redesign for SEO
Structure HTML well consistently
Simple URL
Alt tags
Descriptive titles

Submit sitemap
Ask Google to remove old from cache

Design with social media optimization

Don’t throw old content

Update robots.txt

Pitfall not planning for maintenance in future

Do it right once

Others who took better notes include:

Bobbi Newman

and

Julie Strange