People have been working in teams since before the word 'team' was invented, but modern industrial organizations have adopted the team structure in just the past generation. Because the transition from functional structures is still underway, our understanding of teams is incomplete, and in some ways, incorrect.
To advance our knowledge, and to become more comfortable with this relatively new way of organizing work, we adopt and propagate beliefs that seem plausible. They might apply often, but they aren't necessarily universal. I call them myths because their universal truth certainly is questionable, even though they do sometimes yield desirable results.
One popular example is the idea of the "Mythical Man-Month" conceived and popularized by Fred Brooks. This myth holds that we can speed up all work by applying more people to the task. The reverse usually occurs: applying more people usually slows the work.
Brooks's myth is just one of many teamwork myths. Here is the first in a series about teamwork myths, exploring two myths about team formation.
- There is an optimal size for all teams
- Various investigations have reported optimal sizes for teams, ranging from five to fifteen and more. In team-oriented organizations, wide variation in team size can create management problems, which lead some to search for an optimal team size.
- Problems arise, for example, in task reporting, management development, performance management, and compensation equity for team leads. For instance, meeting reporting requirements can be easy for a large team, but an undue burden for a small team.
- An optimal team size range probably does exist, but it depends on the culture of the organization in which the team is embedded; the degree of dispersion in geography, language, or profession; the need for specialized knowledge; the complexity of the task; the prevalence of split assignments; and the skill of the team's leadership. Most important is how well the teammates know each other.
- When sizing a new team, be guided not by purportedly universal rules of thumb, but by the nature of the task, the character of the organization and the particular people who lead and belong to the team.
- Team building is worthwhile only at the beginning
- We use team building to achieve team cohesion and effective collaboration. Some believe that after the first application, further investment in team cohesion provides only minimal returns.
- Although we do use team building in the beginning of the team's life, we must attend toWe must attend to team
cohesion continuously,
not just at the outset team cohesion continuously. The need increases with the frequency of changes in team composition; with increases in geographic dispersion; and with increases in stress. Stresses can result from new challenges, or from changes in resources, requirements, or constraints imposed from external sources.
Following erroneous guidelines is always problematic. It can be especially damaging during team formation, because damage occurs so early and repair can be so, so costly. Next in this series Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
For more teamwork myths, see "Teamwork Myths: Conflict," Point Lookout for June 17, 2009, and "Teamwork Myths: I vs. We," Point Lookout for July 1, 2009.
The Mythical Man-Month: Essays on Software Engineering is a classic of the literature of software engineering, but it has a place on the bookshelf of any project manager or project sponsor. Order from Amazon.com
Your comments are welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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.
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 Personal, Team, and Organizational Effectiveness:
- Annoyance to Asset
- Unsolicited contributions to the work of one element of a large organization, by people from another,
are often annoying to the recipients. Sometimes the contributors then feel rebuffed, insulted, or frustrated.
Toxic conflict can follow. We probably can't halt the flow of contributions, but we can convert it from
a liability to a valuable asset.
- Remote Facilitation in Synchronous Contexts: I
- Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting
chair — will discover quickly that remote facilitation presents special problems. Here's a little
catalog of those problems, and some suggestions for addressing them.
- Indicators of Lock-In: II
- When a group of decision makers "locks in" on a choice, they can persist in that course even
when others have concluded that the choice is folly. Here's Part II of a set of indicators of lock-in.
- Ethical Debate at Work: II
- Outcomes of debates at work sometimes favor one party, not only at the expense of the other or others,
but also at the expense of the organization. Here's Part II of a set of guidelines for steering debates
toward wise outcomes.
- Red Flags: I
- When we finally admit to ourselves that a collaborative effort is in serious trouble, we sometimes recall
that we had noticed several "red flags" early enough to take action. Toxic conflict and voluntary
turnover are two examples.
See also Personal, Team, and Organizational Effectiveness and Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming May 15: Should I Write or Should I Call?
- After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.
- And on May 22: Rescheduling Collaborative Work
- Rescheduling is what we do when the schedule we have now is so desperately unachievable that we must let go of it because when we look at it we can no longer decide whether to laugh or cry. The fear is that the new schedule might come to the same end. Available here and by RSS on May 22.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed