My Site
Skip to Content

Leland Teschler's Editorial: Teamwork is Overrated

July 30, 2009

Leland E. Teschler

Printer-friendly version

The chatter is rising about what it will take to lift us out of the current economic malaise, and innovative new products are usually part of the prescription. But we may need a change in corporate mindset before we can greatly boost our output of creative products.

The problem: Development teams are often an obstacle to creativity rather than a vehicle for truly elegant solutions. Particularly for large efforts, the evidence is that many team members work at cross purposes. That's why throwing more people at a project frequently slows it down rather than speeds its completion.

Authors Jonathan Littman, who has worked with the Ideo industrial design house, and Marc Hershon, a branding expert, recently pointed out the teamwork fallacy in a book with the tongue-in-cheek title of I Hate People. They point out that even a century ago, researchers found individual productivity declines as teams expand.

Proof came from an experiment with a tug-of-war rope competition such as you might find at a family reunion. A strain gage measured the effort put out by individuals and by groups pulling on the rope. It turned out that the average person in a group of eight yanked only half as hard as someone working alone. In groups of three, individual output dropped by 20%.

The same thing happens among elite women rowers. Eight rowers have been shown to row less enthusiastically than the same rowers individually.

The situation is probably worse in large companies, say psychologists, because many employees are there not specifically to work, but because they like to interact with others. Their focus on chatting slows down those who are trying to get a job done.

And history shows many of the most game-changing products come from the minds of just a few high performers. There is a body of scientific work that has found teams often distract achievers from work and tasks. One study at the University of Calgary, for example, involved people working at a computer alone or with a partner in full view. The sight of someone else working slowed the progress of subjects in this experiment. Things sped up when the other person left.

Merely thinking in terms of individual effort seems to yield innovative ideas, or at least more so than thinking about teamwork does. That was the conclusion of researchers at Cornell and the Hass School of Business who divided business school students into two groups, one answering questions that encouraged individualistic thinking, the other exposed to queries that promoted group-like and collectivistic behavior. The idea was to prime the students to think either distinctively or as a group.

Interestingly enough, groups primed to be more communal were less innovative in coming up with novel ideas for a business challenge. The researchers’ conclusions: When creativity is what you want, individualism trumps teamwork. Most teams are likely get the majority of their ideas from what already exists. But top design firms, say Littman and Hershon, find inspiration in tangential concepts. Designers of baby carriages, for example, are more likely to draw insights from sports cars or skateboards than from other baby carriages.

Unfortunately, most of these findings seem to be lost on upper management. Four decades ago, Fortune magazine found that managers ranked teamwork tenth on the list of most valued qualities in employees. In the 2005 follow-up survey, teamwork was number one.

— Leland Teschler, Editor

Comments

What a Team Is and Is Not

"Teamwork as a Buzzword," I don't think I could have said it better myself. The red-flag statement I had noticed myself was "throw more people at it," which you addressed perfectly. There is a black and white difference between a group of people working together, and a TEAM.

Personally, I work in a creative fashion, and there are environments, methods, disciplines, that work best to bring results, and the best ones are usually surrounded by good selection of people. Far separated from picking people like middle-school kickball, and assigning them a task without any regard for talent, interest, or competency.

How much money, time, effort, blood, & sweat do you think the US Army spends on teaching a group of men to actually work together as a team? The drill instructor knows full well that just because he has a group of men standing in front of him, does not mean they are a team... yet. Until he's done training them, they are a bunch of "inbred... underachievin'... group of misfits he's ever seen...". ;)

The problem is not teams, per se; the problem is not knowing what a team actually is.

On a more domestic note, to add to what Buzzword wrote, have you ever read the book "Now Discover Your Strengths?" Wonderful book on 1) valuing individuals' natural-born talent above being "well rounded", and 2) maximizing that talent in very pointed an aggressive application. A team of highly skilled, purposeful, role-playing individuals will beat out a lone wolf any day.

BTW - Google "Somali Pirates", "Richard Phillips", and "snipers" and you will find a dynamic example of what is only possible through a team.

Teamwork is about spreading responsibility

Most teams are not about getting things done but rather about spreading responsibility by involving everyone available. It fits management expectations mentioned at the end of the article and somehow some members do get things done.

Teamwork

Egad! Next you're going to tell me that when being interviewed for a technical job I should be asked questions about my technical competence - not just how I would resolve conflicts!

Teamwork as a buzzword is overdone

If your idea of teamwork - or your management's idea of teamwork - is to simply throw more people at the project then yes I agree that it is counterproductive and will slow the project down. But if you have actually studied management and teamwork you will have learned two very important points, (1) selecting the right people for the team is paramount, and (2) keep the team size as small as possible to get the job done will improve efficiency. These two concepts are harder to achieve than they seem and in my experience not many senior managers understand them. They tend to look at any random collection of people who have been assigned a single objective as a "team". Also keep in mind that a team can be as small as just two people (Hewlitt and Packard are just one very good example).

All good teams know when it is time for solitary work, and when to come together to review and share ideas.

Brainstorming is a whole other issue, but here as well, too many cooks in the kitchen will spoil the broth. The general thinking is that to get one good idea, you need to generate hundreds culled from a large group. This is in fact - and in my experience - not the best way to innovate. A small group (2 to 5 perhaps) of highly skilled people thinking about a single problem will do a better job working together and individually in the long run. It is, howver less "fun" and won't require the hiring of an outside "brainstorm facilitator" or expensive off-site trips and events.

Teamwork

I believe it depends on the size of the team and even then what the others can or are able to do. Initial creative ideas seem to come out well from a team of two, then the remainder of the group can be used to get the idea to work. Key is that its not so much a team of equals but a team where others do the next steps they are asked too.

Amen!

I came to this conclusion after working on "teams" for the past several years. It became apparent that one or two people actually had good ideas and wanted to get work done and the rest of the team was in place to either argue, socialize, protect their turf, or needed to be brought "up to speed" constantly. It dawned on me that it took only two people camped out on a sand dune to teach humanity how to fly. So why do I need a cross functional team of 25 people to brainstorm a solution? I recentlly came across an equation that describes the IQ of a team...take the IQ of all the team members and divide the lowest one by the number of people on the team.

Ron Khol is smiling down

Ron Khol is smiling down upon you today!

Teamwork is Overrated

I think this was well known by all competetent engineers, as
Leland says this is a popular myth with top managment of most firms, perhaps this was\is the indoctrination propogated by the so called managment gurus?

Leave a comment

The content of this field is kept private and will not be shown publicly.

Acceptable Use Policy