by Rick Brenner
Working in teams is necessary in most modern collaborations, but teamwork does carry risks. Here are some risks worth mitigating.
Three simple carabiners. A carabiner is a metal loop device used in climbing, rescue, and other safety-critical situations. Usually, one passes a rope or harness piece through the loop to secure it to something capable of suspending the load, which is usually a person. To make it convenient to pass the rope through the metal loop, the carabiner has a "gate" that opens to enable the rope to enter the loop without having to thread the rope through the loop end-first. In the pictured carabiners, the gates are spring-loaded. That is, one pushes the rope against the gate from the outside, and after the gate swings open, and the rope passes it, the gate springs shut capturing the rope until one presses on the gate from the outside once more, opening it. After the rope is captured, only a rare kind of accidental event can unintentionally free it.
So it is with deadlocks in teamwork. They form easily, but only a rare kind of accidental event can break the deadlock unintentionally. To intentionally break a deadlock that formed because of a dependency loop usually requires coordinated action and much intra-team communication.
Photo (cc) by Meanos.
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: Part 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 USD 19.95. Order Now! .
Your comments are welcome
Would you like to see your comments posted here? rbrentBQuxxKTZTGzZjMAner@ChacCkncZoNvhLjwCGRhoCanyon.comSend me your comments by email
, or by Web form
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
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.
More articles on Project Management:
- Remote Facilitation in Synchronous Contexts: Part II
- Facilitators of synchronous distributed meetings — meetings that occur in real time, via telephone or video — encounter problems that facilitators of face-to-face meetings do not. Here's Part II of a little catalog of those problems, and some suggestions for addressing them.
- The Injured Teammate: Part II
- You're a team lead, and one of the team members is suddenly very ill or has been severely injured. How do you handle it? Here are some suggestions for breaking the news to the team.
- Guidelines for Sharing "Resources"
- Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.
- Why Scope Expands: Part I
- Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?
- Deep Trouble and Getting Deeper
- Here's a catalog of actions people take when the projects they're leading are in deep trouble, and they're pretty sure there's no way out.
See also Project Management and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming Issues of Point Lookout
- Coming October 14: Contextual Causes of Conflict: Part II
- Too often we assume that the causes of destructive conflict lie in the behavior or personalities of the people directly participating in the conflict. Here's Part II of an exploration of causes that lie elsewhere. Available here and by RSS on October 14.
- And on October 21: Managing Wishful Thinking Risk
- When things go wrong, and we look back at how we got there, we must sometimes admit to wishful thinking. Here's a framework for managing the risk of wishful thinking. Available here and by RSS on October 21.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenscumjjrWrkiRMUDGner@ChacZiNtmghvHWAQRvCDoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: The Organizational Politics of Risk Management
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:
- Team Development for Leaders
- Teams at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program: