There have been many articles written about starting your BPM projects. Let’s look at what happens before that.
People [companies] wouldn’t purchase BPM [business process management] software if they weren’t trying to solve some problem. And, this problem has to have risen to a level of great annoyance or they would just deal with it.
Some typical problems include:
- The process is taking too long
- Some steps are being skipped
- There is no visibility into the status of the process
- Short cuts are being taken
- The process stops / falls off the map
Once the problems have risen to the point of annoyance, companies begin to look for a solution.
So, where do you start?
Do not start with technology. Do start with the process.
Any BPM software that you purchase will need to be configured [or coded] to map to your individual business processes. In order to configure your BPM software, you will have to document how you want your processes to function. Start by documenting your troublesome process.
If the troublesome process is too large, break it into smaller pieces. Some real reasons include: The need to show project success and success can’t happen if people lose interest – keep the project short enough so that doesn’t happen.
Test your project documentation [on paper] to make sure it works and to make sure it works the way you intend.
Now you can begin looking at technology. The technology needs to fit your business, not the other way around.
There are a large number of subject matter experts in this field – including me – contact any of them for help…
Do you have a process that isn’t performing?