Process Change

If an application or BPM solution is implemented without considering the need for process change, you may well be wasting your investment by 'automating your spreadsheets'.

There are a number of key points to be aware of when considering how much process change should be included in your implementation:

• Attempting to configure an application built to support BPM 'best practice', to meet 'in house' practices, based on old technology or spreadsheets, would be inefficient at best, and may unnecessarily increase the cost of implementation.
• Taking a good look at your process during the implementation will allow the business to make full use of the feature functionality available in the applications.
• A complete overhaul of your processes, or a 'process re-engineering exercise' that fundamentally changes the structure of the organisation, should not be done as part of a BPM implementation. This is change management and should be dealt with separately.
• A proper functional decomposition of the process should always precede any process change, to ensure that operational integrity is maintained; in short, understand what you are changing.
• Make sure you get key people to engage in process change, not just those with the time to attend meetings.
• Ensure that the new processes are the basis of testing and training.

ReportSource has significant experience in BPM process change. Our Methodology contains the right level of process change to ensure that you get the best out of your investment, without letting the project turn into a wholesale 'process re-engineering exercise'.