Author Archives: Michael Roy

Upcoming Team Workshops

In the upcoming months, we’ll have the consultant Fred Schmitt on campus doing some work with our teams. In advance of his arrival, I thought it useful to outline what we’ve asked Fred to help us with. We have two major objectives:

1. We want everyone in LIS who has not yet gone through ‘team training’ to spend half a day becoming familiar with the concepts, the roles, and the vocabulary of teams. This will be useful for those who are presently on teams but have not yet been trained. Since we imagine that at some point nearly everyone in LIS will be on a team, we think it useful to have everyone trained. Many who have gone through these workshops have reported that the principles apply equally well to traditional work within a workgroup.

2. We want to re-align the existing teams. We’ve been using teams as a way to accomplish important work that spans our workgroups and areas structure. Having this experience, we need to figure out how to answer questions that we now have about roles, responsibilities, and accountabilities; communication; balancing work in a team with work in a workgroup. We also want to re-confirm the charges for the teams.

You’ll soon be getting more information about this, and invitations to meetings. In advance, if you have specific questions or concerns that you would like to make sure we cover, please feel free to email me, and I will make sure that they are included in these workshops.

Terry Simpkins wrote up a handy FAQ that may help answer questions you may have about teams:

Q. When will the team training be?
A. Probably on Fridays during the management training weeks, but this is not set in stone yet.

Q. Will there be a team leader component?
A. Yes, there will be a discussion of the various roles (member, leader, sponsor, director group, workgroup manager) that are involved in the teams.

Q. Can teams revisit their membership when finished with their charge?
A.  This seems reasonable, and it feels like an appropriate time to look at team memberships.  However, teams are not limited to this, and should revisit membership whenever it is necessary, for any reason.

Q. Should we require anyone without team training to take it, even if not currently slated to be on a team?
A. Yes, that is the plan.

Q. Can we implement a system for rotating members off teams?
A. This issue definitely needs more thought and clarity.  Membership on a team was never intended to be a life sentence, and we certainly want team members to be enthusiastic about being on the team.  Whether or not we institute a (renewable) term length is an open question, but at any rate we should clarify this idea (that serving on a team can have an end date) so everyone is aware of it.

Q. Is team membership an implicit requirement for staff? Are certain staff members “exempt” from teams?
A. All staff should be considered as potential candidates for teams.  We try to match organizational needs with staff interests whenever possible, and we have to consider workloads as well, so staff involved with a particularly large project may be temporarily exempt from serving on a team.  But no one gets a permanent pass.

Q. Do all teams really last forever?  What’s that all about?
A. Teams are intended to address ongoing needs that can not be effectively handled by individual workgroups or areas.  Unlike, say, the intern program, they are not intended to simply deal with a short-term project need.  So the assumption is that most teams will be ongoing, until such time as the work changes, or the work becomes “routine-ized” to the extent that it is integrated (or there is a plan to integrate it, like the work of the digital archives team) into a workgroup’s duties.  However, the changing tech landscape, college priorities, etc. can all effect the team’s work and lifespan.

One interesting thing from our discussion about these issues was something Fred said.  Basically, it’s not the idea of the “team” itself that is important, but rather, the important thing is creating a culture of teamwork and “unmanaged harmony.” We might get to a point where collaboration is so second-nature to us that we no longer need teams.  That would probably be the ideal situation!  But I found it very interesting to hear this.

Paint It Black: Protesting SOPA & PIPA

If you go to the English version of Wikipedia this Wednesday, you’ll find that they have ‘gone dark’ in protest of proposed federal legislation that in the name of stopping on-line piracy would put in place a set of tools that many fear would result in, among other bad things, internet censorship. While we won’t be making our website go dark in solidarity, it seemed that the least we could do would be to provide visibility to this important protest of legislation that many of us find deeply troubling.

More readings on the topic can be found at .

Heads Up: Portal to Launch Monday

When you come to work Monday morning, you’ll see a variety of electronic and print announcements that the portal that we’ve been working on over the past few months has gone live. You can preview it at . I wanted to give everyone who might be asked questions or for help a heads up that with all this publicity, there will likely be questions. You can send those questions to or via the web at . Congratulations to the web services team in general and Matt LaFrance in particular for pulling this together!

The whole point is lost if you keep it a secret: Musings on the LIS Blog

There’s a great scene in Dr. Stangelove where the existence of the Russian’s doomsday machine is revealed, but at a moment when it is too late for its explosion to be stopped.

For those not familiar with the movie, the doomsday machine is a nuclear device that can destroy the entire planet in a single explosion, whose triggering is automated, and once triggered, can not be stopped. In this critical scene, Dr. Stangelove complains that the whole idea of having a doomsday machine only works if you tell someone that it exists. Having a secret doomsday device is not a very good strategy. As he points out, “the whole point is lost if you keep it a secret.”

I think about this insight often when I think about our efforts to communicate with our community, and with ourselves, about all of the services and resources that we make available. Without an effective way to allow people to know about what we provide for them, we risk spending lots of time and money on things that few will ever know about. Thinking about how we are going to communicate when we change something or add something should be integral to the process of changing or adding something.

One of the major ways we communicate what’s new and what’s changed is via the LIS Blog. In turn, some items from our blog find their way into MiddPoints, the LIS eNewsletter, and our Facebook and Twitter feeds.  On a monthly basis, a small group sifts through the LIS Blog to assemble the eNewsletter. Of late, we’ve found that despite all of the changes we’ve made to our services, there is no corresponding posting to point to. Over the years, we’ve tried various strategies for being systematic about always posting to the LIS Blog when there is something new or changed that we want our community to be aware of. We hope not to have to return to the days when we had to hound contributors. That was annoying for all involved. To that end, I turn the question over to you: what can we do across the organization to get into the habit of always posting to the LIS blog news about what’s new and what’s changed in order to avoid having to be heavy-handed about this?

A second question about the LIS Blog that I have is whether or not we should continue to run the blog as a public blog. WordPress, the software that powers the LIS Blog, is now able to easily cross-post items to other blogs (that’s how we get posts from the LIS Blog to MiddPoints).  I wonder if we ought to create an LIS-only Blog where we post and where we read, and then create a mechanism for selected posts to make their way to a public LIS Blog and to MiddPoints. The advantage of doing this is that I suspect we might be more apt to make comments, to try out ideas, and to share more insider information if we knew that only our colleagues in LIS would be able to read the posts and the comments. Am I alone in thinking that this might be a good idea? What other ways might we accomplish the goal of encouraging more contributions, more dialogue, and more communication within LIS? (If you don’t feel comfortable sharing your thoughts on the public LIS blog, send me an email!)

Notes from Manager and Team Leader’s Meeting: September 2011

Here are the notes from this month’s manager’s meeting:
  1. We reviewed and added to the ‘what’s new this fall’ document. (See )
  2. We reviewed the process for goal setting. All workgroup and team leaders will post their goals to the LIS strategic planning site by October 1. In addition, they will update their FY11 goals with a final status update by October 1. This year, we will check in on the status of goals on a quarterly basis.
  3. Mike talked about the theme for the year: the 4 Ss. They are simple, secure, stable, and sustainable. While we gear up for a more ambitious campus-wide technology planning that will start in the next year, this year we want to focus our attention on making what we have simpler for our users, more secure, more stable, and sustainable. While this theme will inform our approach, it is worth noting that we will no doubt also take on new projects that arise naturally either from these themes, or from demands from our campus partners.
  4. Chris Norris gave a tutorial on the latest version of the project directory. The new directory is using a platform called Roadmap. We have agreed that going forward, all LIS projects will be listed in the project directory.

What’s new or will be new this fall

When our undergraduate students return to campus in the upcoming days and weeks, they will face a set of changes to our environment, and will likely have questions about these changes. To help us all understand what has changed, and who to point to if there are questions about any of these things, we’ve put together this handy index of changes for your perusal and as a reference.

Current Changes to Know About

We’re launching a pilot project to provide mobile and tablet users a friendlier way to access our resources. This same project will also provide a customizable portal for desktop and laptop computers. Joe Antonioli can provide more information about this.

Campus Manager
We will be making significant changes to Campus Manager, the software we use to keep track of devices to our network. These changes will happen in mid to late September. Until then, we will likely not be using Campus Manager at all.

Virus Campaign
We’re starting a campaign to get 100% of all College machines to be regularly scanned for viruses. This may result in an increase in questions about how to use symantec. And to make matters even more complicated, we’re also looking at possibly replacing symantec with a different product. Stay tuned on that.

Summon (also added to 2010-11 Annual Report)
The library has implemented an integrated resource discovery system from Serials Solutions called Summon (go\summon).  Summon indexes over 90% of our library resources — MIDCAT, ContentDM, online databases, indexes, and journals — in one combined resource, making it far easier than ever before to get a wide spectrum of results when searching.  Summon also offers tools for filtering search results that are similar (although, in some respects, more powerful) to those found on common websites such as

Music Library Move
In May, the library moved ca. 32000 music books and printed music, 21000 CDs, and 1500 DVDs from the Music Library in the Mahaney Center for the Arts to the Davis Family Library building.  Most of the printed materials are now located on the 3rd floor of Davis.  The CDs are behind the circulation desk (but available for check-out) and the DVDs, periodicals, and reference collection are being integrated into the main library’s collection.  The move when very well, a tribute to the fine planning done by the Space Team and others in the User Services and RCS areas.

Moodle and the Course Hub
We have just launched Moodle and the Course Hub ( and ) and are hosting training sessions for faculty for use this fall.

We’ve moved thousands of DVDs to the circulating collection, which means easier browsing and many more DVDs available to check out from the library.  We have also combined what was a “split” collection (meaning, some titles were classed using the Library of Congress classification system, and some were classed using a locally-developed system using the “MCTR” prefix), which will help reduce staff processing time.

Through a partnership with a company called EBL, the library has added ca. 44,000 eBooks to MIDCAT (go/midcat) that are now available to users “on-demand.”  Under this pilot project, users can access any of these titles from any networked computer and from many hand-held devices as well.  Titles that are accessed 4 or more times are automatically purchased by the library.  For titles that are accessed 1-3 times, the library is charged a small usage fee.  We do not incur costs for titles that are not accessed at all (or only very briefly), thus ensuring that the titles we purchase are titles that are needed and used.  We hope this results in added convenience for users as well as a way to more specifically target acquisitions dollars to materials that are actively used and needed.

iPad Loaners
We’ll soon be loaning out iPads in the way that we loan out laptops and cameras and other devices. If you haven’t yet had a chance to try out an iPad, you might consider taking one for a spin.

PaperCut for Copiers, too
We’ll be using papercut to allow copying as well as printing. Details to be posted on the wiki.

The return of loaning/borrowing audio CDs for Interlibrary Loan
With the move of the music library to Davis Family Library, we will resume loaning and borrowing audio CDs via Interlibrary Loan.

Four New Smart Classrooms in the MCFA
Over the summer, we built four new smart classrooms in the MCFA, one of which has a built-in video recording capability.

Mac Management Tool
We’ve launched a new mac management tool (called Caspar) that will allow us to do system management on Macs in the same way that we can with PCs.

Lynda Video Tutorials
The recently launched lynda video tutorials ( ) are proving to be very popular.

Menu Feeds
We’ve re-written the way the dining application works so that it is possible to see the ingredients of the food served at Middlebury’s dining halls.

On the Horizon

Banner Hosting
As many of you may have already heard, we are moving the hosting of Banner to a facility in Florida that SunGard manages. This won’t happen until much later in the fall. Stay tuned for more details on how this change will impact users of this system.

Stats Lab
If you see architects in the ground floor measuring things, that’s because we are planning to convert  Library 140 to a stats lab for use by the economics department and others.

Mission Continuity / Disaster Recovery
Process inventory work continues with identified functional areas of the College and soon, Monterey.