Business Process Analysis: No Big Deal with e5

A major gating factor to quick implementation of workflow/BPM solutions is that the business process analysis must be done prior to writing one line of code. This analysis process can take weeks to months depending on the size of the organization/department and complexity of the solution.

The analysis is performed ‘off-line’ – we use terms like ‘re-engineering’ and ‘change management’ to describe the process – requiring the business analyst(s) to predict and outline the optimum business workflow each step of the way, for all types of work activity, including exceptions. The outcome of this exercise is the ‘as is’ and ‘to be’ scenarios, with the latter scenario being the basis used for workflow development.

In addition to business process analysis being a long, protracted activity, the question always asked is ‘How do we know this is the optimum workflow process?” With traditional workflow/BPM solutions, the answer is “You don’t.”

So the business analyst takes his most educated guess at optimization, work allocation, routing, exception handling, etc. The solution is then designed and implemented, metrics are established and dashboards are installed (usually taking another few months to implement) and perhaps one year down the road, the organization has the first glimpse of success?  Or is it the first glimpse of the results of change? Regardless, if the results don’t deliver the outcomes originally expected, the business analyst then goes back to the drawing board performing more business process analysis and the cycle continues. And, each time the process is changed, a developer is required to re-write code. With this process, it is no wonder that most BPM users can never identify the ROI on their investment post-implementation.

Work Completed within SLA prior to working with e5

The e5 adaptive case management development tool completely eliminates the need for any upfront business process analysis. Instead, the current process is mirrored with e5, which is a short-cycle task given e5’s integration with SharePoint. Depending upon the complexity of the current process, implementing e5 typically takes a matter of weeks. Once implemented, built-in dashboards immediately deliver real-time metrics, providing the business analyst with a baseline of productivity information. From there, the business analyst can begin to ‘tweak’ the process to improve (no need for a developer in most cases), remeasure, tweak again – repeating until the optimum workflow has been achieved and supported by ‘before and after’ metrics.

Read our customer case studies about how they implemented e5 and the quantifiable results they achieved.


To read other articles on this topic, visit our Business Process Analysis Sitemap