Developing an eForms Strategy - Click to Register | Ray Killam
December 2, 2010
What is an electronic form? How are they evolving? What will these forms look like in the future? Are electronic forms really "applications" and thus subject to IT development requirements?
After more than 25 years of electronic forms efforts, why are most organizations still doing mostly simple print-on-demand and fill-and-print forms? Why do many eForms programs fail, or at least fail to achieve their potential?
As the number of pre-printed forms declines in an organization, even less emphasis is generally placed on forms management. Electronic forms are viewed as the responsibility of the Information Technology department, and are typically viewed as front ends to databases. Forms are created using tools available, such as Microsoft Word, PageMaker, Lotus Notes, and Web development tools. They are frequently weak in function and utility.
An enterprise-wide program generally includes plans for development, deployment, support, software standards, output strategy, management reporting and cost benefit requirements, including Return-on-Investment. These plans can vary widely between organizations and are dependent upon the organization's existing infrastructure and standards already in place. Each element has specific considerations that should be decided and published as a part of the Enterprise eForms Guide.
This presentation will explore the elements of a successful enterprise eForms strategy, success factors, risks, and management support requirements. It will examine both "inside" and "outside" the firewall issues and requirements.