Skip to main content
 
Tying a Sensible Knot: A Practical Guide to State-Local Information Systems



Chapter 3. Best Practices

Choose a capable pilot site


Many system implementations are initiated with pilot tests that bring the system into the field to evaluate and refine design, performance, and integration with other systems and activities. The pilot site (there may be more than one) is a critical organization Œ one that is willing to undergo on-the-spot evaluation and identify and work on the inevitable problems that pilots are created to uncover and resolve. The pilot site provides the system developers with a way to evaluate the initial release of the system in a controlled environment and, if necessary, make any changes before releasing the system to all users. Many of the projects we reviewed involve one or more local pilot sites to test and refine their systems. In some cases, the pilot site was an integral part of the development team, building local needs and practical limitations into the initial design and then serving as the initial implementation site.

Sometimes pilots are promoted as a way to get special attention and early implementation for a new system. While this is true, it is only half the story. In return for these benefits, the pilot organization has to commit staff, space, and other resources to a process whose goal is to find and fix problems. Although it has clear benefits, piloting can be frustrating, time-consuming, and disruptive.

A number of considerations go into the selection of a pilot site. Here are few of the more important ones:
  • Representativeness. Will the site(s) you are considering give realistic results for guiding broader implementation? If there is a great deal of local variation, you may need several pilot sites that represent broad categories of local conditions.
  • Organizational capacity to carry out the pilot.
    Does the pilot site have the staff, space, equipment and other resources needed to carry out the pilot without adversely affecting its ongoing operations? Do the pilot site staff have realistic expectations about their roles and the amount and kind of assistance they can expect from developers or consultants?
  • Leadership commitment to the project and to the special demands of pilot status. Do senior managers in the pilot site believe in the goals of the project? Are they ready and willing to deal with unexpected problems? Will they give their staff the support they need to carry out both pilot activities and regular operations? Will they act as liaisons to local officials in other departments who may be affected by the pilot or eventual operation?
  • Geographic accessibility. Is the pilot located in a relatively convenient place so travel costs and time can be minimized for the project staff who need to be on-site and for the pilot staff who need to travel for training or other project activities? Try to avoid a pilot site whose location discourages on-site technical assistance, monitoring, and evaluation. For example, does it always require an overnight stay or several hours of driving, or more than one mode of transportation to get there?