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.
eople 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.
Herm 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.
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 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 seriesTopNext Issue
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.
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!
As Glen rounded the corner behind the old oak, entering the last mile of his morning run, he suddenly realized that he was thinking about picking up the dry cleaning tomorrow and changing his medical appointment. Physically, he was jogging in a park, but mentally, he was running in a squirrel cage. How does this happen? What can we do about it?
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.
Getting to the truth can be a difficult task for managers. People sometimes withhold, spin or slant reports, especially when the implications are uncomfortable or threatening. A culture that supports truth telling can be an organization's most valuable asset.
Many of us spend seemingly endless hours in meetings that seem dull, ineffective or even counterproductive. Here are some insights to keep in mind that might help make meetings more worthwhile — and maybe even fun.
Do you have some little secret tricks you use that make you and your team more effective? Do you wish you could know what secret tricks others have? Here's a way to share your secrets without risk.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the e-book!
Past issues of Point Lookout are available in four e-books:
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
The Race to the South Pole: Ten Lessons for Project Managers
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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here are some upcoming dates for this program:
Organizational Politics for People Who Hate Politics
Have you ever felt powerless to implement an important new idea? Have you ever been "blind-sided" at a meeting? Have you ever lost two good employees because you could find no way to keep them from attacking each other? These are some of the issues of organizational politics. Many of us have become enmeshed in them from time to time, but we've also known some people who seem to be able to engage and prosper. How is that done? We'll inventory the challenges of organizational politics, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees learn concrete techniques for dealing with the problems that arise in workplace politics, while keeping their integrity intact. Read more about this program. Here's an upcoming date for this program:
Managing global or dispersed teams is challenging — miscommunications, misunderstandings, and interpersonal conflict all thrive in the typical environment of the distributed team. And they're even more common in global teams, because of time-zone offsets and language and cultural differences. We'll inventory the challenges distributed and global teams face, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees will learn concrete techniques for preventing and dealing with the problems that accompany global and distributed teams. Read more about this program. Here's an upcoming date for this program:
Person-to-Person Communications: Models and Applications
When we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program we'll explain — and show you how to use — a model of inter-personal communications that can help you stay out of the ditch. We'll place particular emphasis on a very tricky situation — saying no to power. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here's an upcoming date for this program:
Person-to-Person Communication for Project Managers
When we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here's an upcoming date for this program:
The Race to the South Pole: Lessons in Risk Management for Leaders
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 and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management and its application to organizational efforts. A fascinating and refreshing look at risk management from the vantage point of history. Read more about this program. Here's an upcoming date for this program:
Organizational politics presents a risk not often accounted for by risk models. It creates one of the many components of risk management risk — the risk that the risk management process itself is inadequate. Political considerations can lead to risk products that seem acceptable but which are fatally flawed; or worse, the risk products are plainly unserviceable, but everyone chooses not to acknowledge the problem. In this program we'll examine how organizational politics influences risk management, and discuss several measures for mitigating its effects. Read more about this program. Here's an upcoming date for this program:
A Tip a Day arrives by email, or by Yahoo! Widget, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
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.