Unlocking the Future of Service Desk with Intelligent Automation
June
8th 1:00 PM EST
Create, then Automate: A Conversation on how to Standardize Business Processes to Automate Them
November 10th 1.00 PM EST
This particular point is around soft side of the issues that organizations may face while adopting BPMS.
A pilot project is a great way to iron out a lot of issues and tune overall program structure to align with the organization culture and objectives. While it is important that organization starts with a pilot project, it is even more important that it picks the right process to begin with. We have seen an organization trying to get BPMS in and it was very IT driven decision. IT wanted to push BPMS across without getting business on board and built an “IT Issue Tracking Process Solution” as a first solution, given lack of immediate business support. The program went nowhere for almost one year, given there was no visibility or clear RoI for this. It took until a new CIO come on board to realize mistake of his predecessor and put program back on track!
During the BPMS evaluation itself, it is better to begin with a workshop where business is involved to understand benefits and get them on board, get a business sponsor on board, who has a “right process” that can be picked as pilot.
The following points must be taken into account to ensure you have picked the right process.
Some of advantages of picking the right first process:
In next blog, we will review why it is important to pick right SI partner. This is one of the motivations for starting Nividous!
Join our community of >10K automation enthusiasts! 
