Showing posts with label team building. Show all posts
Showing posts with label team building. Show all posts

Monday, October 04, 2010

The Go.OSU URL Shortening Service: Agile Development in Practice

About a year ago, I wrote about the idea of a creating a University-branded URL shortening service. Late last month, a small team that I collaborated with at Ohio State launched such a service, called Go.OSU.

Right after I wrote my post last year, I created a short project description and shopped the idea around to potential partners. My primary selling point was that the service would leverage the authority of the OSU brand to the shortened URLs that are included in social media, publications, etc. Although I received a lot of positive feedback about the idea, many potential partners were caught up with other projects.

Since there was so much positive feedback on the idea, this Spring I shopped the idea to the Office of the CIO. While receptive, the OCIO suggested that I build a business case document for them to consider. The idea would be vetted through their review process and, if it past that first level of review, the idea would be placed on a list along with other projects seeking funding. The project would move ahead into development if it received funding, or if other support was identified.

Although I appreciate the reality that projects at that level of an organization need to fit into processes and workflow, my gut said that this review process could take at least a year. It wasn't a very agile approach for a such a lightweight project.

Later in the Spring, I was walking through a hallway at a conference on campus when I heard my name mentioned. It was Beth Black, a University Libraries colleague, and Ted Hattemer, from University Marketing Communications, talking about the idea. I jumped into the conversation. In literally 10 minutes, a decision was made that the project would be developed jointly by UL and UMC and that Ted was on board as our (very supportive) sponsor.

No committee consensus.
No formal meeting.
No user survey / needs analysis.

A few weeks later Jim Muir, a developer on Beth's team, demoed for the project team a working prototype. A few weeks! How agile is that?

We pounded on it for a couple weeks and sent Jim all our feedback so he could make changes. Ted brought in one of his designers, Jim Burgoon, to assist the other Jim with the interface design. The project didn't move ahead too quickly over that next couple months due to competing priorities. The project regained momentum in the early summer and was finally launched after we addressed security and legal issues.

Libraries are always talking about the need to be innovative and to take advantage of emerging technologies. Yet, they slow it all down by forcing ideas and fledgling projects to go through formalized systems. As this project shows, innovation is not born in committee and through process. It is born from half-baked ideas and serendipitous meetings and grows by NOT adhering to formal processes or traditional methodologies.
Sphere: Related Content

Thursday, April 09, 2009

OSU Library Labs: Concept to Production in 90 Days

The number of libraries discussing the concepts of agile development, perpetual beta, and rapid prototyping is encouraging. The one thing that all of these approaches have in common is the idea of including customers as active participants in the development and/or testing of new products and services. To that end, many libraries have created library labs sites to distribute various experimental and half-baked tools and gadgets.

A library lab allows an academic library to introduce new services at any time, not just during the three week window between semesters or when the services are ‘perfected.’ It creates an environment for users to experiment with new services. It is a showcase for projects under development or consideration. There is really no limit to what can be put on a labs site, nor is it limited to just technology solutions. A labs site allows a library to invest just enough resources to see if the idea is worth investing in, or let go of prototypes in a dignified manner.

The idea of an OSU labs site has been kicked around internally for at least a year. The challenge was other projects and job responsibilities kept the project in concept mode. Well, today we soft-launched OSU Library Labs.

In late January, as I prepared to transition to my new emerging technologies role, I assembled a small team of five people to (finally) move the project forward. The team members were selected based on both their interest in emerging technologies and in doing a project, well, differently. Since the project was outside the responsibilities of the team members, and that we have a traditionally organizational structure, I worked on an elevator talk (um, err, email) to present to the appropriate managers to gain 'permission' for staff involvement. Fortunately, everyone was excited by the project concept.

Once the initial team was assembled, the first thing we discussed was the need to work against natural tendencies of wanting to get buy-in at all levels and creating the perfect service. This was actually harder than one would think and surprising since we had no outside pressures. In fact, we had support for doing things differently. Goes to show how old behaviors are hard to change.

Once we granted ourselves permission to behave differently, the team decided to work on two-week deadlines. We met in person four times for an hour each. We kept things as simple as possible and kept catching ourselves when we began to over think or over plan. As the title states, it took us 90-days from the first time we began discussions to the posting of our "Hello World" entry.

The team has already gotten props for how fast we got the project up and online. Congrats team! Sphere: Related Content

Monday, November 24, 2008

Moving Towards an Innovative Library

I have been working for a couple months on a graphic that represents the elements of innovative library organizations. The one I came up with was inspired by that which appeared in The Game Changer.

The graphic below depicts a continuum of six concepts which are vital to building a more innovative organization.




Inspiring Leadership

In trying to determine where the continuum in the above model begins, I decided it begins with leadership. Leadership sets the tone for everything that a library does. Innovation is all about change. During times of change an organization will be unstable, characterized by confusion, fear, a temporary loss of direction, reduced personal productivity, and a general lack of clarity about the organization's direction and mandates. A time of change can be a period filled with emotion, with employees focusing on what is changing and being lost and therefore unable to look into beyond the present and into the future. Employees not only need to have confidence in their leadership so they have someone to look to during times of change, they need to be inspired by them.

While a director or formal management group may be the most visible leaders, most library organizations have leaders throughout. Innovative organizations would also seem to have a higher number of change agents and idea champions. As Helene Blowers points out, Innovation starts with 'I.' The challenge is identifying innovation leaders, cultivating their potential, and empowering them to act. While these individuals may not be leaders in the hierarchical sense, they are extremely important leaders in building staff buy-in and moving ideas ahead. It therefore takes inspiring leadership to spot and cultivate organizational leaders.

Courageous Culture

If leadership is the starting point of the innovative continuum, then creating a courageous culture is the foundation. A climate and culture that conducive to innovation will generally be open to change, willing to take risks, tolerant of debate and disagreement, playful, will stress flexibility, adaptability, and celebrate both individual and group achievements and failures.

When it comes to implementing innovative change, there is an inevitable resistance as individuals discover that they may be giving something up. In many organizations, simply suggesting a change is often met with a negative attitude. Nothing is more deadening to the innovative process than having idea shot down even before it has a chance. A change in culture, behavior patterns and how change is approached are critical to moving towards an innovative organization.

Training and Development

Sir Francis Bacon is quoted as saying "Knowledge is Power." Indeed, innovative organizations have knowledgeable staff equipped with the skills they need to innovate and perform. An organization looking to become more innovative should expect, no, require that it's staff advances their understanding and broaden their point of view beyond their individual responsibilities.

To that end, many library organizations are moving towards a competency-based assessment system which recognizes individualized learning styles and methods. In this model, every employee and their supervisor should be accountable for continuous learning with training goals spelled out in annual performance reviews. Exploring and refining new skills, ideally outside of their area of expertise, should be of high value to the organization.

Enabling Organizational Structures

Most mature organizations, and libraries certainly are that, reach a sustaining level where the focus is on efficiency. Employees are slotted into specialized roles and are gathered together in social groups based on those roles and the resulting processes. Therefore, each employee's web of social connections mirrors the way their work is organized. As Chris Trimble points out, most social connections are made with others with closely related specialties, which share similar perspectives, and are shaped by the demands of the same customers.

Being a part of a particular social network for a prolonged period of time does influence individuals in significant ways, such as internalizing the "ways of thinking" (groupthink) of that network. Yet, innovation initiatives are often most successful when there is an unusual interaction between employees. How do many brainstorming or strategic planning sessions start off? By counting off and creating new groups. Otherwise, people tend to organize into the same social groups.

Organizations that are unstable, or responding to instability, are also more likely to innovate. A constant of slight discomfort gets individuals out of their comfort zones, gets them talking to one another, and can create new connections where none previously existed. Trimble states:
"Breaking networks is the only way to prepare an organization to take innovation efforts beyond mere ideas. You can train an individual about what an innovation is and why it demands different behavior, but you can't retrain an organization simply by training the individuals within it. The individuals may acquire knowledge, but organizations are more powerful than individuals..."

Streamlined Processes

Andrew Van De Ven observes that people and organizations are largely designed to focus on, harvest, and protect existing practices than paying attention to developing new ideas. The more successful an organization is, the more difficult this becomes. Clayton Christensen echoes this theory. While the process of conceiving an idea may be an individual activity, innovation is a collective achievement of pushing and riding those ideas.

Transforming innovation into practice involves so many individuals that those involved may lose sight of the big picture. Innovation transforms the structure and practices of an organization. The challenge is creating a culture where process does not get in the way of innovation.

Resource Reallocation

Many innovative ideas die simply due to limited resources. While resources are often equated with dollars, resources also refers to the reallocation of time, people, materials, existing equipment, and assistance. To become more innovative, inspired library leaders need to reposition staff to support innovative projects and programs, through new hires and reassignments where appropriate.

The efforts of staff that develop successful systems should also be rewarded. Innovation activities need to be recognized when decisions are made about merit increases, promotions, and even tenure decisions. If such rewards exist, then more staff will be interested in engaging in innovative activities. In the end, participation in the development of innovative solutions needs to become a vital part of the librarian's career track, and as such, should be reflected in how the librarians work, and resulting scholarship, is defined and evaluated.
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

Tuesday, June 17, 2008

Does the Medici Effect Work for Libraries?

The Medicis were a banking family in Florence that funded sculptors, scientists, poets, painters, and architects among others. Individuals from many disciplines converged upon the city of Florence where they learned from one another while breaking down barriers between disciplines. They forged a world based on new ideas and created what we know as as the Renaissance.

In his book The Medici Effect, author Frans Johansson discusses how he sees the drivers of innovation as being diversity and the intersection of disciplines.
"The key difference between a field and an intersection of fields lies in how concepts within them are combined... If you operate within a field, you primarily are able to combine concepts within that particular field, generating ideas that evolve along a particular direction -- what I call directional ideas. When you step into the Intersection, you can combine concepts between multiple fields, generating ideas that leap in new directions -- what I call intersectional ideas."
Most individuals are predisposed to using directional thinking when faced with a problem or challenge. Solutions based on the intersection of ideas requires breaking down the barriers between traditional methods, fields, and disciplines. Intersectional ideas are important because they have the potential to create what Clayton Christensen calls disruptive innovations.

We recently interviewed candidates for our open Library Director (technically an AVP) position. I asked about how one goes about changing the culture of a library from one being focused on planning and makings sure everything we do is right the first time to a culture in which half-baked ideas and failure are permissible.

One candidate responded that the culture needs to be changed from the inside out. When asked for an example, they describe a situation where they intentionally hired a person with a technical services background to work in the circulation department. Their thinking was that the staff member would bring to the circulation department a perceptive based on the technical services discipline. The result was that new ideas and processes developed. The candidate intentionally created a new intersection, which resulted in a mini-Medici Effect, if you will.

Libraries looking to become more innovative can do so by intentionally creating an environment/organization in the Medici Effect can occur. This can be accomplished very simply by strategic reassignment of staff in key areas as the candidate did.

On a much larger scale, a library can reorganize itself so that existing work/social networks are broken up, an approach that Johansson also suggests. Breaking networks takes a deliberate effort and is tricky because networks are made up of relationships between people, and relationships are cultivated over time. Social networks are built upon relationships that often go beyond work and becomes the foundation for trust. Breaking these social networks would mean disrupting the social capital that has been built within parts of the organization.

Still, one can build a strong argument that innovation is more likely to occur when an organization moves from one that aspires to enhance existing social networks to one that breaks them, then rebuilds them over again.

Photo "Medici statute" by Vic15 is available though the Creative Commons license Sphere: Related Content

Friday, May 09, 2008

MLA 2008 Conference Blogging Aggregated Feed

David Rothman pulled together a very cool Yahoo Pipes feed using Feedburner that aggregrates all of the MLA 2008 conference bloggers postings. The conference wiki has a feed as well, although I do not know when it was added since David indicated in his post that there wasn't one.

It also looks like David will be doing some neat audio/video stuff. I also plan to pull people aside and use the iSight on my MacBook to capture hallway talks.

We are trying to set up a schedule so all the bloggers do not appear at the same events. I guess it is a heads up to presenters that you may/will be blogged. I guess it is like a restaurant owner knowing that a critic will be dining. Since I am also presenting someone will be blogging about me!

Note to fellow bloggers: Should we get together sometime Saturday or early Sunday? While I know some of you, there are others I've never met. It will be great to put faces to blogs. 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

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, April 16, 2007

Five Characteristics Of A Functional Team

In an attempt to figure out how libraries can become more innovative much or my reading and postings of late have focused on the characteristics of innovative organizations. I have come across several works detailing the characteristics of unhealthy and dysfunctional organizations as a way to uncover those traits we do want.

To this end, I recently had the chance to read The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni. Now, I have the tendency to avoid non-fiction works that have titles with numbers in them since they are generally of the self help variety. So, I read it against my better judgement. I skipped over the fictional leadership story at first and went right to page 187 to get the message:

"building an innovative organization is possible, but very difficult since human behavior tendencies corrupt and breed dysfunctional politics within them. "

If you scan your environment you may find one or all of five following characteristics of a functional team at work:

- Focus on the achievement of collective results. In a functional team the team results are the most important goals. Successful leaders will focus on the results and make them clear for all to see, rewarding only the behaviors that contribute to the team and correcting those that don't. There will be problems when individual needs (ego, career development, or recognition) are put above the collective team goals. When team members focus on individual needs there is often a failure to:

- Hold one another accountable for delivering those plans of action. Team members that are close to one another will also hesitate to make them accountable since they do not want to risk personal relationships. The failure to call their peers out on actions and behaviors that seem counterproductive to the good of the team leads to a lack of accountability. The enemy of accountability is ambiguity.Leaders need to make it clear what the standards are, what needs to get done, by who and by when. The lack of accountability results in a lack of:

- Commitment to decisions and plans of actions. Teams that do not have accountability spend much time “off-line” making decisions that the group does not commit to. Many times team members will feign agreement in meetings or creating ambiguity about their particular direction and priorities. Leaders can facilitate building commitment by reviewing all key decisions and making responsibilities and deadlines clear. There can be no commitment if team members do not:

- Engage in unfiltered conflict around ideas. One can tell how healthy an organization is simply by attending a meeting and observing how open the debate is (or isn't). Healthy and productive teams accept that conflict is a normal part of being in a team to learn to deal with it productively. All meaningful relationships require productive conflict for them to grow. Teams become dysfunctional when they are unable to productively deal with conflict or replace conflict with an artificial harmony. Leaders need to understand the importance of conflict and help team members learn about and develop positive conflict resolution skills. There can not be open conflict if team members do not:

- Trust one another. The key to overcoming a lack of trust is through shared experiences. Yet, too often team members are simply not genuinely open with one another and so not open up since doing so may result in the loss of some political advantage or being as seen as vulnerable. The primary role of the leader in building trust is to lead by example and create an environment where it’s safe to be vulnerable.

So, in summary, when team members make decisions based on their own interests there grows a lack of accountability. When there is a lack of accountability for decisions it is difficult for team members to become committed to those decisions. Without commitment team members may be unwilling to engage in honest debate and compromise. Without open debate it is almost impossible to build trust; the foundation on which all functional groups are built. 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