Teams - when and when not LO5156

Rol Fessenden (76234.3636@compuserve.com)
27 Jan 96 16:20:45 EST

Sb: Teams - when and when not LO5130

I realize my note on "when to team and when not to team" is hard to
follow. I have tried to provide a graphic to clarify. This is the
graphic I tried to describe in my original note. The two notes could
probably benefit from being read together.

Here is the graph. I realized I could create it in the "Ascii" language.

Parameters of successful team Organizations in
a Product Development Environment

No-| --B--
|
|
Does the |
Customer |
Understand |
the Product? |
|
|
| -A-
Yes-|__________________________
Yes No
Do we (producer org)
Understand the
Product?

At -A- there are few mysteries about this product, there are few reasons
for undefined or indeterminant communications, and there are opportunities
to create and disseminate the product efficiently and effectively through
an organization of functional specialists.

At -B- there many uncertainties in the creation, understanding and
successful dissemination of the product. Thus, there is a strong need for
a stand-alone team consisting of functional experts to work together to
bring this product to fruition.

--
Rol Fessenden <76234.3636@compuserve.com>