70 Roles
American Management Association
www.amanet.org
New members of the group often have to learn these implicit rules as they
work their way from the periphery into full participation (Lave & Wenger,
1991). There are two reasons, however, why explicitly stated ground rules
are important for e ective group learning.
First, not all communities of practice have developed norms and ex-
pected behaviors that foster productive re ection and e ective communi-
cation. While the social energy generated by a community can, on the one
hand, “give rise to an experience of meaningfulness,” on the other, it can
“hold us hostages to that experience” (p. 85). As Wenger states:
The local coherence of a community of practice can be both a strength
and a weakness. The indigenous production of practice makes com-
munities of practice the locus of creative achievements and the locus
of inbred failures; the locus of resistance to oppression and the locus
of the reproduction of its conditions; the cradle of the self but also the
potential cage of the soul. (Wenger, 1998, p. 85)
Habits may have developed over the lifespan of a community that
block learning and prevent people from speaking their minds without fear
of retribution. Some cultures or groups may shun the idea of re ection
and learning, ascribing these processes to those who “don’t know what
they’re doing”; this often is the result of ingrained defensive routines that
have evolved to keep things just the way they are, whether they serve the
organization, its stakeholders, and its employees or not. Having explicitly
agreed- upon ground rules that help team members interact in more pro-
ductive ways can create the space for new, more functional routines to
develop that lead to improvements not only in strategies, programs, and
projects, but also in how people feel about their work.
The second reason that ground rules are important stems from the
nature of project work. In project environments, people are continually
rotating into and out of various team roles. New teams are constantly
being formed, and people must work with “new faces” who come from
di erent cultures, business units, and functional backgrounds from both
inside and outside their company, including strategic partners, newly ac-
quired entities, vendors, suppliers, and customers. The demands placed on
these teams require the delivery of quick results before a team is able to