- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Preparing for your ServiceNow journey is a lot like preparing for most journeys. Your experience and success depend on how well you have planned for it— what gear to carry, which route to take, what contingencies you need to prepare for — in advance.
Our experience across customer journeys point to four “must do's” as you prepare to implement ServiceNow:
1. Be clear and explicit in your vision for business value
Organizations that approach ServiceNow as a “rip‑and‑replace, lift‑and‑shift” alternative to their current systems limit a full view of the potential value ServiceNow can deliver. The most successful customers include their key business stakeholders in an exercise to clarify the path from vision to value. This exercise should document the business outcomes you need to realize, and how you will measure success. You should be able to capture “vision to value” on a single page, as shown below.
Once you have built a common understanding of the business outcomes you want to realize, prioritize ServiceNow capabilities that can deliver the earliest, greatest value to the business.
2. Make sure you have a foundational configuration management database (CMDB) model in place
The CMDB is a critical “single source of truth” to support smart decision-making by your service desk and rep teams, enabled through ServiceNow. That’s why we recommend an early implementation and integration of CMDB capability. A well‑configured CMDB can save you 40% on your ongoing IT efforts.
But if the data model for your CMDB is not planned properly, you can struggle to implement, sustain, and drive value from CMDB. To maintain your CMDB health, ensure that the CMDB is appropriately scoped to support your business objectives and focuses on the data required to support those objectives.
3. Prioritize the capture of high-visibility, low-cost wins
Progress in implementation and value realization can stumble if you don’t have early and strong adoption among service consumers, fulfillers, and developers. Look to make room for the early implementation of capabilities that first promote the broadest organizational exposure to the Now Platform interface through highly visible service experience improvements, and second, do not overpromise or have significant dependencies with other capabilities. See the graphic below for examples:
Incident management and request management will be ideal quick-wins for your ServiceNow implementation, as opposed to a capability like service mapping, that requires strong discovery, event management, and configuration management capabilities for effective implementation.
4. Don’t wait to build effective organizational change management
Successful ServiceNow implementations don’t just focus on the technology, but also put in the right organizational change management—communications, training, and a community of champions— in place to support the implementation. An effective, tailored communication plan can help drive awareness on the value enabled through the ServiceNow platform. Building and training an internal team of ServiceNow experts—across the platform team, fulfillers, and users—is essential to drive initial adoption. A community of champions— a group of stakeholders willing to contribute their own creativity and experience to evangelize your ServiceNow project—plays a critical role in scaling adoption, and building organizational support to expand ServiceNow to new business opportunities.
For additional details and lessons learned, download our Success Playbook, How to Start the Implementation Journey.
Pooja Gupta, Research Manager, Best Practices Center of Excellence – Customers Success at ServiceNow
- 960 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.