Principles for Identifying Your First AgilePoint Process

Focus on People

Human end users see the greatest benefit from automated processes. Processes that make participants' jobs easier will not only improve efficiency, it will also help adoption of the AgilePoint system as more processes come online.

When you are deciding upon your first process to take on, try to focus on processes where users must touch the system frequently and/or feel a great deal of pain with the current process, and then improve the process for them.

Focus on Subprocesses

Often organizations want to start with a large or complex process first to get an immediate high impact. However, AgilePoint recommends breaking large processes into smaller subprocesses.

For example, when sending an alerts for events such as approvals or system errors, the alert subprocess can always be the same, regardless of the parent event that triggers the alert.

• Subprocesses are relatively easy to manage because they are smaller
• Subprocesses are relatively easy to define because they often occur within a single department or group.
• Subprocesses yield a high impact because they can often be reused across processes.
• Modularized subprocesses can use a standardized interface, so changes to the subprocesses do not impact the parent processes. (This is similar to the advantages of the SOA software model.)