30.05.2013 Views

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3. Challenges<br />

70<br />

BEST PRACTICES <strong>2012</strong><br />

Momentum is an important word to remember when starting a new group like NewFeds.<br />

Thanks to the enthusiasm and leadership of our co-chairs, NewFeds quickly became less<br />

of a “good idea” and more of a “real thing.” Within a few weeks of meeting <strong>for</strong> an in<strong>for</strong>mal<br />

lunch, we convened our first meeting (with official minutes!) and began brainstorming<br />

how to structure the group. We maintained momentum through the 2011 summer<br />

conference season, primarily through email exchanges and via posts to the NewFeds<br />

Facebook group .<br />

Our first event, the NewFeds Virtual Conference Redux in August 2011, was our way to<br />

crowdsource the knowledge we had gained and provide presentation opportunity to<br />

NewFeds members. Using Adobe Connect and a conference call number, we brought<br />

together 15 members of the federal library community to share insights and resources.<br />

Knowing there was a quickly-approaching FEDLINK event, we established subcommittees,<br />

recruited co-chairs <strong>for</strong> these new entities, created a handout, and set up a<br />

bare-boned website.<br />

And then life intervened. Some of us got new jobs, some sought different jobs, and others<br />

were thrown curveball after curveball at our current positions. Moreover, as early-career<br />

professionals, many of us faced challenges making time <strong>for</strong> NewFeds activities during our<br />

workdays. We were juggling the demands of learning our jobs while also trying to stand<br />

up NewFeds. With the addition of a busy holiday season, NewFeds went into<br />

organizational hibernation.<br />

Our loosely-defined roles were not yet documented, which left some members feeling less<br />

empowered when asking their leadership <strong>for</strong> time to work on NewFeds initiatives. This<br />

created communication challenges, since our fledgling leadership group was trying to<br />

coordinate by email after hours, during our busy personal time. Many NewFeds face<br />

additional work barriers such as technology and security issues in the workplace that<br />

prevent access to certain communication tools. Another challenge has been finding the<br />

time to attend additional training events. Some supervisors are more flexible than others,<br />

and some require professionals to use annual leave to attend activities. As new<br />

professionals, we have not built up much leave.<br />

NewFeds leadership has reflected on what has happened so far with our organization and<br />

its sub-committees. We have also observed processes of other professional organizations.<br />

We are collectively using this knowledge to continue to improve our organization. We<br />

intend to annually assessing what we have accomplished and where we want to go in the<br />

future.<br />

4. Lessons Learned<br />

With signs of spring coming back to the DC area, several members of the NewFeds<br />

leadership began a vigorous dialogue via email and telephone in recognition of the need to<br />

re-energize NewFeds. We convened a foundational and instructive face-to-face meeting.<br />

Although we had been leveraging a range of communication tools to coordinate our group<br />

activities, one of the main lessons we learned was the value of traditional in-person<br />

conversations and relationships. During our strategic brunch meeting, we had a<br />

productive discussion about NewFeds and the way ahead. Seeing one another allowed us<br />

to learn about our non-librarian lives and find other ways our interests converged. We

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!