Chapter 3. Best Practices
Match the technology to the job
Understanding that the solution to one problem is not always the solution to another even
highly-related problem, helps a project team avoid mismatching technology solutions to problems.
Further, understanding that not all problems have or require a technology solution helps ensure
that an appropriate match between technology and the task at hand is made. Over-doing as well as
underutilizing technology are both risks to state-local system initiatives.
Project teams often look to the technology lessons from their last project and try to apply
them in the current project. Or they become interested in a new technology that seems to be
barreling through the marketplace with powerful new features. They sometimes fail to give full
consideration to the work processes and overall business context in which the system must
operate. Consideration must also be given to user capabilities and the organizational and
staffing limitations of the agencies that will be implementing, using, and maintaining the
system to deliver services. Technical awareness activities that introduce a variety of technical
tools to the project team are often helpful. These can consist of literature reviews, searches
on the World Wide Web, vendor presentations, or attendance at technology exhibitions and
conferences. Prototyping is an excellent, relatively low- cost way to test the
"fit" between a technology and the environment it which it must work.
In most cases, incremental system building using appropriate standards, prototyping,
piloting, and evaluation techniques, is a good idea. This approach allows for additions to
system functionality as well as for the integration of new technologies over time.
"Before choosing technology, consider work processes, user
capabilities, organizational factors, and existing systems."