team.GIF (1362 bytes) EXAMPLES

Example 1

The following example is taken from the Team-Building Experiment undertaken by FMV.

FMV Infosyst is the main IT procurer for the Swedish military. Their procurement project was to procure a system solution for UAV (a small aircraft without a pilot) to include the aircraft, a ground system, and training. Approximately 25 people were involved in the procurement team.

The difficulties the team faced were largely centered around information dissemination, as follows:

The experiment was therefore targeted at improving information flow. The following recommendations were made:

The expected benefits from implementing the recommendations were as follows:

Example 2

The following example is taken from the Team-Building Experiment undertaken by Rhone Poulenc.

Rhone Poulenc is an international chemicals, pharmaceutical, and animal health business with a turnover of US$14 billion and 69,000 employees worlwide. Their annual IT spend is at least £100 million on mission-critical systems.

Their method of working is decentralized, with central coordination. Their IT purchasing teams are led by senior managers based in France, the U.K., and the U.S., and they communicate by phone, video conferencing, and email.

Rhone Poulenc’s challenge was to bring about collaboration as a normal way to do business in a delegated, highly pressured environment. Therefore, the objectives of the experiment were to:

The following problem areas were identified:

The approach taken for the experiment was as follows:

The TEAM consultant presented to the team members by video and phone. The team members themselves then developed the agenda and design of the workshop (guided by the consultant). The Procurement Survey Tool was used as a catalyst for rethinking their processes.

The procurement team at Rhone Poulenc realized that their instinct was to focus on projects, rather than process. The recommendations were to:

From feedback, the team members said that the experiment had helped to break down barriers, to work out who does what and when, and to communicate better.

Return to TEAM