Team Risks

Teams enable us to do things we could never accomplish working individually — or if we could accomplish them, they would just take too long to be worth doing. For that reason alone, we need teams. But working in teams carries with it risks that arise much more often than when we work as individuals. Here's a short catalog of these risks.

Runaway damage risk

The power of teamwork amplifies not only the team's ability to do good, but also its ability to do damage. When we produce wrong-headed output for whatever reason, we must undo the damage we do. But before recognizing what happened, a team can do much more damage than an individual can.

Interpersonal conflict risk

When there are interpersonal problems in teams, everyone's productivity can be degraded. And the conflict might be unrelated to the work at hand. It can be a residual effect of a previous effort, or it can arise from something as unrelated to the work as unfounded rumors of changes in office assignments.

Decision-making risk

The word team means different things to different people. For example, with respect to decision processes, some of us believe that team means that each person's opinion is of equal weight. Others are searching only for work to do, and will do that work without question. Teams must define their decision processes for corresponding classes of situations. If they don't, each member will assume that their preferred decision process is in force. That difference in expectations can lead to interpersonal conflict. See "Decisions, Decisions: I," Point Lookout for November 17, 2004, for a summary of common decision processes.

Coordination risk

Teamwork is inherently parallel. The working members of the team assume that the parts they're working on will fit with the parts other people are working on. If a problem develops, and one of the parts has to be revised, some of the work already completed might have to be done again. This possibility is much less likely when a single person does all the work, because that person is presumably aware of all that has been done or will be done. Coordination risk is highest when interpersonal communication is the least effective, or when uncertainty is greatest.

Wariness risk

Inherent in The power of teamwork amplifies
not only the team's ability to do
good, but also its ability to do damageparallelism is the need to trust that teammates working on other elements are honoring their commitments. That is, we give our all to one portion of the work, trusting teammates to do the same with theirs. If trust is absent, and people become wary, they devote some of their efforts to protecting themselves from blame. That is what makes wariness so expensive.

Intra-task deadlock risk

Within the team's task, deadlock occurs when some members of the team are waiting for the output of one or more of the rest of the team. The whole thing can lock up if a dependency loop develops. If a subtask is late because of unanticipated difficulty or lost workdays, the rest of the team can become stuck.

Team-based development is different from the scaled-up effort of a single individual. Think it through carefully.  Top    Next Issue

Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Project Management:

Dispersity Adversity

Geographically and culturally dispersed project teams are increasingly common, as we become more travel-averse and more bedazzled by communication technology. But people really do work better together face-to-face. Here are some tips for managing dispersed teams.

Emergency Problem Solving

In emergencies, group problem solving is unusually challenging, especially if lives, careers, or companies depend on finding a solution immediately. Here are some tips for members of teams that are solving problems in emergencies.

Nonlinear Work: When Superposition Fails

Much of the work we do is confounding, because we consistently underestimate the effort involved, the resources required, and the time required to get it done. The failure of superposition can be one reason why we get it wrong.

Defect Streams and Their Sources

Regarding defects as elements of a stream provides a perspective that aids in identifying causes other than negligence. Examples of root causes are unfunded mandates, misallocation of the cost of procedure competence, and frequent changes in procedures.

Joint Leadership Teams: Risks

Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams of two or more. They face special risks that arise from the organizations that host them, from the teams they lead, or from within the joint leadership team itself.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info