This is an article in the July 2002 issue of Geospatial Solutions magazine, written by Jeff Meyers. Mr. Meyers is president of Miner & Miner, a software development and engineering consulting firms and has managed GIS projects for more than 20 years.

He talks straight about what can go wrong with GIS project implementation. Many variables affect a GIS project, and a cookbook approach to building the databases and using a GIS seldom works. He lists the top ten mistakes that can keep a GIS from delivering the promised business benefits.

The ten mistakes are briefly summarized below. If you are considering or are in the process of implementing a GIS, this article is a ‘must read’.

10. Didn’t have enough IT support. A GIS is more than ‘just mapping’, and database administrators and other technical support are needed to get the system off the ground and thrive in an integrated environment. Continuing maintenance is also important.

9. Had too much IT support. A balance is needed between meeting IT standards and procedures and getting the GIS task done in a timely way.

8. Failed the "bus" test. If the GIS is implemented by a single person and that person gets hit by a bus, the system could be in big trouble.

7. Lacked a sponsor (at a high enough level). An upper management sponsor can help convince other management to stay the course when a GIS project appears to bog down.

6. Had a poor project manager. The project manager must understand the goals and stick to the task until it is achieved.

5. Had a poor methodology, or none. It is important to be clear on the tasks required to implement the GIS and the methods of accomplishing the tasks are well defined. The project team must understand and support the methodology.

4. Had unrealistic schedule expectations. Create realistic time lines from the beginning and keep components small.

3. Didn’t plan for technology change. Suppliers are always providing new tools and usually more quickly than they can be incorporated into an implementation cycle. "GIS implementation is a process, not an event." The GIS can continue to be improved in small increments.

2. Didn’t/couldn’t/wouldn’t take internal ownership. The GIS will continue to need care and nurturing - user training, regular database updates, continuing support. The internal GIS team needs to be involved from the beginning.

1. Had unrealistic scope of expectations or none. "Scope creep" is the single most common cause of death among GIS projects. As users start learning and experiencing the power of being able to manipulate data in new ways, they become ‘give me more’ junkies.

Geospatial Solutions magazine is free to qualified people. Go to the Web site to sign up for your free copy: www.geospatial-online.com.