Manage goals and identify successes to maintain public and constituent agency support for a coordinated incident management program.
Major metropolitan areas' experiences with formalized incident management programs.
public. Providing timely, accurate information to the public enables them to make informed choices and will be essential in sustaining a successful incident management program. The following lessons are based on the experience of other ITS professionals on managing goals and identifying successes to maintain public and constituent agency support for a coordinated incident management program.
- Identify realistic goals and make sure that expectations are met. Formulating goals is always an exercise in balance. The goals must be aggressive enough that they will foster enthusiasm, but not so aggressive as to be unrealistic. They should create realizable expectations, whose achievement can be measured and communicated. The risk of setting goals too high is that the program may be perceived as a failure. Goals that cannot be measured may be viewed as a sign that the participants have no confidence in the program. Goals that are set too low may not be viewed as demonstrating a true value for the community or justifying the investment. In each case, the interest will wane, and participants are likely to withdraw their support.
- Ongoing successes are important. The program will need to have some ongoing, visible successes in order to sustain interest by participants and to keep the funding flowing. It is important to realize, however, that the full scope of benefits may not be immediately visible or easily measured. Because of this, effort must be focused on keeping the program moving forward and on identifying successes. Successes can sometimes be derived from special circumstances, such as a service patrol providing aid and comfort to a school bus full of stranded youngsters. If there are no visible winners, it will be difficult for some major participants to remain involved.
Author: Vincent Pearce
Published By: U.S. Department of Transportation, FHWA ITS Joint Program Office, Federal Transit Administration
Source Date: 5/1/2001
EDL Number: 13149
Other Reference Number: FHWA-OP-01-002/FTA-TRI-11-00-03URL: http://ntl.bts.gov/lib/jpodocs/repts_te/13149.pdf
Average User Rating
Show the V