www.hbr.org
PERSPECTIVES
Teams in all kinds of
nonbusiness settings—from
stock car racing to wedding
planning to hostage
negotiating—rely on flawless
preparation and execution.
Here’s how they consistently
achieve the highest standards.
When Failure Isn’t an
Option
Perspectives from Michael R. Hillman,
Philippe Dongier, Robert P. Murgallis, Mary Khosh,
Elizabeth K. Allen, and Ray Evernham
•
Reprint R0507C
Teams in all kinds of nonbusiness settings—from stock car racing to
wedding planning to hostage negotiating—rely on flawless preparation
and execution. Here’s how they consistently achieve the highest
standards.
PERSPECTIVES
When Failure Isn’t an
Option
COPYRIGHT © 2005 HARVARD BUSINESS SCHOOL PUBLISHING CORPORATION. ALL RIGHTS RESERVED.
Perspectives from Michael R. Hillman,
Philippe Dongier, Robert P. Murgallis, Mary Khosh,
Elizabeth K. Allen, and Ray Evernham
Some teams, by the very nature of their work,
must consistently perform at the highest levels. How do you—as a team leader, as a supervisor, as a trainer, or as an outside coach—ensure that this happens?
To answer that question, we sought out a
number of people who have worked with
teams in settings where high performance is
crucial: Michael Hillmann, deputy chief of the
Los Angeles Police Department and commander of its Special Operations Bureau,
which includes the SWAT team; Philippe
Dongier, who headed up a joint United Nations/World Bank/Asian Development Bank reconstruction team in Afghanistan after the fall
of the Taliban; the National Fire Academy’s
Robert Murgallis, who trains firefighting
teams; Mary Khosh, the former career coach
for players on the Cleveland Browns of the National Football League; Elizabeth Allen, a planner of society weddings, charity galas, and corporate events; and Ray Evernham, who, as a
stock-car-racing crew chief, helped driver Jeff
Gordon win three NASCAR championships.
harvard business review • the high-performance organization • july–august 2005
The following commentaries—drawn from interviews with each of the authors—offer an
array of perspectives on developing and managing high-performing teams.
The types of teams represented here are
very different. Some are ad hoc, formed for a
specific task, while others are ongoing, typically improving their performance with each
task they undertake. Some have a clearly defined leader, while others make decisions more
collaboratively. Even when there is a clear hierarchy, some teams require a leader who micromanages whereas others rely on the individual
initiative of their members. The teams may be
composed of people with similar or very different personalities and areas of expertise. And
success is measured in very different ways: the
buzz of excited conversation and media coverage generated by a successful society wedding
versus the little noticed resolution of a potentially explosive situation by a SWAT unit.
For all these teams, however, the stakes are
high. And despite their differences, some similarities emerge in the ways they achieve top-
page 1
When Failure Isn’t an Option •• •P ERSPECTIVES
level performance. For example, selection of
team members is crucial—as is a willingness to
get rid of members who don’t consistently deliver outstanding performance. A leader who
supports and builds confidence in team members is also important—and high-performance
teams without such a leader will often informally create one. Finally, the stress that defines
the work of these teams in itself helps generate
peak short-term performance—and poses the
constant risk that members will eventually
burn out.
Are lessons gleaned from such teams transferable to teams working in other environments? Certainly some of them are: Just ask
the U.S. Army, which has studied NASCAR pit
crews for ways to reduce the time their medevac teams take to get injured soldiers off the
battlefield. And even those lessons that aren’t
directly transferable may suggest ways to improve the achievements of your own highperformance team.
When a suspect walks
out of a building and
raises a rifle to the head
of a hostage, a SWAT
marksman doesn’t wait
for the command to
shoot.
Life-or-Death Tactics
by Michael R. Hillmann
Michael R. Hillmann is the deputy chief of the
Los Angeles Police Department and the commanding officer of the department’s Special
Operations Bureau, including the Special Weapons and Tactics (SWAT) team, of which he was
one of the earliest members.
On February 28, 1997, three members of our
Special Weapons and Tactics team heard over
their police radio: “Officer needs help; shots
fired.” The call came from North Hollywood,
where two suspects—heavily armed with automatic weapons and wearing body armor—had
held up a Bank of America branch, shooting
and injuring a number of people in the process.
The SWAT officers, acting on their own initiative, drove to the scene and plunged into the
thick of a firefight between the suspects and
regular police officers already at the scene. As
one of the suspects was about to carjack a bystander’s vehicle, SWAT members shot and
killed him and his cohort—thus preventing
them from escaping into the surrounding community and doing any further harm.
By contrast, the SWAT unit several weeks ago
got a report from the Foothill area that a vehicle belonging to a suspected gang member recently seen brandishing a firearm was parked at
harvard business review • the high-performance organization • july–august 2005
a residence. A SWAT team, led by their tactical
team leader, arrived and systematically evacuated the surrounding neighborhood. Although
a female leaving the house told SWAT personnel that no one was in the building, a probe of
the exterior by a canine team determined people were indeed inside. Team members covertly
entered the house and, using sophisticated electronic equipment, found the suspect and two
others hidden in the attic, along with a stock of
handguns. The three men—one of whom, it
turned out, was suspected of involvement in
several recent homicides—were taken into custody. Not a shot was fired.
These two incidents, one extraordinary and
one very typical, together highlight a key characteristic of a successful SWAT team: the ability of members both to make quick and courageous decisions on their own and to work
systematically and methodically as part of a
highly coordinated group. When a suspect
walks out of a building and raises a rifle to the
head of a hostage, a SWAT marksman doesn’t
wait for the command to shoot. But if that
same suspect has barricaded himself with others in a building, the team needs to execute a
synchronized plan of action, from initiating negotiations to covertly removing door locks to
creating a diversion that will draw attention
away from colleagues entering the building.
This combination of individual initiative
and disciplined teamwork requires a certain
type of person, which means that selection of
team members is crucial. When the Los Angeles Police Department formed the nation’s first
SWAT team in 1966 in response to a growing
number of unusually violent and dangerous
situations, it was staffed with volunteers, many
of them Vietnam veterans using their own
equipment. But in the following years, there
were incidents—a deadly shoot-out at 4115
South Central Avenue involving members of
the Black Panther Party, a confrontation at
54th and Compton with members of the Symbionese Liberation Army during which 9,000
rounds were fired—that made us realize we
needed more than a volunteer organization of
committed officers. We needed a budget and
training and a formal selection process.
Over the years, we’ve developed selection
criteria based on a number of key personal
traits, including self-discipline, perseverance,
maturity, loyalty, and, crucially, the ability to
work as part of a team. Officers applying to
page 2
When Failure Isn’t an Option •• •P ERSPECTIVES
join the SWAT unit—already screened on the
basis of their physical condition and their work
record within the LAPD’s elite Metropolitan
Division—go through a six-day selection process. The grueling test includes time in
“Hogan’s Alley,” a mock street scene where
candidates are confronted with surprise situations in which they must instantly decide,
among other things, whether or not to shoot at
a suspect. There are obstacle courses designed
to test the physical reserves of candidates so
that we can see whether they are able to think
clearly and make correct decisions when they
are exhausted or even hurt. And a series of exercises—for example, a six-mile group orienteering test over rough terrain—show us
whether an individual is a good team player.
It’s important to add that the majority of candidates who don’t make the cut are treated
with honor and dignity and their tremendous
effort during the six-day trial is acknowledged.
Passing the test doesn’t guarantee a permanent place in the 67-member SWAT platoon. If
someone fails a physical fitness qualification
more than once, he is removed from regular
SWAT duties until he can pass the test. The fitness requirement is a measure of whether
someone is really committed to SWAT duties.
Despite the high ongoing standards, membership in the unit is very stable. The average
SWAT team tenure is 14 years for supervisors
and eight years for officers, and people sometimes turn down promotions within the department to stay in the unit. This consistency is
crucial to the team’s ability to work together
and carry out its mission: to defuse violence
and save lives.
A Country at Stake
by Philippe Dongier
From November 2001 to February 2004, Philippe
Dongier (pdongier@worldbank.org) was the
Manager for Afghanistan Reconstruction at the
World Bank in Washington, DC. He now leads
a task force aimed at enhancing organizational
effectiveness within the World Bank.
Crisis is a powerful motivator. That truth was
brought home in 2001 when I led a joint team
preparing the reconstruction effort in Afghanistan following the defeat of the Taliban. The
team included approximately 60 colleagues
from the Asian Development Bank, the United
harvard business review • the high-performance organization • july–august 2005
Nations, and the World Bank. Our mission was
to help set Afghanistan on the path to reconstruction and development.
The urgency of the situation in Afghanistan
focused our minds sharply. We all knew that
the country could easily fall back into conflict
if the government did not show rapid results.
Because the international community was
keen to get started as quickly as possible, we
had just one month to conduct a needs assessment in order to guide how much assistance
donors would pledge and how help would initially be channeled to the country.
The team met the challenges and delivered.
We consulted with many Afghans, analyzed all
possible data, fleshed out a vision of what
needed to be achieved over the next ten years,
and prepared plans and cost estimates. Building on the needs assessment and the subsequent work done with the Afghan government, the city of Kabul doubled its power
supply in one year. By the end of 2004, about a
third of the country’s 20,000 villages were receiving grants and implementing small reconstruction projects such as those for water supply, schools, and roads. These villages also
conducted secret-ballot elections to choose
leaders to manage the projects—and the majority of the women voted despite expectations
to the contrary. During the same period, basic
health services expanded in almost all of the
country’s 34 provinces. In Helmand province,
for example, the number of functioning health
clinics has increased from six to 42. These are
just some examples of the progress that has
been made in Afghanistan.
That progress has largely come about because the government espoused the team’s recommendation of hiring private firms and notfor-profit organizations to design and run many
of the country’s reconstruction programs,
guided by a cadre of outstanding Afghan government officials. In parallel, the government
set in motion longer-term reforms of the civil
service. Arriving at such a strategy usually takes
years of debate between aid organizations and
the governments being helped—and the strategy is rarely so clear and shared by key players.
When the team began its work, we found it
was important to step back and take a moment
to define our roles. We had to be selective in
deciding who was going to produce what, as
opposed to just rushing into action in many directions. Probably because of the pressure,
page 3
When Failure Isn’t an Option •• •P ERSPECTIVES
There’s no time-out
during a fire. You can’t
tell the fire to wait a
minute while you consult
somebody or look up the
solution in a book.
team members needed little convincing to stay
focused on true priorities. Clear accountability
helped generate results.
Furthermore, high team performance didn’t
require micromanagement. To be effective, I
had to step back from the details and play a
support role that, in the end, proved crucial to
the team’s success. It was important, for example, to keep the teams linked with one another.
The group focusing on the health sector
needed to remain in contact with those focusing on water supply, for obvious reasons. As
overall team leader, one of my roles was to ensure this communication took place.
Forming the right team was probably the
single most important factor in our success. In
choosing team members to lead each sector,
we looked for people who had a reputation for
making things happen. We needed to be sure
that they had firsthand experience with getting
a country rapidly on the path to reconstruction
and development.
Forming the right team also meant letting
go of the least productive team members. As
work progressed, it became clear that familiarity with the country was less important than
teaming up with Afghans who possessed deep
knowledge of the way the country operated. In
fact, some expatriates who had been working
in Afghanistan for years resisted the leadership
of new outside experts by systematically critiquing their efforts. In the end, those who inhibited team performance by focusing solely
on risks and failing to offer constructive strategies had to be sidelined in favor of strong outside technical expertise.
A compelling shared vision of a rebuilt and
stable Afghanistan and the urgency of the situation at hand helped to instill a focus on results and overcome the inertia that often pervades large organizations like ours. The Asian
Development Bank, the UN, and the World
Bank are not known for their speed, but in this
case we were able to do away with much of the
red tape during the critical stages of our
project. Clear goals and accountability and
close attention to team composition were
other key success factors.
Performance Under Fire
by Robert P. Murgallis
Robert P. Murgallis (robert.murgallis@dhs.gov)
is a training specialist for the Emergency Inci-
harvard business review • the high-performance organization • july–august 2005
dent Policy and Analysis Programs at the National Fire Academy in Emmitsburg, Maryland.
The difference between a team like the New England Patriots and a team of high-performing
firefighters is the time pressure. In football, you
can call a time-out. There’s no time-out during a
fire. You can’t tell the fire to wait a minute while
you consult somebody or look up the solution
in a book. This is one business where you have
to make very quick decisions on the basis of
very little information.
Intuition is critical to high-performing firefighting teams—it can mean the difference between life and death. But our kind of intuition
is learned. Through training, reading, responding to emergencies, and talking with veterans,
we learn the cues and signals that indicate that
certain things might occur. We have a vast
mental data bank that is based on experience
and training. If a fire is a certain color, we
know the chances are pretty good that a particular product is burning. In a wildland fire, for
example, you know that certain trees burn at a
faster rate. And you know that a fire burns uphill more quickly than it does downhill. But
your training has to be such that you recognize
those cues immediately. You can’t start pondering and planning and getting an official
weather report before making decisions and
taking action.
The fact that there is seldom chaos when
firefighters go into a burning area can be
summed up in one word: confidence—confidence in their skills and in one another. Confidence is contagious. If leaders are self-assured,
capable, and knowledgeable, their people will
respond with high performance. Being a
leader in name only and driving and intimidating your teams will reduce the effectiveness of
any unit. People need to be guided and motivated. Even self-motivated individuals will lose
their drive if you don’t provide them with positive reinforcement. The trick for you as the
leader is to make your team members believe
that you believe they have worth.
Like most high-performing teams, firefighters need a mission. It’s the mission that sets the
priorities. If your mission is to stop the fire
from getting to a certain place, all your actions
and decisions will be targeted toward that outcome. Often the mission will force you to make
very difficult decisions. You may have to anticipate letting houses burn that haven’t even
page 4
When Failure Isn’t an Option •• •P ERSPECTIVES
Whatever form the
coaching takes—athletic
or psychological—a
coach needs to focus on
just one thing: his
players’ confidence.
caught fire yet, because they’re not defensible
based on the type of roof they have or the fact
that they’re surrounded by highly flammable
brush. You can’t waste your resources if you’re
going to accomplish the greatest good for the
greatest number. But it’s hard trying to explain
to home owners why you decided not to protect their homes.
People who can’t cope with that kind of
pressure shouldn’t be leading high-performing
teams, and in my line of work, leaders who
don’t perform don’t last long. On September
12, the day after the attack on the World Trade
Center, the New York City Fire Department
contacted the National Fire Academy to ask us
if we could help them restore their command
structure because they had lost so many of
their top people. As part of that effort, I saw
one of the team leaders struggling. He was a
nice person, but he really didn’t have a good
understanding of what needed to be done. His
training and expertise in other areas did not
equip him for the situation. As his inability to
cope became more apparent, an unofficial
leader emerged from among his crew who
shepherded the project along. I’ve seen this
happen many times on high-performance
teams: If a leader is not up to the job, the top
performers will step up to produce a leader
who can carry the ball.
The Confidence Game
by Mary Khosh
Mary Khosh was a career coach for the Cleveland Browns in the late 1980s and early 1990s.
During that time, she advised players on work/
life issues and was the only woman doing psychological coaching in the NFL. She is currently
a consulting psychologist with the Leadership
Development Institute at Eckerd College in St.
Petersburg, Florida.
When I worked with the Browns, the coaches
emphasized playing one game at a time—always focusing on the immediate play and the
immediate goal, always focusing on high performance. The Browns’ coaches pushed for
team excellence—in life as well as in the
game—player by player.
Coaching is a major factor in an athlete’s
success. Most of the players I worked with recognized this. They’ve been coached since they
were first discovered in youth football leagues,
harvard business review • the high-performance organization • july–august 2005
and they’ve always believed in and trusted
their coaches. In fact, sports players’ reliance
on coaches may explain why so many of them
make mistakes in life and lose most of their
money after their athletic careers are over.
They are still looking for a coach, and there are
many con artists happy to oblige.
Great coaches understand the way the
minds of high performers work. Each player
has his own needs. You can see this most
clearly after the players lose a game. Some
want the coach to come up to them and talk to
them about it. Others want to be left completely alone; they want to deal with the loss in
their own heads first.
During my time with the Cleveland Browns,
I saw players working with several different
coaches. The successful coaches kept the individual needs and interests of each player in
mind. The players willingly worked harder for
them because they wanted so much to please
them.
In my own work, my priority was also to try
to get a sense of who each player was. I would
begin with an interview, in which I focused on
understanding a player’s background—when
his talent was first recognized, how he had
been steered into pro football. In a second session, I would conduct a more formal assessment to gain a deeper understanding of the
player’s core personality, motivations, values,
needs, problem-solving skills, and interests. Finally, in a third session, we would go through
all the results of the assessment tests. It was at
that point we talked about who the player was,
what really challenged him, what put fire in
his belly.
Whatever the coaching takes—athletic or
psychological—a coach needs to focus on just
one thing: his players’ confidence. In a top
pro-football team, all the players are talented
and fit. What differentiates the winners is selfconfidence. And that kind of confidence is a
matter of choice. It isn’t something your opponents can take away; it’s something you give
away when you stop believing that you can
win. That’s why a good coach never undercuts
or demeans his players when a game is going
badly. The players need to believe that their
skills are better than their opponents’. That’s
not to say that coaches should ignore failure—
far from it. They have to analyze and understand the failure in order to avoid repeating it.
But they must not point fingers, because that
page 5
When Failure Isn’t an Option •• •P ERSPECTIVES
The trick is learning how
to manage diverse
individual personalities
and take control with
style and grace.
only makes the players more likely to repeat
the mistake.
I think my main contribution to the Browns’
performance was to get players to separate
their personal identities from their results on
the field. If self-worth were linked to scores, the
pressure associated with each game would be
tremendous. It was important for the players’
self-confidence to see football as their job—
what they did, not who they were. We talked
about their lives in general—about their families, their education, and their off-season careers. The decisions they made in these areas
helped maintain top performance as well as an
attitude about success that accompanied them
onto the field.
In my current work as a consulting psychologist focused on coaching high performers in
companies, I have found that effective senior
executives are a lot like the best sports coaches.
Like coaches, executives need to be excellent
listeners, able to evaluate the characteristics of
the people they manage. They need to be able
to work in different ways, with different people, and in different places. They need to be
dedicated, determined, persistent, and fair.
They need to be visionary and able to communicate that vision with confidence to those who
are charged with executing it. As a woman, I
used to object to all the male sports metaphors
that are thrown around in business conversation. Now that I see the parallels, I occasionally
use sports language myself.
Creativity on Demand
by Elizabeth K. Allen
Elizabeth K. Allen is the founder of Elizabeth K.
Allen, Inc., an event-planning company that
organizes and produces society weddings, charity galas, and corporate events across the United
States. The company has offices in New York and
Boston.
As an event planner who conceives, designs,
and orchestrates every type of event from corporate affairs to weddings, it’s my responsibility to put together and manage the individual
creative teams that are contributing to the occasions. Together, we do everything from selecting the perfect stamp for the invitations to
installing temporary roads in order to provide
access to an event.
One of the greatest challenges of my job,
harvard business review • the high-performance organization • july–august 2005
yet one of its most rewarding aspects, is working with creative people on a day-to-day basis. I
deal with a lot of high-profile, artistic individuals—people who are extremely knowledgeable and well known in their own right. They
are passionate and talented, caring and wonderful individuals who often have their own vision of how they want particular elements of
events designed and executed. Therein lies the
challenge. As the event producer, it’s my responsibility to keep everyone focused on the
overall concept and design and to work with
each team leader to ensure that the teams
move forward in the same direction, all while
minimizing difficulties and drama.
When you are working with creative minds,
it’s crucial to keep them on track so they don’t
go off on tangents and disrupt the project’s
rhythm or production schedule. This means
taking a very active management role. If an individual is not functioning as part of the team
in the way that he should be, I will manage
him a bit more than the others until I feel he is
back on track. If needed, I will take the person
aside and remind him that producing an event
is a team effort and not a platform for an individual to shine.
If you can’t get the creative team leaders to
accept some kind of direction and parameters,
then you must strongly consider removing
them from the project and not hiring them in
the future, however brilliant they are. For example, I worked with a very well-known and
talented but very self-centered florist. His volatile behavior would wreak havoc on the team
and affect the overall event production. Now I
just won’t work with him. If I have a client who
insists on hiring this particular florist, I decline
the project.
At the same time, you do have to trust your
most talented people. People in general always
produce better results when you trust them—
trust that they are going to perform not only to
your expectations but to their highest levels.
People hate being micromanaged because it
implies that you don’t respect or trust them.
The trick, I believe, is how to manage diverse
individual personalities and take control with
style and grace. I make sure that my people understand their position within the project
while giving them the latitude to express their
abilities, talents, and ideas.
When you want people to produce at their
peak levels, empowerment and communica-
page 6
When Failure Isn’t an Option •• •P ERSPECTIVES
tion are vital. I strongly believe in communication—it’s what I do all day. I am constantly on
the phone or in meetings. Communication
doesn’t always have to be direct, of course, and
I am a tremendous fan of e-mail. But I do
think, even in this day and age, you really cannot beat just talking to someone face-to-face or
at least by phone. Obviously, as a leader, you
cannot do all the communicating yourself. The
key is to identify the items that you really must
communicate yourself and delegate the rest.
Of course, for that to work you need to have an
associate who can function as your right-hand
person.
Inspiring and motivating a team to perform
at the top of its game is exciting and sometimes exhausting. But the process is always
very rewarding. You learn a huge amount from
your creative people, and they constantly surprise you with their ideas.
The Mechanics of Speed
by Ray Evernham
The performance of the
entire race team was
crucial to our success:
The greatest car and
driver in the world, after
all, can lose four or five
places during a stop on
pit road.
Ray Evernham was the crew chief for driver Jeff
Gordon from 1993 to 1999, during which time
Gordon won three NASCAR (National Association for Stock Car Auto Racing) championships.
Today, Evernham is president and CEO of
Evernham Motorsports, which fields a team of
NASCAR entrants for the Dodge division of
DaimlerChrysler.
When seven people have to change four tires,
fill up a gas tank, make quick adjustments to
the suspension, and get a car back on the track
in just over ten seconds, teamwork is, to put it
mildly, essential. And not just for those seven
pit crew members who “go over the wall” during a race.
Behind the wall is an entire team of people—several dozen mechanics, engineers, and
other specialists—who must also work together under extreme time pressure, even if
measured in days rather than in seconds. From
one weekend race to the next, they’ll dismantle
an entire car and several engines, making repairs and modifications to correct problems
and customize the car for the particular demands and configuration of the upcoming
track.
I was a young, unknown mechanic when I
began working with a young, unknown driver
named Jeff Gordon. But from the beginning, I
harvard business review • the high-performance organization • july–august 2005
realized that the performance of the entire
race team was crucial to our success: The greatest car and driver in the world, after all, can
lose four or five places during a stop on pit
road. How were we going to get the top-notch
performance that we needed?
First, we put together a team of particularly
dedicated and intelligent people, looking even
to individuals who didn’t have a lot of racing
experience. Our chief mechanic was a former
truck mechanic who’d been working at a car
dealership in New Jersey. He soon learned the
car racing business and was better than anybody. Our parts guy was a kid whose full-time
job had been selling plumbing supplies. He
was able to find and get the best piece at the
best price—whether it was a wheel or a toilet,
a shock or a sink.
We also put in place some formal processes
that were unusual for the sport. We’d get everybody together to watch “game films” of the
previous race and discuss areas for improvement. We kept careful records of race and mechanical data. We hired a pit crew trainer, a
former Stanford football player, who was responsible for the physical training of the crew
and the high-speed choreography of the pit
stop. Many of our rivals thought things like
this were a waste of time. But our record, and
the later adoption of many of our methods by
competitors, proved their value.
And we worked hard to keep people motivated. NASCAR’s nearly ten-month season is
the longest in professional sports, and it’s easy
for people to burn out. But our “Rainbow Warriors”—the nickname adopted by the race
team because our fire suits bore a rainbow of
paint colors offered by our sponsor, DuPont—
stayed motivated not only for an entire season
but from one season to the next. In fact, the
team remained pretty much intact for the six
years Jeff and I worked together for Hendrick
Motorsports, the owner of the car and employer of the crew.
More recently, I’ve run a much larger team
that reflects the changes in NASCAR as the
sport has grown rapidly in popularity. In 1999,
Dodge offered me the chance to lead the automaker’s return to NASCAR after a 20-year absence. Today, we employ nearly 250 people,
many of whom work in areas that go beyond
racing itself: engine and body design (our engineering staff consists of numerous specialists,
including one who holds a PhD in aerodynam-
page 7
When Failure Isn’t an Option •• •P ERSPECTIVES
ics), sales and marketing, product licensing,
travel logistics, and so on. We have four facilities that house R&D and manufacturing, six
tractor trailers and three aircraft to transport
cars and people from race to race, and an annual budget of around $50 million.
Again, I’ve tried to establish processes—
some of them, again, unconventional—that
will help this team perform at a high level.
These processes are particularly important as
we grow, because they’ll allow newcomers to
get up to speed quickly. With a team of this
size, I can no longer communicate daily with
everyone as I did when I oversaw 25 people,
but we can instill in individuals a way of thinking that will make us winners.
In fact, our team represents a new approach. Instead of the traditional NASCAR
harvard business review • the high-performance organization • july–august 2005
model that focuses on the individual driver
and car, we’ve adopted a model that we think
represents the future of the sport, one (based
on Formula 1 auto racing) that focuses on the
team’s technology and its sponsors. We run
two identical cars in NASCAR’s Nextel Cup Series, which doubles our sponsor’s exposure and
the chances of winning. At the track, each car
has its own team, and they both are out to win.
(All I ask of our drivers, Jeremy Mayfield and
Kasey Kahne, is that they don’t crash into each
other.) But our motto is: “One team, one goal.”
Reprint R0507C
To order, see the next page
or call 800-988-0886 or 617-783-7500
or go to www.hbr.org
page 8
Further Reading
The Harvard Business Review
Paperback Series
Harvard Business Review OnPoint
articles enhance the full-text article
with a summary of its key points and
a selection of its company examples
to help you quickly absorb and apply
the concepts. Harvard Business
Review OnPoint collections include
three OnPoint articles and an
overview comparing the various
perspectives on a specific topic.
Here are the landmark ideas—both
contemporary and classic—that have
established Harvard Business Review as required
reading for businesspeople around the globe.
Each paperback includes eight of the leading
articles on a particular business topic. The
series includes over thirty titles, including the
following best-sellers:
Harvard Business Review on Brand
Management
Product no. 1445
Harvard Business Review on Change
Product no. 8842
Harvard Business Review on Leadership
Product no. 8834
Harvard Business Review on Managing
People
Product no. 9075
Harvard Business Review on Measuring
Corporate Performance
Product no. 8826
For a complete list of the Harvard Business
Review paperback series, go to www.hbr.org.
To Order
For reprints, Harvard Business Review
OnPoint orders, and subscriptions
to Harvard Business Review:
Call 800-988-0886 or 617-783-7500.
Go to www.hbr.org
For customized and quantity orders
of reprints and Harvard Business
Review OnPoint products:
Call Rich Gravelin at
617-783-7626,
or e-mail him at
rgravelin@hbsp.harvard.edu
page 9
SUMMER 2007
V O L . 4 8 N O. 4
Lynda Gratton, Andreas Voigt and Tamara Erickson
Bridging Faultlines in
Diverse Teams
Please note that gray areas reflect artwork that has been
intentionally removed. The substantive content of the
article appears as originally published.
REPRINT NUMBER 48411
O R G A N I Z AT I O N
Bridging Faultlines
in Diverse Teams
Project teams can fly
or founder on the
demographic attributes
of team members and
the fractures they can
create. Here’s how to
recognize the potential
for division, and how
to respond in time when
team fractures do arise.
Lynda Gratton,
Andreas Voigt and
Tamara Erickson
C
ompanies create diverse teams to take on their most complex challenges —
tasks across boundaries, functions and geographies that no single department
or function could accomplish. Yet guiding these diverse teams to success requires some counterintuitive management practices. In particular, team
leaders should focus on tasks at the early stages, rather than on interpersonal relationships,
and then switch to relationship building when the time is right.
In a recent study of teams at large companies, we found that diverse membership of
teams and task forces is becoming the order of the day. Take Nokia Corp., which frequently
brings together disparate talent from different departments among its businesses around
the globe, while at the same time partnering with many external suppliers. Or consider the
British Broadcasting Corporation, which routinely creates huge teams for events, such as
the production and broadcast teams for the 2006 FIFA World Cup and the 2008 Olympic
Games. These typically involve groups of more than 100 people, a high proportion of whom
are not full-time employees. Team members often represent more than 15 different nationalities, with skill sets ranging from electrical work to intellectual property, from scheduling
to production. The BBC’s teams also face the daunting challenge of a one-shot deal for
which execution has to be right the first time.
The challenges that Nokia and the BBC face are by no means unique. Between 2004 and
2006, we partnered with executives from 15 large European and American companies to study
55 of their teams. What was most striking about these teams was their sheer size and complexity. The diversity of Nokia’s design team — with men and women of many nationalities and
with a wide range of ages, representing multiple functions from many different businesses
— was repeated in companies in many different industries from across the globe. Companies
in the media industry (such as Reuters Group PLC and the BBC), in telecommunications
(such as France Telecom and Canadian wireless giant Rogers Communications Inc.) and in
banking (such as Royal Bank of Scotland and Lehman Brothers Inc.) all employ large and
diverse teams to attack some of their most difficult problems. Many of the teams in the study
numbered more than 50 people, all had more than three nationalities represented and most
brought in people from several functions and businesses. (See “About the Research,” p. 24.)
Lynda Gratton is professor of management practice at London Business School. She is the author of Hot
Spots: Why Some Teams, Workplaces and Organizations Buzz With Energy — and Others Don’t (San Francisco: Berrett-Koehler Publishers, 2007). AndreasVoigt is a research assistant in organizational behavior at
London Business School. Tamara Erickson is president of the Concours Institute, the research and education
arm of the Concours Group, a professional services company headquartered in Kingwood, Texas, and a coauthor of Workforce Crisis: How to Beat the Coming Shortage of Skills and Talent (Boston: Harvard Business
School Press, 2006). Comment on this article or contact the authors through smrfeedback@mit.edu.
22
MIT SLOAN MANAGEMENT REVIEW
SUMMER 2007
SLOANREVIEW.MIT.EDU
Companies form these teams precisely because they bring to
bear the range of experiences and attitudes that will ensure that
the final product or service will be market-sensitive and innovative — more so than an offering designed by a group of people
with similar characteristics.1 Paradoxically, however, the very
nature of team diversity often creates challenges that reduce the
team’s innovative capacity and even significantly lessen its overall
effectiveness. So while business heads may wish for innovation
through diversity, what they sometimes achieve is reduced productivity and efficiency.2
How Diverse Teams Fail, and How Some Succeed
The teams in our study failed in many different ways. Some
could not deliver on time; others fell short of the hoped-for
productivity; still others were unable to produce innovative re-
sults. Some teams broke up in acrimony and
bad feeling; some foundered in incompetence. They were a litany of what could go
wrong. Many executives had been trained to
manage rather simple teams but were surprised at just how hard it is to create a
high-performing team of diverse people.
Analyzing these problems uncovered two
root failures. The first was a failure of collaboration, in which team members did not
develop trust and goodwill among themselves.3 The second was a failure of knowledge
sharing, in which team members withheld
their individual knowledge from other team
members or from other teams.4
Why is it so fiendishly difficult to enable
high-performing, diverse teams? To understand the nature of the collaborative and
knowledge-sharing failures, we looked closely
at the demography of the teams. Using complex statistical modeling, we created a unique
demographic profile for each team that took
into account team members’ ages, genders,
nationalities, education levels, functions and
tenures within the company. The model examined the configurations as a whole and the
interplay of different demographic attributes.
Close examination of these team demographic profiles revealed that in many cases
the failures in collaboration and knowledge
sharing were a direct result of faultlines —
subgroups or coalitions that emerge naturally
within teams, typically along various demographic lines. (See“An Overview of Faultline
Theory,” p. 25 for causes and characteristics
of faultlines.) These faultlines split the teams into subgroups
that were based on shared demographic characteristics. When
faultlines emerge, subgroups rarely collaborate with other subgroups, instead tending to share knowledge only within their
subgroup. Yet knowledge sharing across subgroups is critical for
complex teams to operate effectively.5
Despite the emergence of faultlines in many of the 55 teams,
some teams were able to work collaboratively and share knowledge. Deeper analysis of these productive and innovative teams
showed that a defining factor was the behavior of the team leader
and the way in which she or he structured the leadership role.
Thus, although faultlines are a common hazard, some executives
are able to reduce the problems associated with diverse teams
and, indeed, to enhance the benefits.
In particular, the executives’ leadership style and the manner
SUMMER 2007
MIT SLOAN MANAGEMENT REVIEW
23
O R G A N I Z AT I O N
About the Research
We studied 55 workgroups in 15 European and American
companies (ABN AMRO, BBC, BP, Citigroup, France Telecom,
Lehman Brothers, Marriott, Nokia, PricewaterhouseCoopers,
Reuters, Rogers Communications, Royal Bank of Scotland,
Siemens AG, Standard Chartered Bank and XL Global Services). The study was based on a quantitative survey of
1,543 members of the workgroups and their leaders. The
teams ranged in size from four to 184 people, with an average team size of 43 members. Most of the teams were
diverse in terms of gender (32% women), age (ranging
from 4% under 25 to 15% over 46), nationality (26% British, 23% American, 23% European, 15% Asian and 13% rest
of world) and education level (7% high school diploma,
50% undergraduate degree, 37% master’s degree, and 6%
doctorate). We achieved a 64% response rate.
We measured demographic faultline strength along six
demographic variables: gender, age, nationality, education, work function and tenure in the company. We
applied a statistical procedure that produced an overall
quantitative index of faultline strength by combining the
effects of all individual attributes. We used multiple regression analyses to identify the faultlines and to control
for the size of the group, the degree of task complexity,
the geographical distance between team members and
industry-level differences.
in which they prioritized actions significantly reduced the extent
to which faultlines hindered collaboration and the flow of knowledge. By studying the way these executives behaved, we are able
to make recommendations about leading diverse teams. However, while some of the recommendations are straightforward,
others are deeply counterintuitive and defy the received wisdom
about good management practice.
The Emergence of Faultlines
To illustrate this seeming paradox, consider a team from a telecom company in our study. Think of the faultlines in this team
as analogous to geologic fractures in the Earth’s crust. Like geologic fractures, faultlines can remain dormant and invisible for
some time. Geologic fractures explode as earthquakes when put
under immense pressure. The same is true of team faultlines,
which cross multiple layers of demography. In many cases, the
tensions of the faultlines emerge under the pressure of a complex, time-dependent task.
The stated goal of the telecom team was to bring together
several parts of the business to build an innovative product and
service offering for one of the company’s major multinational
24
MIT SLOAN MANAGEMENT REVIEW
SUMMER 2007
clients. Many of the client’s needs were standard, but meeting
their expectations would require the creation of a rather complex
service and delivery process. A business unit head was assigned
leadership of the new project and given charge of a core group of
22 people. She had to bring together the remainder of the team,
which was expected to total 48 people, from the four countries in
which the client had significant operations (Germany, the United
States, Japan and France), drawing from three functions (technology, marketing and operations). Although this may seem a
rather large and diverse team, many of the teams studied were of
a comparable size and complexity.
Initial Faultline Formation Is Based On Surface-Level Attributes
The telecom team members began to get to know one another
through face-to-face encounters and e-mails. Within a short
time, however, the initial faultlines began to emerge. These faultlines were drawn around readily detectable demographic
attributes — for example, the team members’ age, gender and
functional background. Team members typically use obvious
characteristics to assign themselves and others to subgroups. In
this team, an early faultline emerged between a subgroup of male
technical engineers and a subgroup of female marketing specialists. Other subgroups rapidly emerged: for example, between
people of French nationality (many of whom had been in the
company for years and were typically in their 40s and 50s) and
Americans (many of whom had joined the company recently and
were in their 20s and 30s). Note that none of these subgroups was
based on a unitary dimension but rather on the combination of
multiple dimensions (gender and function in the first case; nationality, age and job tenure in the second). A strong faultline
emerged because the team members fell into distinct, nonoverlapping subgroups based on demographic attributes. (See “The
Emergence of Faultlines in a Telecom Team,” p. 26.)
As a rule, when subgroups emerge within complex teams, each
tends to see itself as an “in-group” — people like us, who we like
because we have something in common — and those across the
boundary of the faultline as an “out-group” — people not like us,
whose interests we may find puzzling. Each subgroup within the
telecom team collaborated closely among its members, who all
got to know, like and trust one another. In a sense, what each
subgroup was doing was learning more about what its members
already knew. This deepening of knowledge can be crucial as a
team builds professional insight and muscle. However, for a team
to become truly innovative, the combination of knowledge across
subgroups is essential.6
As members of the telecom team’s subgroups began to identify more strongly with one another, the team leader came to
understand that the emerging faultlines had negative consequences. The dealings across the subgroups became a source of
tension and conflict, particularly under the pressure of task deadSLOANREVIEW.MIT.EDU
lines. For example, the predominately male engineers at one stage
refused to allow the predominately female marketing group access to some of their product findings. The story was that this
information was too technically sophisticated for the marketing
function; the reality was that the engineering subgroup did not
want to let go of their valuable knowledge. The subgroups just
didn’t seem to understand one another — they did not know the
other’s interior language, and they did not understand the other’s
key concepts and models.
orientation and switching to a task orientation. (See “The Four
Paths of Leadership Style,” p. 27.)
Path 1: Task Orientation In this pathway, the team leader uses a
strong and consistent task-oriented leadership style, as perceived
by team members, during the entire life of the team or project.
The leader can do this by creating a detailed project plan, building tight schedules for the work and emphasizing performance
goals that are high but realistic. This type of leader places great
emphasis on the task at hand, so he or she strives to remain accessible at all times and provide information that team members
need to carry out their day-to-day work. Leaders who follow this
pathway are often technically proficient — and they see their role
as providing the team with the technical and specialist assistance
critical to the task.
Deep-Level Attributes Come Into Play At Later Stages of Team
Development As complex teams develop and group members get
to know more about one another, a deeper layer of faultlines
becomes visible — this time based not on surface-level attributes but rather on subtler, deep-level attributes such as personal
values, dispositions and attitudes. At the time of a team’s formation, these deeper-level attributes are not visible. They emerge as
Path 2: Relationship Orientation This type of leader places particular emphasis on the culture of the team and on the extent
team members interact with one another and reveal themselves
and depth of relationships among team members. They do this
through their actions, words and what they choose to disclose
7
by treating team members with kindness and respect, encouragabout their personal lives.
In the telecom company team, a later set of subgroups also
ing a climate of trust and cooperation and providing recognition
formed around values, disposition and
attributes. A faultline surfaced between
An Overview of Faultline Theory
those members with cooperative values
and a subgroup of people with more
competitive values.
Faultline theory explains how a combination and the configuration of the attributes of
The Leader’s Role in Faultlines
In the geological analogy to faultlines,
various external factors (such as pressure) have an impact on how a fault
actually fractures. Similarly, many aspects of a team’s context can affect the
extent to which faultlines impact the
team’s performance. Two examples are
the extent of the cooperative culture in
which the team operates and the degree to which team members believe
senior executives work across boundaries. The most important factor in
determining whether destructive faultlines emerged was the style of leader,
and in particular the extent to which
the group’s leader was task-oriented or
relationship-oriented.8 Some leaders in
the study were able to adjust their leadership styles as the project progressed,
beginning with a task orientation and
then switching to a relationship orientation, or beginning with a relationship
SLOANREVIEW.MIT.EDU
team members can influence the team’s behavior and ultimately its performance. The
attributes that drive faultlines can be surface-level or deep-level. Readily detectable attributes such as gender, age, nationality and education are surface-level. Underlying,
or deep-level, attributes include values, personality and knowledge.
Strong faultlines emerge in a team when there are a few fairly homogeneous
subgroups that are able to identify themselves. Weak faultlines can emerge in two
rather different configurations. Faultlines generally do not emerge, or do so only
weakly, when all the members of the team are rather similar (for example, the same
age and job function). However, at the other end of the spectrum, faultlines also are
unlikely to emerge when there is heterogeneity — when the members of the team
are all very different from one another (for example, different ages and working in
different job functions).
Strong faultlines are particularly likely to emerge when all the demographic attributes of the members of the subgroups form distinct, nonoverlapping categories. For
example, a strong faultline will emerge if all women in a team are over 50 years old and
all the men are under 30. In this example, gender and age have formed a single, strong
faultline.
Whether a faultline emerges depends on how apparent the attribute is to members
of the team. As the team members get to know each other better and learn what is
similar and what is different, the possible sources of potential faultlines increase.
Strong faultlines can create a fracture in the social fabric of the team. This fracture
can become a source of tension and a barrier to the creation of trust and goodwill and
to the exchange of knowledge and information. Inevitably, therefore, when strong
faultlines emerge, the team’s creative and innovative capacity is severely limited.
SUMMER 2007
MIT SLOAN MANAGEMENT REVIEW
25
O R G A N I Z AT I O N
and appreciation for individual and group accomplishments.
These leaders are often skilled communicators and listeners.
Path 3: Task Orientation, Switching to Relationship Orientation In this
pathway, the leader begins with a strong task-oriented style by
setting targets and scheduling work. As the project progresses,
these leaders encourage team members to collaborate with one
another and work to increase the general trust and goodwill
within the team.
Path 4: Relationship Orientation, Switching to Task Orientation This
type of leader begins by creating a feeling of trust within the
team, putting an emphasis on socialization and meetings. As the
project progresses, these leaders move to a more task-oriented
approach by setting clear goals and standards and carefully
monitoring the group’s progress.
Which, if any, of these leadership paths is most appropriate
when there are strong faultlines in a team? Where it is likely
strong faultlines will emerge, the natural tendency of many leaders is to encourage team members to come together through
meetings and socializing. In effect, these leaders take Path 2.
However, this leadership action actually increases the likelihood
that faultlines will strengthen: when team members simply so-
cialize, their differences become more apparent, and the fractures
in the team can solidify.
In fact, a leader can significantly mitigate faultlines — but not
in the most obvious manner. To increase collaboration and
knowledge sharing across teams with strong faultlines, leaders
need to vary their leadership style according to how long the
team has been together. There are times when a task-oriented
style works very well and other times when a relationship orientation would be more appropriate.
Recommendations For Leading Diverse Teams
The leaders of complex teams should take four actions:
1. Diagnose the Probability of Faultlines Emerging At the outset of
a project, team leaders should think very carefully about the
diversity in their team and strive to predict as accurately as possible the probability of faultlines emerging. (See “The
Probability of Strong Faultlines Emerging in a Team,” p. 28 for
a short questionnaire that provides a way of gauging this likelihood.) It is important to remember that faultlines are not a
natural result of diversity per se but are found in situations of
moderate diversity, when a team is neither very homogeneous
nor very heterogeneous in member attributes. A medium degree of diversity leads to the emergence of only a
few fairly homogeneous subgroups. The divides
between these subgroups create the tensions that
The Emergence of Faultlines in a Telecom Team
can impede the team’s functioning.
If there is a high probability of subgroups and
Faultlines quickly emerged around obvious demographic attributes with
faultlines emerging, then the leader should emphathe formation of a team in a telecommunications company. None of the
size a task-oriented leadership style in the early
subgroups was based on a unitary dimension but rather on the combinastages of the project.
tion of multiple dimensions (gender and function in the first case;
nationality, age and job tenure in the second).
French
American
Male Engineers
Female Marketers
26
MIT SLOAN MANAGEMENT REVIEW
SUMMER 2007
2. Focus on Task Orientation When a Team Is Newly
Formed As previously mentioned, the inclination
for many leaders when they saw faultlines emerging in a new team was to focus on the relationships
between members of the subgroups. The leaders
created opportunities for people to get to know
one another better, hoping that socializing would
cause the faultlines to be bridged. Yet this exacerbates the problem. Simply put, in a team’s early
going, the more people interact with one another,
the more likely they are to make snap judgments
and to emphasize their differences.
A better strategy for leaders of teams with potential faultlines is to create energy around the task
itself. This was clearly visible in teams at the Royal
Bank of Scotland. In these teams — even those with
strong faultlines — collaboration and knowledge
sharing were strengthened through a host of taskSLOANREVIEW.MIT.EDU
began with a task orientation, coordinating the
team’s activities, creating clear schedules and
providing technical support. This support from
The most important factor in determining whether destructive faultlines
the top initially ensured that the subgroups
emerged in a team was the style of its leader and, in particular, the extent
learned more about each other and began the
to which the leader acted along a continuum of task orientation and relaprocess of sharing knowledge. At the same
tionship orientation.
time, the leader’s capacity to clearly state the
team’s mission and create a common goal enPath 1
sured that the subgroups became strongly
Task-Oriented
aligned to a common purpose despite the faultPath 4
lines already running through the team. The
members of the team began to feel that they
were united in a goal that was greater than the
Time
differences among the subgroups.
Over time, however, deep-level faultlines in
this complex and diverse team began to emerge
Path 3
and become increasingly important. The major
Path 2
faultlines initially had formed around functional specialization and nationality. The
Relationship-Oriented
media team’s creative designers came mostly
from the West Coast of the United States, while
the production teams were located on the East
oriented characteristics. At the beginning of team formation,
Coast and in Germany. These differences were bridged by the
leaders created very detailed descriptions of realistic perforclear sense of a shared task and goals created by the team
mance goals. Next, the work was planned and scheduled with
leader. Later, though, subgroups began to form around the attributes and personalities of group members. A subgroup of
precision: Every project was on a 30-day, 60-day or 90-day timetable. At this early stage, much effort was focused on providing
high-energy, highly competitive people (known as Type A personalities) began to form. These are people who like to work
the necessary resources and coordinating team members’ activities. Team members learned about one another’s skills and
under pressure and create pressure for others, who enjoy the
competencies rather than about their personalities and lives.
rush of adrenaline and love competing.9 Members of this subgroup were drawn from the West and East coasts of the United
This task orientation focused the attention of team members on
States and from Germany; some were men, some were women;
performance and requirements. Subgroups did emerge, but they
some old, some young. Their deep-level Type A characteristic
revolved around task-oriented characteristics such as functional
cut across the surface-level characteristics.
expertise and education, rather than personality differences. By
As the original faultlines began to be bridged through a
learning who they could go to for particular types of information, the subgroups at Royal Bank of Scotland were able to move
shared task, this new personality-based, deep-level faultline became an increasing source of conflict and tension. Those outside
swiftly into the task itself
However, while this approach increases the early effectiveness
the Type A category created names for them (“the crazies,” “the
of teams, it is not as useful for dealing with some of the tensions
no-lifers”), while the Type A subgroup became frustrated by
that later emerge, such as around deeper personality traits and
what they saw as slowness and a lack of focus from the others.
differences in values. To do this, team leaders must learn how and
The task-oriented leader — who also had a Type A personality
— failed at this point to switch styles, instead continuing to plan,
when to switch leadership styles.
organize, schedule and create tasks. Since the Type A subgroup
3. Learn When to Make the Switch Focusing on the task is crucial
was the most vocal (and the team leader was a member of the
to the early effectiveness of a team in which strong faultlines are
subgroup), the schedules simply became faster- and faster-paced
expected to emerge. However, if the team is to be effective in the
and the task demands more and more frequent. Conflicts arose
longer term, then the leader has to switch styles from task orioften, and those outside the Type A subgroup became more isoentation to relationship orientation. If the leader fails to make
lated, demotivated and unhappy.
This discord came to a head during a performance meeting.
this switch, the team will slowly become less effective, as observed in one of the media teams in our study. The team leader
The business unit head overseeing the project criticized the team
The Four Paths of Leadership Style
SLOANREVIEW.MIT.EDU
SUMMER 2007
MIT SLOAN MANAGEMENT REVIEW
27
O R G A N I Z AT I O N
leader for the lack of innovative ideas coming from the team.
The team was fast-paced, but the results were often boring and
predictable. Looking back, this outcome should have been no
surprise: Some of the most creative members of the team were
not among the Type A subgroup, whose members were calling
all the shots. Yet those outside the dominant subgroup lacked the
power to slow down the program, argue for time for reflection
or get their creative ideas heard and discussed.10
The team leader had failed to read the signs that called
for switching from task-oriented leadership to relationshiporiented leadership. The Type A subgroup was able to dominate
by overly influencing the agenda and taking most of the
resources.
nance companies studied. At one point, tensions were coming
to the fore around different values and personalities among
team members. The team leader — who previously had been
predominately task-oriented — was able to switch to a more
relationship-oriented style. Over the course of a few weeks, the
leader brought the team together for several social activities,
surfaced and talked openly about the tensions the members of
the team felt and showed respect to the various work styles and
values in the group.
Developing Better Teams and Team Leaders
So how does a team leader know when to switch from task orientation to relationship orientation? The switch will be
successful only at the point at which the team has sufficient
shared experience to have developed a clear protocol for communication and coordination of activities and an established
operational structure.11
As a guideline, when all members of a team have developed
specific expectations for the project and have negotiated a
4. Switch to Relationship Building When the Time Is Right In the
media company example, the team leader had built an effective
team but not an innovative team. The leader had failed to make
the switch that characterizes Path 3 of leadership.
A team leader did follow the third path in one of the fi-
The Probability of Strong Faultlines Emerging in a Team
For team leaders: This short survey will show you the probability
of a strong faultline emerging in your team. Rate your team
members against these four elements:
1. The number of nationalities in the team
a. Team members are all of the same nationality.
b. There are two nationalities.
c. There are three to five nationalities.
d. There are six to 10 nationalities.
e. There are more than 11 nationalities.
2. The current age, education and gender of the team members
a. The majority are the same gender and about the same age
and have the same education level.
b. The majority are the same gender and have the same education level but are of different ages.
c. The majority are of the same age and have the same education level and are both men and women.
d. The majority are the same age and gender and have different education levels.
e. The team contains both men and women of different ages
and education levels.
3. The current business location of team members
a. They are all from the same function and the same business.
b. They are all from different functions in the same businesses.
c. They are all from different functions and different businesses within the company.
28
MIT SLOAN MANAGEMENT REVIEW
SUMMER 2007
d. They are from different businesses and functions in the
company and from longstanding partners from outside the
company.
e. They are from different parts of the company and include
longstanding partners of the company and new partners
and customers of the company.
4. The values and aspirations of the team
a. All members of the team have very similar values, dispositions and attitudes.
b. Many members of the team share values, dispositions and
attitudes.
c. There is a clear divide between groups with regard to values,
dispositions and attitudes.
d. Many people have different values, dispositions and attitudes.
e. There is a great deal of variety in values, dispositions and
attitudes.
Low probability of faultlines emerging:
Scoring mostly a’s and b’s — The team is relatively simple and
homogeneous, so it is unlikely that faultlines will emerge.
Scoring mostly e’s — The team is heterogeneous. Therefore, it is
unlikely that faultlines will emerge.
High probability of faultlines emerging:
Scoring mostly c’s and d’s — This team has a high potential for faultlines to emerge because a medium degree of diversity tends to lead
to the development of only a few fairly homogeneous subgroups.
SLOANREVIEW.MIT.EDU
A leader can significantly mitigate faultlines. To increase collaboration and knowledge sharing across teams with
strong faultlines, leaders need to vary their leadership style according to how long the team has been together.
widely accepted influence structure, then the time is right to
switch to a relationship-oriented leadership style. Instilling
confidence in the team and creating opportunities to socialize
at that point helps the development of new abilities and allows
the team to grow. However, if the team is still trying to learn
the specifics of the project, clarify people’s roles and negotiate
members’ status and authority, then the switch would come
too early and would only amplify the underlying tensions between subgroups.
This provides important guidelines for managers who head
diverse teams, which are tasked with some of the most important and difficult challenges that companies face. But it also
points to an important new development challenge for executives. Not only do future leaders need to develop solid program
management skills and confident interpersonal skills but they
also need to learn which leadership style to emphasize, based on
their team’s needs and characteristics. Providing team leaders
with a framework for assessing faultlines will give them the insights needed to overcome the divisions and move teams toward
achieving their, and the company’s, ultimate goals.
REfEREncEs
1. The power of integration on innovation has been described in L.
Gratton, “Managing Integration Through Cooperation,” Human Resource Management 44, no. 2 (2005): 151-158; and S. Ghoshal and L.
Gratton, “Integrating the Enterprise,” MIT Sloan Management Review 44,
no. 1 (fall 2002): 31-38.
2. Richard Hackman’s work on group dynamics provides early insights into the formation and maturation of teams; see, for example,
J.R. Hackman, ed., “Groups That Work (and Those That Don’t): Creating Conditions for Effective Teamwork” (San Francisco:
Jossey-Bass, 1989). The difficulties of managing complex teams are
described in L. Gratton, “Hot Spots: Why Some Teams, Workplaces
and Organizations Buzz With Energy — And Others Don’t” (San
Francisco: Berrett Koehler Publishers, 2007).
3. The way in which teams collaborate with each other is increasingly
seen as central to their effectiveness. An overview of this argument is
provided in S. Alper, D. Tjosvold and K.S. Law, “Interdependence and
Controversy in Group Decision Making: Antecedents to Effective SelfManaging Teams,” Organizational Behavior and Human Decision
Processes 74, no. 1 (1998): 33-52.
4. Knowledge sharing has been argued to be central to the innovative
capacity of a company. See, for example, I. Nonaka and H. Takeuchi,
“The Knowledge-Creating Company: How Japanese Companies Create
the Dynamics of Innovation” (New York: Oxford University Press, 1995).
SLOANREVIEW.MIT.EDU
5. The challenge of team faultlines is currently being studied by several
scholars. For an academic description of faultline theory, see D.C. Lau
and J.K. Murnighan, “Demographic Diversity and Faultlines: The Compositional Dynamics of Organizational Groups,” Academy of
Management Review 23, no. 2 (1998): 325-340.
6. The study of in-groups and out-groups has been a central theme of
group analysis. For an overview of some of the key concepts, see, for
example, H. Tajfel and J.C. Turner, “The Social Identity Theory of
Inter-Group Behavior,” in “Psychology of Intergroup Relations,” ed. S.
Worchel and L.W. Austin (Chicago: Nelson-Hall, 1986), 7-24.
7. The distinction between surface-level and deep-level attributes
has been explored in more detail in S.E. Jackson, K.E. May and K.
Whitney, “Understanding the Dynamics of Diversity in Decision-Making Teams,” in “Team Effectiveness and Decision Making in
Organizations,” ed. R.A. Guzzo and E. Salas (San Francisco:
Jossey-Bass, 1995), 204-261. For a more academic treatment of the
theory, see D.A. Harrison, K.H. Price and M.P. Bell, “Beyond Relational Demography: Time and the Effects of Surface- and Deep-Level
Diversity On Work Group Cohesion,” Academy of Management Journal 41, no. 1 (1998): 96-107.
8. Task orientation and relationship orientation are a continuum
of leadership styles and have been examined in leadership research for more than a decade. For an overview of both, see G.A.
Yukl, “Leadership in Organizations,” 6th ed. (Englewood Cliffs,
New Jersey: Prentice-Hall, 2005). The distinction was first made in
the 1950s in the seminal research by E.A. Fleishman, “The Description of Supervisory Behavior,” Journal of Applied Psychology, 37,
no. 1 (1953): 1-6.
9. For a more detailed overview of Type A characters, see, for example, M.A. Chesney and R.H. Rosenman, “Type A Behavior in the
Work Setting,” in “Current Concerns in Occupational Stress,” ed. C.L.
Cooper and R. Payne (London: John Wiley, 1980), 187-212; and M.
Friedman and R.H. Rosenman, “Type A Behavior and Your Heart”
(New York: Knopf, 1974), which provides a detailed description of the
psychological construct.
10. The potentially negative impact of speed on creativity has been
explored by several scholars. See, for example, C. Mainemelis,
“When the Muse Takes It All: A Model For the Experience of Timelessness in Organizations,” Academy of Management Review 26, no.
4 (2001): 548-565. For an overview on time, see D.G. Ancona, P.S.
Goodman, B.S. Lawrence and M.L. Tushman, “Time: A New Research Lens,” Academy of Management Review 26, no. 4 (2001):
645-663.
11. For an overview of studies on the impact of time on group development and processes, see S. Blount, ed., “Time in Groups,” vol. 6,
“Research on Managing Groups and Teams” (Greenwich, Connecticut:
JAI Press, 2004).
Reprint 48411. For ordering information, see page 1.
Copyright © Massachusetts Institute of Technology, 2007
2007.. All rights reserved
reserved..
SUMMER 2007
MIT SLOAN MANAGEMENT REVIEW
29
PDFs ■ Reprints ■ Permission to Copy ■ Back Issues
Electronic copies of MIT Sloan Management Review
articles as well as traditional reprints and back issues can
be purchased on our Web site: sloanreview.mit.edu or
you may order through our Business Service Center
(9 a.m.-5 p.m. ET) at the phone numbers listed below.
To reproduce or transmit one or more MIT Sloan
Management Review articles by electronic or mechanical
means (including photocopying or archiving in any
information storage or retrieval system) requires written
permission. To request permission, use our Web site
(sloanreview.mit.edu), call or e-mail:
Toll-free in U.S. and Canada: 877-727-7170
International: 617-253-7170
Fax: 617-258-9739
e-mail: smrpermissions@mit.edu
MIT Sloan Management Review
77 Massachusetts Ave., E60-100
Cambridge, MA 02139-4307
e-mail: smr-orders@mit.edu
Reproduced with permission of the copyright owner. Further reproduction prohibited without permission.
Purchase answer to see full
attachment