Team Challenge - Training Technology Teams

Without staff development and training there is little chance of success for building high-performance technology teams. Staff development endeavors that allow users to share experiences need to be designed with readily available resources such as online help bulletin boards. As the technology team advances in use and skill of the technology, a more sophisticated approach is needed such as a listserve for getting expert advice and sharing that advice with multiple users. Once the listserve has been functional for some time the information can be archived and placed on a searchable database for users to renew their skills or for new team members to use in the early stages of technology teaming.

A Learning Approach to Teams

Characteristics of Technology Team Training

Technology team training requires appropriate hardware with storage for growth and the needed speed and bandwidth for activities that include video conferencing.
Technology team training requires appropriate software with features that are needed for accomplishing training goals. Look for and visit other similar systems for finding out potential problems, or for discovering features that may not have been anticipated.
Technology team training requires an experienced system operator for keeping the system running and working-out potential bugs.
Technology team training requires application compatibility within the system and among different operating systems. Determine the level of users and their current hardware. The likelihood of success is diminished when putting in a system among many users of a different platform.
Technology team training requires the availability of functions identified in the goals for the training such as group e-mail, the ability to send files, and the ability to conference with message threading, private discussions, and keyword searches.

Checklist for Training Technology Teams

Develop a training plan that addresses the following:

The writing of training manuals that are written in "user friendly" formats for non-technical people.
The opportunity for users to share experiences and build relationships.
The exploration of opportunities for hands-on training.
The provisions for advanced training.
The development of a training curriculum which goes beyond the mechanics to include "real work" activities and homework.
The use of a series of online exercises for dispersed teams.
The development of simple step-by-step protocols.
The creation of a "buddy system" to group experienced users with novices.

Develop and manage a team online information forum for the following purposes:

To supplement e-mail communication.
To create an online "home" that can be customized for the team.
To provide an organizational memory for new generations of team members.
To serve as a link to other teams on the host network.
To provide team issues greater visibility encouraging more involvement of stakeholders.
To provide a possible team member recruiting tool

Develop listserves for consultation with experienced users and for building mailing lists.

Develop open forum discussion groups that are simple to access, navigate, and search. Update frequently for removing outdated items.

Checklist for Team Member Roles

Teams should assign specific roles and change them periodically.
Team roles should include at minimum team facilitator/leader, task coordinator, document preparation, and monitor.
Team members may perform the same role, but all members should remain actively conscious of team activities.
Team members need to volunteer for roles at times, but also expect assignments when there is a need.
Team members should acknowledge that roles have been assigned and/or volunteered for.
Team members should expect to play multiple roles.
Team members require clarification of roles, and expectations need to be made explicit.
Team members should be flexible because roles are constantly changing in high-performance virtual situations.

Cautions with Training Technology Teams

$Fear of technology and computers ("Computerphobia").

$Be patient with new technology users.

$ Do not disregard resisters; they sometimes become the biggest supporters.

Adapted from Gamse and Grunwald, 1991; G. D. Bailey, T. Ross, and G. L. Bailey, 1997, and Lipnack & Stamps, 1997.

Last updated: March 10, 1998