• Products
  • Use Cases
  • Industries


  • Gartner: ServiceNow a Leader
  • 2018 Enterprise High-Productivity Application Platform as a Service Magic Quadrant


  • Your Strategic Resource
  • Discover best practices for every phase of your ServiceNow journey


  • Thanks to you.
  • You're why we're #1 on the Forbes World's Most Innovative Companies list.

The seven essentials for implementation success with ServiceNow


ServiceNow® implementations fundamentally change how people work, and that means implementations need careful oversight and management. In our experience with over 3,000 customers, we’ve identified the most essential elements of a successful implementation—one that brings you the most value. 

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.


Ask yourself these seven questions to ensure a successful implementation of the Now Platform™:

  1. Do we have clear, explicit, and documented business goals for our ServiceNow implementation? It’s easy for implementation to get bogged down in all of the project requirements associated with system and data migration, organizational change, and training. But implementations without a clear statement of business goals—whether in terms of improving employee experience, reducing service outages, increasing speed of delivery, or something else—are often challenging, because they lack a North Star that helps decision makers prioritize activities and resolve competing interests.

    What to do Work with your executive sponsor (ideally, either a C‑level executive or someone who can reflect the C‑level “voice”) to define, document, and communicate a limited set of measureable business goals that everyone in the organization can understand.

  2. Do we have consistent engagement with an executive sponsor for the implementation? Project and/or executive sponsors can be difficult to engage, given the number of priorities on their calendars. Yet without consistent engagement and regular reviews with the project team, it’s difficult to ensure that resources are made available to address business priorities that change during implementation or risks that may surface. Often, sponsorship is less about the amount of time the sponsor spends on the project and much more about the consistency of their involvement. A key metric that organizations should track is the percentage of implementation‑related meetings the sponsor attends—if the number is dropping, it could be sign of declining engagement. 

    What to do Define a regular cadence for consistent engagement with the executive sponsor, and follow a structured agenda that captures:  

    • Progress and anticipated obstacles that may require additional resourcing 
    • Any change to business priorities that may affect implementation
    • Early warning signs or risks that could affect implementation
  3. Have we defined a phased approach to implementation with an early emphasis on incremental wins? “Big bang” approaches to implementation can be problematic due to their complexity. For most organizations, it’s simply too much process change and training all at once, which limits effective adoption. Leading organizations define a phased or iterative rollout of functionality that’s focused on three things:

    • Ensuring the functionality they roll out respects end users’ and service fulfillers’ (such as service desk agents) capacity to absorb it
    • Identifying and capturing lessons learned at each phase of rollout so they can improve subsequent phases 
    • Capturing incremental wins that can drive adoption momentum among key populations

    What to do Divide your implementation phases into the most feasible incremental wins based on: 

    • Your overall value realization 
    • Your organization’s change capacity 
    • The lessons you can potentially learn at each phase 
  4. Have we explicitly defined and documented governance rules for the implementation? Your ServiceNow implementation will involve a diverse group of stakeholders from C‑level executives funding the project to process and service owners to the technical staff responsible for integration and support. It can be easy to lose sight of responsibilities and authorities across these stakeholders, potentially slowing down key decisions as implementation moves forward. The start of implementation should come with clear rules for the road. Create a defined decision model that explicitly identifies who approves different categories of decisions and who is required to be informed or consulted around these decisions—ultimately, this will be one person.

    What to do – Define a responsibility assignment matrix (like a RACI or OARP) for:

    • Strategic decisions, like those related to budget approvals or team resourcing 
    • Business decisions related to implementation, like process configuration
    • Technical decisions, like those related to integration or security protocols 
    • If governance is new or not strong within your organization, make sure that the partner you’re engaging has solid governance experience.
  5. Are we engaging certified and experienced partners to help lead the implementation? Initial implementations should take advantage of the experience of consultants who are familiar with implementation pitfalls and best practices. This limits your organization’s overall project risk and can save time and effort for internal staff who may be required to carry out their “day jobs” in addition to supporting implementation.  

    What to do –  Identify partners with certification in the specific ServiceNow product lines you’re implementing. Review partners and consultants for a consistent, successful track record of experience (and references) with organizations similar to yours in size and industry.

  6. Do we have comprehensive training plans in place for technical staff and end users? Training is often subject to “benign neglect” in implementation. Sometimes it happens at the end of the project, and sometimes the new information is covered lightly and generically rather than comprehensively. But solid technical implementations with inadequate training are a recipe for slow adoption—and a slower path to realizing value.

    Leading organizations pull training forward and ensure their training plans reflect:

    • The specific needs of different populations – These might be the differences across geographic regions or, for example, between service desk agents and process owners. 
    • The needs of end users, not just technical staff – Many organizations often underestimate the training they should make available to end users, whether they’re front‑line staff or business leaders.  

    What to do –
     Document comprehensive, specific training requirements across technical staff and end‑user groups as you plan your implementation. As you identify these requirements, estimate the level of investment you need to support comprehensive training. Then make sure to communicate this to the executive sponsor and reflect it in your overall implementation budget.

  7. Do we have a fully budgeted plan for organizational change management? Your ServiceNow implementation will change how people work for the better—but even positive change can meet with confusion, inertia, and resistance, which will delay adoption as well as seeing value. Implementation should be accompanied by specific organizational change management plans that aren’t generic or purely focused on top‑down messaging. Leading organizations ensure that organizational change management provides the resources for teams to make themselves confident co‑creators and champions for change.  

    What to do Ensure that your plan and budget includes time and support for the teams most affected by the change to play a role in cocreating the change, whether in terms of workshops that elicit their voice in process change or through other mechanisms that address their most critical points of concern. Then invest in resourcing the demonstration and training activities that make teams confident they can navigate ServiceNow and provide key peer influencers with the materials that allow them to effectively champion change across the organization.


For more information, see our best practice guide, Start your implementation journey with ServiceNow, or contact your account executive. 

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.


Explore additional phases


You want to be sure everything is in place for a smooth, successful deployment.


You want to be sure you’re following best practices during implementation.


You’re up and running and want to get the most from your investment.


You’re ready to extend ServiceNow into other areas of your enterprise.

Thank You

Thank you for submitting your request. A ServiceNow representative will be in contact within 48 hours.

form close button

Contact Us

I agree to receive emails from ServiceNow about product, services, and events. I can unsubscribe from any email if I wish.