Workflow Analysis

This is because you are transferring a process from one way of doing things to another -- or from one system to another. The system change is usually the result of a diagnosed problem -- one that employees do not simply want rendered again electronically.

The more people that are involved in completing a process, the more crucial workflow analysis becomes. 

Without an adequate analysis of workflow:

• the application designer cannot understand the problem
• the application designer cannot suggest a solution
• the programmer will not know what should appear on the screen when
• the same problem may emerge in the new system
• the new system may cause more problems and cost more than the old one

Without an objective third party to perform the analysis, results may be biased in favor of person filling the role of the analyst. 

With a thorough workflow analysis, organizations can implement protocols that do not duplicate efforts. This can mean:

• Data is entered into a system once, and is accessible to everyone who needs to use it, in the form they need it in.
• Everyone understands who is responsible for various aspects of the process
• The people who "own" pieces of the process have adequate control where they need it.
• System security can be reinforced and permission established on multiple levels.
• Appropriate checkpoints exist to ensure that the outcome is targeted, of high quality, and complete.