Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 9, Issue 21;   May 27, 2009: Teamwork Myths: Formation

Teamwork Myths: Formation

by

Much of the conventional wisdom about teams is in the form of over-generalized rules of thumb, or myths. In this first part of our survey of teamwork myths, we examine two myths about forming teams.
Statue of Hermes with modern head

Statue of Hermes with modern head. White marble, Antonine Era, second century. From Porcigliano estates in Castelporziano. Hermes was the ancient Greek god of business, among other duties. Although Greek businessmen probably relied on Hermes for insight and assistance in their deals, most people today would doubt that such reliance ever did much good. So it is with our modern reliance on principles and guidelines for which there is today little evidence or support — our descendants will regard these beliefs as mythology. The work is at Museo delle Terme di Diocleziano in Rome.

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  Go to top Top  Next issue: One Cost of Split Assignments  Next Issue

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.

Order from AmazonThe 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

52 Tips for Leaders of Project-Oriented OrganizationsAre 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!

Your comments are welcome

Would you like to see your comments posted here? rbrenPhLMVtDQbewBWvJRner@ChacBsiUYygRvANyVIKKoCanyon.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.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

A checklistKeep a Not-To-Do List
Unless you execute all your action items immediately, they probably end up on your To-Do list. Since they're a source of stress, you'll feel better if you can find a way to avoid acquiring them. Having a Not-To-Do list reminds you that some things are really not your problem.
Apple PieGive Me the Bad News First
I have good news and bad news. The bad news is that if you wait long enough, there will be some bad news. The good news is that the good news helps us deal with the bad news. And it helps a lot more if we get the bad news first.
Albert Einstein playing his violin on his 50th birthday in 1929The Perils of Piecemeal Analysis: Content
A team member proposes a solution to the latest show-stopping near-disaster. After extended discussion, the team decides whether or not to pursue the idea. It's a costly approach, because too often it leads us to reject unnecessarily some perfectly sound proposals, and to accept others we shouldn't have.
Henri Laurence Gantt, inventor of the Gantt ChartThe Tyranny of Singular Nouns
When groups try to reach decisions, and the issue in question has a name that suggests a unitary concept, such as "policy," they sometimes collectively assume that they're required to find a one-size-fits-all solution. This assumption leads to poor decisions when one-size-fits-all isn't actually required.
Rapids in a northern streamThe Risks of Too Many Projects: Part I
Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.

See also Personal, Team, and Organizational Effectiveness and Project Management for more related articles.

Forthcoming issues of Point Lookout

kudzu enveloping a Mississippi landscapeComing April 5: Listening to Ramblers
Ramblers are people who can't get to the point. They ramble, they get lost in detail, and listeners can't follow their logic, if there is any. How can you deal with ramblers while maintaining civility and decorum? Available here and by RSS on April 5.
Ruth Bader Ginsburg in 2016And on April 12: How to Listen to Someone Who's Dead Wrong
Sometimes we must listen attentively to someone with whom we strongly disagree. The urge to interrupt can be overpowering. How can we maintain enough self-control to really listen? Available here and by RSS on April 12.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenqOitVCIDFDlQOiHdner@ChacWQTHeMNAoPnwuoZFoCanyon.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

Public seminars

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.