- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
There is a temptation to focus only on the implementation of the tool and assume as you build it people will come. I recently implemented the Project and Resource modules in ServiceNow replacing multiple spreadsheets and manual processes. Our PMO tracks and reports on millions of dollars of project activity in Information Services so it was key that the implementation and transition occur without significant issues. I'll share some key points that lead to the success of the implementation.
1. Keep it simple - very simple
Here is the opportunity to implement all those processes and key business rules everyone wanted - don't. We used a strategy of minimum viable product that is implementing the very basics that would cover the finances, tasks and resource assignments. It's a huge lift to get everyone over to the new product and new processes, compounding this transition with complex processes and business rules could make it impossible.
2. Middle Management
Selling Senior Management on the benefits of the new system is not a difficult task at all. Forgetting to address the business value to middle management could be catastrophic. These are the individuals that will be dealing with the system day to day, assigning resources, running reports and managing the finances. We garnered support by creating a Working Commiitte and putting middle management in that committee. The Working Committee provided resources, direction and support for the implementation. This removed what could have been a significant challenge for the project.
3. Configuration versus Customization
One of the fundamental mistakes that are made with the introduction of a new product is that everyone wants nothing to change or for things to stay the same as much as possible(the reverse condition of point #1).. That is not going to happen. For every presentation to the Working Committee I posed the question, "Make the software do what you want or adjust your process to match the software." I tried to limit the customization and focus on configuration. Longer term upgrades from ServiceNow should not have a significant impact on "custom code".
Possible Next topics
- ROI
- More Key Points on Implementation
- Implementation Roles
Regards,
Patrick
- 1,237 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.