BLOG
Congratulations! You’ve purchased ServiceNow. Now it’s time to make its broad suite of capabilities work for your organization. That takes us to the topic of ServiceNow implementation. What’s the right approach to ensure success? What can you do to make sure your investment and effort doesn’t turn into shelfware? And, of critical importance, which implementation partner is best for you?
Given the expanse of service management in the enterprise and its numerous applications, these considerations are very real. Aside from making sure ServiceNow pricing is at or below fair market value, the most important cost aspect of your ServiceNow investment will be implementation. The way you handle implementation will have significant bearing on the ROI you receive.
In this post, we’ll discuss several considerations that will lead to a successful ServiceNow implementation, higher adoption across the enterprise, and – ultimately – greater ROI.
There are a few things you can do to make sure your ServiceNow investment delivers value and savings for the long-term:
Using an experienced implementation vendor is a must. So what are your options? They fall into two buckets – ServiceNow Professional Services or a vendor partner. How do you know which one is the right fit for your implementation? Let’s take a look at both options.
ServiceNow PS is the gold standard of implementations. They are the ultimate ServiceNow product authority, often leveraging resources that have been involved with new product releases and features since their development stage.
ServiceNow PS employs a QuickStart, Agile-oriented methodology focused on time-to-value and knowledge transfer for the customer. Simply put, the concept focuses on short development sprints comprised of a few weeks rather than months, and embraces a “we do, we do together, then you do” model to ensure that the customer can support their ServiceNow environment post-implementation.
First-time, basic implementation of Service Management Suite functionality such as Incident-Problem-Change, Knowledge Base build out and migration, Service Catalog build out, and Asset Management.
Because ServiceNow PS resources are the ultimate authority and scarce in availability, they will be highly priced. ServiceNow PS staff is limited, so they tend to focus on core functionality versus projects that require a high degree of customization, ServiceNow niche product implementation, or specific industry or product use cases. Because of this, ServiceNow PS availability can also be limited based on the timing of your implementation.
More so than many software companies, ServiceNow runs a tight implementation vendor ecosystem that promotes deep knowledge sharing and training across the ServiceNow Community. ServiceNow is very transparent about recommending when a vendor partner may be the best approach depending on the customer’s timing and goals, especially if cost is a large consideration. There are four types of partners in the ServiceNow ecosystem:
ServiceNow’s implementation partners typically adopt a similar QuickStart, Agile-oriented methodology and provide their services at a fraction of the cost of ServiceNow PS. An added bonus is they often have more all-around implementation experience than ServiceNow PS. In other situations, a partner is highly recommended for niche-oriented projects that ServiceNow PS will not have the bandwidth or experience to handle.
First time, basic implementation of Service Management Suite functionality as well as niche product implementations.
The evaluation process can be a little cumbersome especially if you are comparing a GSI against a smaller generalist or niche partner. Resource availability can be an issue for smaller and niche partners. There is also more of a quality risk when going with a non-ServiceNow entity simply because they are not ServiceNow.
Once you’ve implemented the basics, you’re only just getting started. Schedule a roadmap planning session with key members of IT and business senior leadership – and revisit the roadmap every 6 months. This will enable you to expose the organization to how ServiceNow can automate key pain areas within the organization and prioritize your ServiceNow projects. By taking these steps, you will maximize your success with the solution, increase adoption and time to value, and be in the driver’s seat for future ServiceNow investments and renewals.
This blog post was originally published on March 31, 2017 but has been updated to reflect the latest changes to ServiceNow’s solutions and implementation best practices.
This website uses cookies to improve your experience. By using our site, you accept our use of cookies.