- Actively shaping expectations of those using the team's inputs
- Rapidly adjusting to changing situations
- Growing steadily stronger
- Has members growing as individuals
- Fueled by interpersonal commitments
- Work with a shared passion
In my recent experience, the team I worked with on the transition of maintenance responsibilities of select pieces of equipment had some of these elements present. We communicated very frankly on what we could and could not do, as well as just how long it could take. We also got very good at doing somewhat rapid overhauls of our slide decks to accommodate the preferences and requests of our leadership. Finally, we all had developed better individual understandings of the systems and procedures involved, and did our best to help each other out as a matter of principal. Admittedly though, the passion was somewhat lacking. Most of our interest in the project was the product of not wanting to be further hassled by our leadership, and the common mood was more getting what we could done and over with as the project was widely recognized to be rather difficult and cumbersome to work with.
On a further note of high performance team, Denning writes that in cases where there is a poor opinion of collaboration, there are other factors at work besides the concept itself. In part, he notes that systems for incentives and the like tend to be individually focused in nature, but he also adds that "...the root cause lies deeper: collaboration rests on values." Just because people are thrown together into a work unit with a common goal doesn't necessarily translate to believing in the same things. In the case of my most recent team project, we didn't exactly have much in the way of explicitly stated values per se, but we did seem to have in mind the common interest at least of minimizing frustrations for both ourselves and our respective units. We were also driven in part by the ever present values shared among us to do the best we could for the overall good of the unit and our mission set. I suppose you could say we were pragmatic about the whole thing, but we wanted to do good by our greater team as well.
Later in the same chapter, Denning discusses four distinct patterns of people working together, to include work groups (where every member has a task but doesn't necessarily need to collaborate), teams (where people work together with a very high degree of interaction), communities (people of a common value and interest set gathering), networks (acquainted individuals sharing information, but not necessarily building relationships).
I can think of a couple different experiences in discussing these patterns. During the course of my undergraduate education, I've run into a number of work groups and they weren't necessarily great experiences. Often times, we would divide the work between us and work on our respective pieces. We usually succeeded and got the job done in the end. However, like the book noted, there was not a great deal of collaboration and there was little to nothing developed in the way of developing a deeper rapport or getting to know our strengths and weaknesses. On the other hand, I've also had the opportunity more recently to work on something more akin to a team when I was working on an equipment transition team. Although I've said in the past this wasn't the most pleasant task and we were more driven by a desire to have it done and over with, we did in fact collaborate. Among the three of us young officers, we understood that each of us brought something to the table, whether it be knowledge of the systems or the ability to take decent notes. We also recognized the fact that we had to actively collaborate on behalf of our respective work centers, and we even got other people talking and collaborating. The good news out of all of this is that even as we got assigned other tasks to contend with, the project is still moving along fairly well considering the sheer scope and the limited timelines.