The goal of BPM is to improve efficiency and ultimately improve profits…
Before choosing a software vendor, here are some steps that will help you to create a solid requirements document.
Choose a Champion
A champion will be the evangelist on this project. They will promote the benefits of process improvement up to management and down to the user community. This is an internal sales activity that will not likely diminish any time soon.
Select a team of stakeholders
Be sure to involve all of the people that these processes will affect. Bring nay-sayers into the fold so that they can feel some ownership.
Choose the initial process to manage
Choose a process that has some visibility – one that, if improved, will be beneficial to the company. This initial project should take less than 6 months to complete so that people don’t lose interest.
Document how you actually work
It is important to establish a baseline. Document your process as it is working today. Attempt to follow that process manually – this activity will let you know if you have documented it correctly. Measure how long it takes to complete the process for your baseline.
Improve the process
Look at activities within the process that do not add value. Look at ways to eliminate these activities. Look at activities that could be handled by a computer rather than a person. Identify the impact this would have upon your process. This activity should help you identify the cost savings of your solution.
Create your Requirements Document
If you haven’t got this project approved, this document along with the cost savings can be used to pitch it to upper management. Use your requirements document to speak with potential BPM vendors.
What would you add or delete from this list?