Showing posts with label leadership. Show all posts
Showing posts with label leadership. Show all posts

Monday, February 09, 2009

New Responsibilities: Emerging Technology

Over the past year, I have been working with library leadership on the creation of a new role for me within our Library system. As is the case in many Universities, the health sciences library I work at is administratively separate from the main University Libraries (OSUL) . While a part of the libraries system, our only formal relationship with OSUL is though our faculty appointments.

The piece which took a little while to work through is an experimental and very interesting (and innovative?) job/time swap with OSUL. My new position description is below.

One of the challenges I saw in our library is that we simply do not have enough librarians to do a great job on many of the new information services and initiatives underway, such as a liaison program and what I call embedded reference. I also have observed from a distance that OSUL could benefit from more hands to handle IT-oriented projects. Additionally, I observed that both organizations were further challenged trying to keep staff up-to-date with various technologies.

So, as I was building the job description, I proposed the idea of a time swap in which I would work with OSUL and that a subject librarian from OSUL would assist with the new information services. This is the first time during my 16-year-tenure here that such an arrangement with OSUL has been suggested or made. The OSUL leadership was very supportive of the idea and have been really accommodating. The timing was perfect since the President of the University has been touting the idea of 'one campus' over the past year.

I know there are others out there with a similar title and responsibilities, and in some ways we are late to the party. But, we made it....

Emerging Technologies and Services Specialist

25% Spearheads efforts to enhance services through implementation of innovative customer-centered solutions; integrates technologies such as social networking, virtual reference, mobile technologies, and other Web 2.0 applications; directs cross-department project-oriented implementation teams; investigates and obtains external funding and serves as the Principal Investigator on related projects; participates in collaborative emerging technology projects within the University Libraries, the Colleges of the Health Sciences, the Medical Center, the Office of CIO, and TELR; collaborates in the design of assessment tools.

20% Shares knowledge about emerging and emergent technologies through formal and informal educational activities; collaborates with educational technology specialists in the application of emergent technologies in instructional and research activities; prepares presentations for leadership groups; serves as a resource for subject specialists / liaisons in the identification and application of technologies within their disciplines; creates customer-centered materials and activities as needed.

20% Serves as an emerging technologies specialist for the University Libraries; works closely and in consort with University Libraries IT Department leadership.

20% Faculty unassigned time for research, scholarship and professional service activities.

15% Serves as an explorer of, and champion for, the use of emerging and emergent technologies as part of the Prior Health Sciences Library and Center for Knowledge Management’s commitment to research, instruction, and knowledge transfer; keeps current in the latest developments in library technology, web-based support, and other emerging technologies; serves as a staff expert on technological trends and equipment in the marketplace and will articulate how these trends will impact and enhance the services; Sphere: Related Content

Monday, October 13, 2008

Consensus Building Cripples Library Innovation

I am not a fan of consensus building, an approach that is common in many, if not most, library organizations. While such an approach can be effective for small groups it has a number of shortcomings in larger groups, or if used to manage an organization.

One of the problems I have with consensus building is that an individual or a small minority can effectively block agreement to a proposal or idea. It unfairly tips the decision-making scales towards a staff member who may simply like the existing conditions, which may continue to exist long after the majority would like the conditions changed. Consensus building has the potential to reward the least accommodating group or staff members while punishing those trying to innovate. 

By giving all group or staff members the right to block any idea or proposal, an organization can essentially be held hostage to an inflexible minority or an individual. The impact this has on a library's ability to create innovative library services can be significant since creative or alternative ideas can be blocked or slowed by a small minority.

Consensus building also focuses on the need to discuss the topic ad nauseam and the need to seek the input of anyone would could possibly be affected.  This turns decision making into a very time-consuming process. This poses a liability to organizations trying to become more innovative since decisions often need to be made quickly. Since innovative process often result in half -baked solutions, it is simply not feasible to incorporate the opinions of everyone who could be affected in a reasonable period of time.
 
Library organizations probably migrate to consensus building since they generally want to work towards agreement, not disagreement. Yet, innovative organizations more often create atmospheres in which there is a great deal of disagreement and debate. Staff in innovative organizations learn how to disagree and build up a tolerance for disagreement. In such organizations, everyone is encouraged to act based on their individual motivations, and are rewarded simply for acting, rather than for success or failure. If libraries wish to create a culture innovation, we must 'allow' staff with the desire and energy to act on their own vision. This means that libraries must also empower staff to act by changing the system of rewards and support non-consensus decision-making processes.

Throughout history the most innovative ideas have been in opposition of the consensus opinion. According to Robert S. Root-Bernstein, the decision to go forward with an innovative idea should not be made because everyone agreed that it would work, but instead on different set of criteria: 
  • that it was controversial, striking at the heart of the field. (Libraries tend to want to avoid controversy) 
  • that it hasn’t been tried before and was therefore likely to yield new knowledge regardless of the outcome. (Libraries tend to wait until 'someone else' does it first and publishes it in the literature. And if it fails nobody will ever forget it did.)
  • that it was designed in such a way that it would easily be seen whether it worked or not (Libraries tend to over-think solutions and make things more complex then they need to be)
  • that the research was relatively inexpensive compared with the possible pay-off if success were to occur. (See above)
  • that the idea had a champion (or leader) who was willing and eager to risk his or her time and effort to implement the program. (Libraries support this notion, but there also needed to be a task force or committee with full representation and, oh, there still needs to be a consensus) 
Sphere: Related Content

Monday, September 08, 2008

Library Innovation Requires Regularizing the Irregular

To move towards a move innovative organization requires experimentation, trial and error, doing new things, and breaking rules. Libraries looking to become more innovative are confronted with reality: it takes 100 crazy ideas to find 10 worth funding experimentally in order to identify 1 project worth pursuing. As it has been said, it takes a lot of acorns to grow an oak tree.

The challenge is that most library organizations are structured and managed to continue current practices rather for than for innovation. Both strategy and resource alignment are focused on supporting short term missions and goals. This holds library organizations captive to a culture that is antagonistic toward innovation. Such a culture kills most attempts at innovation and can eventually drive innovative individuals away. It is not that the individuals within a library do not want to innovate, they talk about it all the time. Simply put, the structure of library organizations and their approach to management may make them unwittingly systematically hostile to innovation.

Gary Hamel notes that that the bottleneck within an organization that ultimately throttles innovation is almost always located at the top. Organizations are trained to look to the top for clues about where it's going. In such organization the vast majority of people have simply ceded responsibility for innovation. When the authority to set strategy and direction is held so narrowly then attempts at innovation inevitably falter. Therefore, new voices and new thinking are essential for a library to create a culture of innovation.

In his book The Future of Management, Hamel discusses new management principles which can help transform a library into a more innovative culture, including:
  • variety, diversity, experimentation, depoliticizing / depolarization of decision making
  • resource allocation flexibility
  • enabling activism through democracy (devolution of accountability, distributed leadership, unalienable >
  • engagement and mobilization through a common cause
  • increasing the odds and successful contribution of serendipity
Other interesting quotes from Hamel:
“To a large extent, managers play the role of parents, school principles, crossing guards and hall monitors. They employ control from without because employees have been deprived of the ability to exercise control from within. Adolescents outgrow most of these constraining influences; employees often aren’t given that chance. The result: disaffection. Adults enjoy being treated like 13-year olds even less than 13-year olds.”

“One can fairly describe the development of modern management as an unending quest to regularize the irregular, starting with errant and disorderly employees. Increasingly, though, we live in an irregular world, where irregular people take advantage of irregular events and use irregular means to produce irregular products that yield irregular profits.”

“Try to imagine what a democracy of ideas would look like. Employees would feel free to share their thoughts and opinions, however politically charged they might be. No single gatekeeper would be allowed to quash an idea or set the boundaries on its
dissemination. New ideas would be given the chance to garner support before being voted up or down by senior execs. The internal debate about strategy, direction and policy would be open, vigorous, and uncensored. Maybe this sounds hopelessly romantic, but such a thoughtocracy already exists—not in any big company, but on the web.”

"When you step on a treadmill and start to jog, your heart automatically increases the blood supply to your muscles. When you stand up in front of an audience to speak, your adrenal gland spontaneously pumps out a hormone that accelerates your heart rate and heightens your faculties. And when you glance at someone who is physically attractive to you, your pupils dilate reflexively, drinking in the agreeable visage. Automatic. Spontaneous. Reflexive. These aren’t the words we typically use to describe deep change in large organizations. And therein lies the challenge: to make deep change more of an autonomic process—to build organizations that are capable of continuous self-renewal in the absence of a crisis."

Sphere: Related Content

Monday, July 14, 2008

Using IDEAS to Create an Innovative Library

I have been reading The Game Changer by A.G. Lafley and Ram Charan. The book provides a different way of thinking about management processes to make innovation a central driver of a business. It draws upon the authors experience at Proctor and Gamble. There, they made building an innovative culture a fundamental part of the organizational strategy by using the concept of IDEAS.

Inclusive - the benefits of diverse thinking and ideas

Decisive - eliminating organizational debate and overanalysis to enable faster innovation development

External
- being in touch with customers

Agile - able to react quickly to changing customer and market conditions and taking calculated risks

Simple - ongoing streamlining and simplification of structures and processes.
I think that libraries do the inclusive and external parts very well. However, we have a lot of work to on being decisive, agile, and simple.

In fact, we tend to have very specific processes and procedures (committees; task forces) to encourage debate and overanalysis (all areas must be represented) which prevents us from being agile (12-18 month development cycle).

The book also reinforces two other characteristics of innovation that I have learned. First, innovation is not about the end product. It is not about the widget produced. Instead, innovation is all about the new interpersonal connections and the intersection of ideas which emerge.

Second, leadership plays a very important role. Leadership does not mean the administrative organization. Instead, it is about building a pipeline of leaders which allow a culture of innovation to grow and be sustained. These leaders can exist at any level of an organization. They must be given opportunities to lead and learn. Sphere: Related Content

Tuesday, June 10, 2008

Three Perspectives on Innovation

I have been given a great opportunity to lead an innovation task force for Ohio State University Libraries. The TF is one of several the resulted from a day long planning session held back in April. The goal of each of the TF is to help the library create a five year plan. I am planing to create a series of posts based on the TF activities.

The following are several perspectives on innovation the TF has uncovered:

Michael Schrage:
  • Innovation is more social than personal. It is a byproduct of how well or poorly one plays with others. Behavior - not knowledge, not insight - drives innovation.
  • You can't be a serious innovator unless you are willing and able to play

Clayton Christensen:

  • You have to be careful which customers you listen to, and then you need to watch what they do, not listen to what they say."
  • The problem is when you say "listen to your customers," your customers are only going to lead you in a direction that they want to go in. Generally, that will never lead you to disruptive growth. You've got to find that new set of customers, and listen to them and follow them. That's the trick.

Andrew H. Van De Ven:

  • People and organizations are largely designed to focus on, harvest, and protect existing practices than pay attention to developing new ideas. The more successful an organization the more difficult this is. (Christensen echoes this theory)
  • While the innovation of conception process many be an individual activity, innovation is a collective achievement of pushing and riding those ideas.
  • The process of transforming innovation into practice involves so many individuals that those involved may lose sight of the big picture.
  • Innovations transform the structure and practices of an organization. The problem is creating an infrastructure conducive to innovation.
Sphere: Related Content

Monday, April 21, 2008

Tossing Technology Eggs

I had a chance to chat with Richard Akerman over lunch at the NISO conference last month.

During our conversation he made mention of the various position / white papers he has created over the years. What caught my ear was when he said he experiences about a two-year time delay between the time when he poses an idea and the time the same idea emerges from elsewhere in the organization. It is not until it reemerges that it gains organizational buy-in.

This made me feel good since this is the same idea lag time I generally experience. As I talked to other technology-oriented librarians this does seem to be the general trend. Add on another 6-12+ months of working through the logistics and politics of getting an idea off the ground the technology concept-to-release gap is about three-years.

Three years!? I can't think of another part of a library organization that such a delay is acceptable. For some reason with technology it is OK. But I digress.

In my Why Someone May Hate Your Ideas post I point to an egg and bird analogy, which I shared with Richard.

When technology staff tosses out half-baked ideas to library staff it is like tossing them an egg when they are expecting a bird.

Technology staff can look at the egg and see what will happen; the egg will hatch, the hatchling will grow and eventually learn to fly. It may eventually have eggs itself and the cycle is repeated. Since the library staff expected a bird they simply let it drop and splatter on the floor. Unless the library environment is very forgiving, an egg (a premature technology idea) will simply not survive.

At the same time, libraries can no longer wait two-years for an egg to hatch. As library technologists, we need to do a better job of tossing our staff and customers hatchlings (prototypes). The time has come for libraries need to carve out a part of their organizations to focus on creating Library Labs like the one at the National Library of Australia. It is a place in which prototypes and emerging ideas can be made available and tested. Sphere: Related Content

Wednesday, February 20, 2008

The Vanishing Librarian? Sound the Alarms!

John Berry's Library Journal article has been making the rounds internally here. Sound the alarms!? Nope. Either I am missing all the uproar on the blogs about this article, or there simply isn't any. The editorial is so misguided that I am not going to spend any time arguing the points made. Maybe others are feeling the same way.

As AL comments on the LJ site: "Is this John Berry or Michael Gorman!?!"

OK. One point.

Libraries need to take a lesson from the train industry, who met their demise because they thought they were in the business of trains, not transportation. Libraries can no longer afford to view themselves as being in the business of libraries; we are in the information business. As such, our organizations need to create innovative products, services, process, management styles, and organizational structures in order to remain relevant. Sphere: Related Content

Sunday, November 25, 2007

Is Your Library Tech Staff Friendly?

The LibrarianInBlack provides a nice summary of Jenny Benevento's presentation at Internet Librarian 2007 discussing the problems of tech-savvy librarians leaving libraries. Jenny cautions that libraries need to be careful about keeping tech-savvy people in the profession. Some of the things that contribute to negative environments for techies in libraries include (my modifications/enhancement/creative liberties in italic):

  • Creating a organizational culture where technology and library staff are not put into a position where they can (have to) gain respect for each other's uniqueness
  • Adopt technology just because of the buzzword aspect. Make the implementation a high priority
  • Hop on Internet trends two years after they happened and 18 months after your technology person suggested them, rinse and repeat
  • Include the workplace luddite on all technology projects with the expectation that the individual will change or somehow assimilate the technology
  • Under resource and underpay your technology staff
  • Don't fund projects yet expect them to be important services
  • Tell techies that you want new technology, but reject all change that they suggest.
  • Don't make an effort to understand emerging technologies, but expect the techie to create, implement, and manage new services based on them.
  • Equate all technical knowledge--it's all interchangeable; all techies know everything. For example, desktop support staff can manage firewall issues.
  • Expect your techie to keep all staff up-to-date on emerging technologies and still investigate, implement, and maintain it.
  • Expect all tech requests to happen immediately
Sphere: Related Content

Wednesday, November 07, 2007

Revisited: Are OSS4Lib Networks Needed?

Over a year ago, I posted a piece entitled Are OSS4Lib Networks Needed? I argued that libraries have traditionally banded together to pool resources with the common goals of obtaining monographs, serials, and databases as economical as possible. The decision to develop or become involved with a library network is to affect a positive change on a library’s ability to plan and budget.

Unlike these cooperative efforts of the past, libraries have chosen to work independently on information system solutions. So, I asked this question: With the significant costs involved in the purchasing and maintenance commercial information systems why haven't more libraries banded together to build library systems?

A post by Joe Lucia to NGC4Lib presents a compelling case in support of this concept. He discusses a shift from an investment in commercial software support to a collaborative support environment for open source applications facilitated by regional networks.
"It is frightening for many to contemplate the leap to open source, but if there were a clear process and well-defined path, with technical partners able to provide assistance through the regional networks, I suspect some of the hesitancy to make this move, even among smaller libraries, might dissipate quickly... The success models are there and developing best practice frameworks and implementation support methods that will scale will not be rocket science."

"What if, in the U.S., 50 ARL libraries, 20 large public libraries, 20 medium-sized academic libraries, and 20 Oberlin group libraries anted up one full-time technology position for collaborative open source development. That's 110 developers working on library applications with robust, quickly-implemented current Web technology -- not legacy stuff. There is not a company in the industry that I know of which has put that much technical effort into product development. With such a cohort of developers working in libraries on library technology needs -- and in light of the creativity and thoughtfulness evident on forums like this one -- I think we would quickly see radical change in the library technology arena. Instead of being technology followers, I venture to say that libraries might once again become leaders. Let's add to the pool some talent from beyond the U.S. -- say ! 20 libraries in Canada, 10 in Australia, and 10 in the U.K. put staff into the pool. We've now got 150 developers in this little start-up. Then we begin pouring our current software support funds into regional collaboratives. Within a year or two, we could be re-directing 10s of millions of dollars into regional technology development partnerships sponsored by and housed within the regional consortia, supporting and extending the work of libraries. The potential for innovation and rapid deployment of new tools boggles the mind. The resources at our disposal in this scenario dwarf what any software vendor in our small application space is ever going to support...

I couldn't have said it any better.

The State of Ohio has a great resource in OhioLink. OhioLink is a consortium of 86 Ohio college and university libraries, and the State Library of Ohio, that work together to provide Ohio students, faculty and researchers with the information they need for teaching and research. Serving more than 600,000 students, faculty, and staff at all 87 institutions, OhioLINK’s membership includes 16 public/research universities, 23 community/technical colleges, 47 private colleges and the State Library of Ohio.

I have been in discussions for over the years involving concepts like a state-wide electronic document delivery system. They go nowhere. Right now, much of the technical site of the OhioLink system lies on the shoulders of Peter Murray and Thomas Dowling (There are a couple others, but they are the ones I know of) The usual response is they can provide a LAMP box for testing, but have no spare staff for development, let alone ongoing support. So, the question I have been posing for a while now is:

What if each of the 87 institutions provided 1/2 of an IT position to OhioLink as a condition of membership?

That would result in over 40 FTE developers. Not only would the state be able to build and maintain an vendor-based catalog system that uses open standards and service-oriented architecture, they could build other systems and services that could benefit the entire state rather then each struggling to find resources to do so. Imagine if each provided a full FTE!

The challenge that Joe will find is libraries are very protective of their IT resources. This issue became apparent to me in the question/answer period following my presentation at a Library 2.0 conference earlier this year. A library director asked how libraries can change from the siloed systems we currently have and adopt SOA. My response was essentially it is up to you! The discussion then turned to the limited numbers of IT human resources. (In my opinion, this is because too many library directors still equate all technical knowledge as being interchangeable and that all IT staff know everything. As a result, most libraries do not allocate enough resources into IT yet have high expectations of their limited staff. But, I digress.)

The challenge continues to be that libraries leaders/directors need to be willing to see the benefits and more importantly, willing to make the sacrifice. They control the resources and therefore hold all of the cards. So, having more of us out there talking to them like Joe, is key! (assuming, of course, that they are not in this communication space and not a part of the dialog).

There have been many of us out there evangelizing for over 10 years now, (Thanks, Dan Chudnov and Eric Lease Morgan, for helping me see the light!) and we are only now beginning to see some daylight. Sphere: Related Content

Tuesday, August 28, 2007

CAUTION: Paradigm Shift Ahead

As a librarian inclined to think that libraries are at risk, I am one of those open to many of the more radical ideas about how libraries need to change. Several of the other librarians I work with may gravitate towards ideas that support the traditional core values of librarianship and will reject those that involve redefining reference, circulation, and cataloging services. The resulting discussions are very intersting, if not polarizing.

I was just rereading a John Blyberg post about how librarians are drifting into two camps – those that believe libraries are in peril and those that don’t.
"Like two distinct brands of the same religion, librarians are drifting into two camps–those that believe libraries are in peril and those that don’t. Those who find themselves as a member of the former tend to feel that their libraries need to change in a number of fundamental ways in order to remain relevant. Those who identify with the latter group feel that good old-fashion librarianship is still what their users want or need. They’re the purists."
This brought me back to Thomas Kuhn's 1962 book The Structure of Scientific Revolutions, where he discusses paradigms as they relate to scientific discovery and evolution. It is the work which popularized the term 'paradigm shift.'

A scientific revolution occurs when an older paradigm is replaced whole or in part by an incompatible new one. When a new paradigm is revealed, the supporters of the new and old paradigms naturally argue in defense of their position. The emergence of a new paradigm affects the structure of the group that practices in a given field.

This is exactly what we are are experiencing in library science. We have the emergence of a new technology driven/focused definition of what a library is and is contrasted with the existing traditionalist definition highlighted by reference librarians sitting at desks. These are the two camps that John identifies.

According to Kuhn, scientific paradigms before and after a shift are so different that their theories are incomparable. It is impossible to construct a language that can be used to perform a neutral comparison between conflicting paradigms, because the very terms used belong to a the paradigm and are therefore different. In essence, a new paradigm cannot build on the preceding one, it can only supplant it. Advocates of mutually exclusive paradigms are in an impossible position:

"Though each may hope to convert the other to his way of seeing science and its problems, neither may hope to prove his case. The competition between paradigms is not the sort of battle that can be resolved by proof."
When an individual or group produces a synthesis that attracts the attention of the next generation of practioners, the older schools gradually disappear. In part, the disappearance is caused by the members conversion to the new paradigm:

"a new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it."
The next generation of library scientists graduating from library school will be hardwired to naturally accept the technology driven/focused definition of a library. If Kuhn is right, as the profession's retirement bubble bursts over the next few years the next generation should help complete the library science paradigm shift.

That is, until the next paradigm emerges. Sphere: Related Content

Wednesday, August 22, 2007

A Two Hour Meeting to Plan A One Hour Meeting?

I just read Alexander Johannesen's resignation from a library in Canberra, Australia. Mr. Johannesen is not a 'librarian' by training and admits that he is leaving libraries due to an incompatibility. So it goes.


"Every time I see a glimmer of hope or a flash of something exciting going on in the library world, it usually fast fades into a charades of politics and committee-shuffle. I'm too impatient for this, and I seriously think the world is, too ; it will race past us as we decide on who's going to chair what committee, who'll take notes, and how we're reporting progress to what group. Also since these glimmers of hope usually is attached to specific people more than institutions or organizations, whenever that person goes or moves, so does the glimmer. Again, because we're not traditionally in the business of technical development, we're so fragile..."


It is unfortunate that Mr. Johannesen is so frustrated. Yet, I do think that the perspective he offers as a programmer coming into the library profession is an important one. One could try to argue the culture and problems he encountered are unique to his library, but we all know better.

This quickly brought to mind Stephen Abram's quote:

"librarians like to process things to death, and death wasn't the original goal."

Just yesterday, I had lunch with a colleague who is not a librarian, but whose current and previous positions have allowed her to work closely with libraries and librarians. Our various discussion topics always seemed to loop back around to the culture of libraries, resistance to change, and the need to process EVERYTHING.

Another colleague also told me yesterday that earlier in the day they were in a two hour library meeting to discuss plans for a one hour meeting.

What's the deal with us, folks??!!

What also concerns me is that Mr. Johannesen is a self admitted "mid-life-crisis-aged" individual. What will happen when the younger generation begins to enter the profession? The next generation of library scientists graduating from library schools will be hardwired to naturally accept the technology driven/focused definition of a library. Will this culture embedded in the 'legacy' librarians reaching retirement bubble simply be handed off to the next generation, or, will the next generation finally force a culture shift?

I am fairly confident that Mr. Johannesen is not alone in his frustration about the library culture and maybe even with his unwillingness to wait for that shift to occur. Sphere: Related Content

Monday, July 23, 2007

Service-Oriented Library Systems Pt. 5: Final Comments

The web as we currently know it has been built using relatively simple technologies which have been proven to have scalability, efficiency and utility. The next generation web that is emerging will be an 'operating system' on which developers can create reusable and constantly updated information systems. Functionality that has been traditionally performed on systems installed and run on a local computer in a single application will be performed on the network involving many applications running on many computers.

The resulting information systems architecture is not the 'self-contained' single application structure that we have been used to. Instead, it is a Lego-like design of 'loosely coupled' systems referred to as service oriented architecture.

There is an agreement in the more general information systems world that the SOA approach is the way that applications need to be built. The adoption of SOA will not only make our library systems more flexible and agile, but will allow organizations to modernize their legacy applications.

In the “Introduction” of the 2006 issue of Library Technology Reports entitled “Web Services and the Service-Oriented Architecture” Marshall Breeding writes:


"If, in the future, libraries want to be isolated islands in the ocean of content and information, they can ignore Web services. But because much of what libraries do centers on providing information to library clientele and because information is increasingly more electronic—which causes libraries to overlap with many other organizations in the information sphere—it is necessary for libraries to cooperate and interact with a broad set of other organizations and their technical infrastructures. Web services provide mechanisms that allow libraries to expand their services in many important ways"


In order for libraries to take advantage of the benefits of SOA, some things will have to change. First and foremost, our library leaders need to refocus their collective vision. We need to rethink the services our libraries now offer and how those services are delivered. We need to realign human and fiscal resources into the development of new systems that can change and adapt as fast as our environment.

Libraries in general also need to reduce our reliance on proprietary systems. Sure, libraries can still have vendors build our systems, but we need to demand that they adopt a more open and modular approach in their designs. Our library leadership and professional organizations need to begin demanding that vendors use open standards and open up their APIs. Our library leadership and professional organizations also need to begin viewing open / community source products not only as alternative solutions, but as leverage to force vendors to adopt SOA.

For libraries to retain their market share in the networked world we need to embrace the SOA information approach, now. If libraries do not begin to adopt SOA soon we will not only remain three to five years behind the technology curve, we may never catch up.


RESOURCES:


CONTENTS:
Part One: Introduction
Part Two: What We Have Today
Part Three: Where Are We Heading?
Part Four: Challenges Sphere: Related Content

Monday, July 16, 2007

Service Oriented Library Systems Pt. 4: Challenges

In my three (1 2 3) SOLS posts I have provided a basic introduction to SOA and how it can be applied to the development of the next generation of library systems.

Historically, library information systems solutions have been built (almost) exclusively by vendors. While some libraries do build their own systems or use open source solutions, the large majority still rely upon vendors. Most of our challenges in implementing SOA are the direct result of this decision.

Commercial software developers rarely develop new products until they find a critical mass of users since they need to recoup development costs and make a profit at the same time in order to survive. The relatively limited size of the library system market makes it a difficult one for new vendors to enter. This means libraries have few choices when choosing software solutions and few libraries will switch once a significant investment in licensing, maintaining, and training support. When a library becomes so dependent on a vendor for products and services and cannot move to another vendor without substantial costs, whether real or perceived.

The first challenge to adopting SOA is that library systems vendors have created an effective paradigm that many libraries cannot afford to break away from. The vendors of key library systems understand the lock in phenomenon and libraries let them get away with it.

Many library vendors, if not most, build their solutions upon proprietary architectures. Some vendors are beginning to build their systems around some of the principles of SOA. Still, the core of what makes SOA work - the API - remains one of their their most tightly guarded core intellectual properties and revenue streams. The vendors place a death grip on those very APIs which would allow libraries to create SOLS using services provided by disparate systems.

The lack of compatibility between different library systems intentionally or unintentionally forces a customer to continue to use products and services from a particular vendor. Developers may design their products so that replacement parts or add-on enhancements must be purchased from the same manufacturer, rather than from a third party. Developers may also build in incompatibility between versions of their systems to force customers to upgrade.

The second challenge to adopting SOA is that the lack of compatibility and the API licensing fees charged to developers to create compatible products - required in SOA - creates a barrier for new vendors trying to enter the market for a particular library system. If the costs of entry or compatibility are great enough an effective monopoly can be maintained.

Libraries have built entire resource sharing networks around single vendor solutions. This results in a de facto standards. De facto library system standards are those which have been accepted for practical purposes by a significant proportion of the marketplace. What comes to mind is a significant library Internet document delivery network based on a product who's name is now a verb.

The third challenge to adopting SOA is that for work flow or legacy reasons we continue to support single vendor supplier solutions. In doing so, we create an environment where library products do not have to keep up with current technology needs, service support that does not meet expectations, and systems that will not allow for the adoption of SOA.

When one steps back and looks at it, we have nobody to blame for outdated library information systems or our inability to more readily adopt SOA except for ourselves. We keep licensing these products at a time when the number alternative approaches available to libraries has never been greater.

In the last posting in these services (no. 5) I will provide some closing remarks and observations.

CONTENTS:

Part One: Introduction
Part Two: What We Have Today
Part Three: Where Are We Heading?
Part Five: Final Comments Sphere: Related Content

Monday, June 18, 2007

Interview with Clayton Christensen (The Innovator's Dilemma)

Business Week's Jena McGregor recently interviewed Clayton Christensen to mark the 10-year anniversary of his book the Innovator's Dilemma.

I would highly recommend this book if you are involved in library IT or in a library leadership position. As you read it replace the phrase "hard drive industry" with "libraries" as I did. Doing so creates a new perceptive and meaning to the work.

Here are some snipits from the interview. (the italics are my emphasis)

"you have to be careful which customers you listen to, and then you need to watch what they do, not listen to what they say."

"The problem is when you say "listen to your customers," your customers are only going to lead you in a direction that they want to go in. Generally, that will never lead you to disruptive growth. You've got to find that new set of customers, and listen to them and follow them. That's the trick."

"People come up with lots of new ideas, but nothing happens. They get very disillusioned. Never does an idea pop out of a person's head as a completely fleshed-out business plan. It has to go through a process that will get approved and funded."

"... many of the programs we teach are fundamentally biased against innovation. There are just a whole bunch of paradigms of financial analysis that really lie at the root cause of companies' under-investments in innovation."

"It's hard for me to see what will disrupt Google. I think they've got a pretty good run ahead of them. "

"The iPhone is a sustaining technology relative to Nokia. In other words, Apple is leaping ahead on the sustaining curve [by building a better phone]. But the prediction of the theory would be that Apple won't succeed with the iPhone. They've launched an innovation that the existing players in the industry are heavily motivated to beat: It's not [truly] disruptive. History speaks pretty loudly on that, that the probability of success is going to be limited. "
Sphere: Related Content

Tuesday, June 12, 2007

OhioLINK's Tom Sanville Receives ASCLA Award

One of many reasons that it is great to be a librarian in Ohio (yes, there are many) is OhioLink. For the past fourteen years, Tom Sanville has served as OhioLINK's executive director. He also led the way for the partnership that created Libraries Connect Ohio and is one of the founders of the International Coalition of Library Consortia.

Tom's hallmark has been demonstrating that librarians can successfully negotiate with vendors. While having breakfast at a conference with a vendor representative last year he looked at the institution on my name tag. His first words were, with a hint of fear in his eyes, "Oh, you are from Ohio. I have had many tough negotiations with Tom Sanville."

I just received an email that Tom has been named the 2007 recipient of the Association for Specialized and Cooperative Library Agencies (ASCLA) Professional Achievement Award. This award is presented for professional achievement within the areas of consulting, networking, statewide service, and programs.

The award will be presented during the ALA Conference as part of the ASCLA President’s Program and Awards Ceremony, "Is Your Information Technology Accessible? Section 508 and Libraries," on Sunday, June 24, 10:30 a.m. - 12:30 p.m., at the Grand Hyatt Washington Hotel, Constitution B.

Congrats Tom! Sphere: Related Content

Wednesday, May 23, 2007

Library Information Systems Quicksand

When the Internet came of age over ten years ago libraries had few information systems choices. Creating software applications back then required fairly complicated development tools and a relatively high degree of programming skills. It was rare for a library to have staff with such skills. Libraries had little choice but to license technologies from vendors.

As the paradigms have changed so have the tools and protocols of application development. They have become very accessible. Still, from my vantage point libraries seem to continue to fall further behind. As a profession we seem to be stuck in information system quicksand.

One of the problems is that most of the vendors used proprietary technologies instead of those that support open standards. These closed systems which our vendors have provided us have made solutions such as federated and metasearching quite complicated, if not impossible, primarily since our systems can not talk to one another.

While libraries have embraced consortia solutions for most large scale purchases, the collective vision of library leadership has failed to see the potential for open systems development that would result in new library systems based on open standards. These systems could be built using an open architecture and shared with the library community. Community source, if you will.

At the very least, I believe our library leadership and professional organizations need to begin demanding that vendors begin using open standards and opening up their APIs. By continuing to embrace proprietary vendor solutions - as they decide to build them - we may be destined to remain two or three years behind the technology curve.

I do applaud those libraries that have abandoned traditional library ILS vendors like Ex Libris, Innovative Interfaces, and SirsiDynix and instead have embraced systems like Endeca and AquaBrowser. While the later are still vendor solutions at least they are offering solutions that libraries need now, not just talking and planning for "future enhancements." Sphere: Related Content

Monday, May 14, 2007

Managing Libraries by Crisis

Does the following scenario sound familiar?

You identify an issue within your organization but unable to get the support to solve it before it turns critical. You communicate the issue on several occasions and it is ignored, that is until the issue becomes a real crisis. Once the issue becomes a crisis it becomes THE organizational priority. Resources once unavailable to resolve the issue proactively are somehow made available. You are left saying to yourself (maybe out loud) "I identified and communicated that issue long ago many but nobody paid attention!"

This approach is what is referred to as management by crisis. It is a reactive method of management in which strategies are formulated as events occur.

In management by crisis, certain situations are known to exist within the organization but for a variety of reasons they are ignored or not seen as an immediate threats. In such an environment, planning doesn't occur and resources remain unallocated until the issue actually becomes a crisis. More time and resources are then spent to repair and manage by crisis then were required to prevent it. The New Orleans' levees come to mind.

This is a different concept than crisis management. Crisis management implies that the timing of a situation was relatively unpredictable. For example, an earthquake, tornado, or a zero-day virus attack. Crisis management forecasts a potential crisis and plans how how to manage it with a generic strategy based on experience and anticipation. As a crisis unfolds the manager identifies its nature and then intervenes using the plan in order to minimize damage and to expedite recovery.

In the Katrina example, FEMA (should have) served as a crisis management organization. In contrast, the US Army Corps of Engineers apparently managed the issue by crisis. They apparently were aware the levees would not hold years ago and failed to step in to do anything until after the disaster. They have spent significantly more to repair the broken levees than it would have taken to build them properly to begin with.

While it is a desirable trait for a leader to have a set of crisis management skills, it is not that uncommon to see leaders that manage by crisis. It is a type of leadership which is built on managing day-to-day issues and not on strategic planning. Some leaders may actually see the identification of a crisis, the action steps and resources allocated to resolve it, and the elimination of complaints as being an aggressive / proactive management style. In fact, it is a defensive / reactive / passive management approach.

One way to spot an organization that manages by crisis is when the success and direction of the organization is determined by the complaints they get. Those issues with the most complaints are given a high organizational priority. Project planning and decisions are guided by the potential for complaints.

When the complaints decrease the leadership pats itself on the back for dealing with the issue. The incorrect assumption is that no complaints means everything is fine. The Hawthorne Effect is also an issue in organizations managed by crisis: the increased attention to the crisis results in a temporary increase in effort focused on the issue.

Strategic planning is one way to break out of the management by crisis cycle. By creating a strategic plan and using it set direction many more issues can be properly anticipated. The result is a managerial approach that is more aggressive in nature and is focused in on managing change. When change is effectively managed it becomes a part of the organizational routine. The strategic plan becomes the road map for planning and critical issues can be addressed more proactively. Sphere: Related Content

Monday, April 30, 2007

Can Change Occur Despite the Unchangeable Library Administrator?

In his recent rant about changing the unchangeable, David Lee King posted some very important observations and asked for ideas to convince administrators that constant change and innovation is good, and that it’s also a necessity in our new millennial world.

Technology (still!) is a world of mystery for many administrators. Technology happens. The challenge is that if the library administrators do not make technology a critical part of the library's vision it will continue to be an after thought. Any change involving or resulting from technology will continue to be a struggle.

It some ways it is understandable. Given fiscal and administrative functions and responsibilities make it nearly impossible for administrators them to keep up with technology. As an IT professional even I am even challenged to keep pace. Expecting administrators without a technological aptitude to carve out time to understand technology is simply not realistic.

Maybe we need to focus instead on convincing administrators that technology leaders need to be a part of the strategic planning and decision making processes. Make them a part of the senior leadership team. This way the administration is constantly exposed to technology talk and some assimilation could occur. However, getting new individuals added to the leadership team could be as difficult as convincing adminstrators themselves. Being a part of a team also does not assure support for ideas, but at least it opens up new communication opportunities.

In the classic Diffusion of Innovations, Everett M. Rogers states that adopters of any new innovation or idea could be categorized as innovators (2.5%), early adopters (13.5%), early majority (34%), late majority (34%) and laggards (16%). Each adopter's willingness and ability to adopt an innovation would depend on their awareness, interest, evaluation, trial, and adoption.

While Rogers' research focused more on market driven products, I feel this categorization and breakdown also describes how change and innovation is accepted within a library organization. Based on the categorization the innovators, early adopters, and even the early majority are likely to have their own motivations to change. Half of the library organization (the late majority and laggards) is likely to demonstrate some sort of resistance to change. The problem occurs when the administrators are among this group.

To be a change agent one needs to work on the unmotivated people first and get them involve in the change process as early as possible. Through exposure they gain knowledge and understanding and are more likely to form of a favorable attitude that allows the change to move forward. Once this group becomes committed to the change the easily motivated will simply fall into place.

There has been many threads over the last year regarding the concept of Learning 2.0 . I wonder. If we are able to educate the staff on technology and related changes would administrators be exposed to technology and change in most daily discussions? Would even more assimilation occur? Could a library organization learn to embrace and adapt to change despite the administrators? Sphere: Related Content

Monday, May 22, 2006

Is Change in Libraries Evolutionary or Revolutionary?

In a recent post, Michael Casey discusses Pip Coburn's book called The Change Function and supports the author's position that for change to be successful it must be continuous, regular, and almost imperceptible:

"Successful change is not the old school variety of change that comes every few years and is accompanied by massive upheavals, frightened staff, and upset customers. Successful change is constant change, and constant change cannot be discontinuous or fractured. Constant change is fluid; it’s evolutionary, not revolutionary."

However, there are those who have successfully argued that the normal pattern of successful transition from one paradigm to another in the sciences is indeed via revolution. In all fairness, I am generally in line with Michael's viewpoints. While change needs to be relatively imperceptible to the customer, the way in which the profession itself changes is another issue.

In his 1962 book The Structure of Scientific Revolutions, author Thomas Kuhn discusses paradigms as they relate to scientific discovery and evolution and popularized the term paradigm shift. There are some interesting ideas that Kuhn discusses that are relevant to libraries and this discussion. While Structure has generated a good deal of controversy with many of Kuhn's ideas challenged, I feel his theories make sense relative to library science.

A paradigm is an acceptable model or pattern that gains its status because it is more successful than other concepts in solving problems. A scientific revolution occurs when an older paradigm is replaced whole or in part by an incompatible new one. When a new paradigm is revealed, the supporters of the new and old paradigms naturally argue in defense of their position. The emergence of a paradigm affects the structure of the group that practices in a given field.

This is exactly what we are are experiencing in library science. We have the emergence of a new technology driven/focused definition of what a library is and is contrasted with the existing traditionalist definition highlighted by the fact we still have reference librarians sitting at desks. The viewpoints of the two competing groups are reflected in part by the reaction to Michael Gorman's President's Message in the May 2006 issue of American Libraries.

Those practioners supporting the emerging technology driven/focused vision are creating a new community that utilizes new technologies to advance their ideas (e.g. blogging). Meanwhile, those holding onto the current paradigm fall back to traditional communication tools as evidenced in how one has to track down Mr. Gorman's piece in electronic format.

Scientific paradigms before and after a shift are so different that their theories are incomparable. The shift does not just change a single theory but changes the way that words are defined, the way that the scientists look at their subject and the questions and rules used. In essence, a new paradigm cannot build on the preceding one, it can only supplant it:

"the normal-scientific tradition that emerges from a scientific revolution is not only incompatible but actually incommensurable with that which has gone before."

Therefore it is simply not possible, according to Kuhn, to construct a language that can be used to perform a neutral comparison between conflicting paradigms, because the very terms used belong to a the paradigm and are therefore different in different paradigms. Advocates of mutually exclusive paradigms are in an impossible position:

"Though each may hope to convert the other to his way of seeing science and its problems, neither may hope to prove his case. The competition between paradigms is not the sort of battle that can be resolved by proof."

When an individual or group produces a synthesis that attracts the attention of the next generation of practioners, the older schools gradually disappear. In part, the disappearance is caused by the members conversion to the new paradigm. Those who cling onto the older viewpoint and are simply read out of the profession and must proceed in isolation or attach themselves to another group that does:

"a new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it."

The next generation of library scientists graduating from library school will be hardwired to naturally accept the technology driven/focused definition of a library. As the profession's retirement bubble bursts will the next generation force the paradigm shift? Is the shift occuring now? Is this a cyclical process resulting from natural evolution or from a revolution?

Regardless, librarianship has all the characteristics of and is ripe for a paradigm shift. Sphere: Related Content

Tuesday, April 25, 2006

Are Libraries Managing Innovation in a Disruptive World?

Librarians apply traditional methods and models to everything we do, including technology innovation. We must do surveys, formal needs assessments, focus groups, usability studies, before deciding on a technology. However, this traditional approach may be leading librarians right down the path to the Librarian's Dilemma.

In his paper Central Problems in the Management of Innovation Andrew H. Van De Ven points out that there are four factors that faciliate and inhibit innovation:
  • people and organizations are largely designed to focus on, harvest, and protect existing practices than pay attention to developing new ideas. The more successful an organization the more difficult this is. (Christensen echoes this theory)
  • while the innovation of conception process many be an individual activity, innovation is a collective achievement of pushing and riding those ideas.
  • the process of transforming innovation into practice involves so many individuals that those involved may lose sight of the big picture.
  • Innovations transform the structure and practices of an organization. The problem is creating an infrastructure conducive to innovation.

It is very difficult, if not impossible, to identify any of the requirements and needs for a potentially disruptive technology. This is because we do not know anything about the technology. Therefore, the goal of the innovation process in libraries should be one of learning and the exploration of new ideas and not meeting the needs of our current customers. In order to manage disruptive technologies, libraries need to adopt new organizations and processes that are much different than what we are used to. Where traditional processes consist of planning before action, managing disruptive technologies requires action before planning.

Like the hard drive manufacturers in Christensen's book, libraries need to create new organizations designed to facilitate innovation. These new organizations can be as simple as new emergening technology task forces or committees. There needs to be a deliberate reallocate of resources away from supporting routine services and towards supporting innovation. Libraries then need to adopt different standards for evaluating both routine work and innovation.

Innovation is based on guess-work, estimation, and hypothesis. To get technology innovations out much sooner short development cycles are needed. Rapid Prototyping is a development approach based on the assumption a library may know the objectives that they wish to address but not know all the nuances of the data or the details of the system features and capabilities. An assumption is made as to how the system might work and then rapid iterations are used to quickly incorporate suggested changes and build a usable system.

Below are some of the characteristic differences between managing sustaining and disruptive technologies:

SustainingDisruptive
Primary Question: What do customers need? What do customers do?
Needs Assessment: Surveys and focus groups Ethnography
Innovation Goal: Planning before action Action before planning
Innovation Outcome: Meeting current customer technology needs Learning and exploration
Innovation Process: Structured and linear Dynamic and spontaneous
Organizational Models: Traditional models and roles New structures and quick development cycles

What are libraries doing to create new organizations and processes? What are the best practices that we can look at? A visit to the Library Success: A Best Practice Wiki provided an interesting insight. While other sections of the wiki are built out, the section Management and Leadership contained virtually nothing.

Does this mean that there are no best practices? Or, are library administrators simple not contributing because they are not actively engaged in the use of potentially disruptive technology themselves? If library adminstrators do not understand the technology environment we are in how can they affect organizational and process change to foster innovation?

Resources:


Ruby on Rails. Ruby is a programming language just like Perl, Python or PHP. Rails is a web application framework written in the Ruby programming language. If you’re writing a Rails-based application, you’re writing Ruby code. Powerful web applications that formerly might have taken weeks or months to develop can be produced in a matter of days.

Sutton, Robert. "Why These Ideas Work, But Seem Weird" Design Management Review, Winter 2004 15(1):43-49

Van de Ven, Andrew H. "Central Problems in the Management of Innovation" Management Science, May 1986 32(5):590-607 Sphere: Related Content