The steps we always take to RAPIDly implement any ServiceNow module are as follows. Though the steps are the same, our actions will differ based on the ServiceNow module to implement. For ease, we’ve taken ITSM as an example here:

1. Understand
We start with assessing People, Process, Technology and Data. We gain an understanding of your business objectives and relevant KPIs. We set up structured capturing of As-Is (master) data to populate ServiceNow.

2. Level up
We obtain executive sponsorship and train key stakeholders on the “Why, Who, What and How” of ServiceNow OOTB.

3. Showcase
We showcase an end-to-end demo of the processes using your master data, we explain the purpose and usage of each field, UI action and views. We identify and capture required inputs for a smoother process execution.

4. Align
Work with your individual teams to clarify Technical Service Offerings and develop Catalog Items, CMDB data structure and possible automations.

5. Deploy
We perform UAT testing. We start training to excite, enable and empower end-users to start using ServiceNow. We establish platform governance to embed outcomes.

If you’d like to know the details of what steps we take for a particular ServiceNow module, don’t hesitate to contact us!

There are many factors that influence the speed of our RAPID implementations, including what applications we need to implement, and the maturity and complexity of the organization. For relatively simple applications like WSD and ITSM (limiting the scope to essential processes only), a first go-live may be achieved in as little 30 calendar days.

One of the most common factors that delay a RAPID implementation is the availability of key resources at our clients (e.g. process owners, architects, etc.). As these people are often vital in running the business, making them sufficiently available for digital transformation projects is a key success factor and something you need to be aware of.

In any case, we like to work Agile as often as we can to ensure we add value quickly. Even for more comprehensive projects, we always recommend a first go-live within 3 months of the start of a project. When the scope is larger, we schedule a series of follow-on release moments where additional functionality is made available. This allows our clients to benefit from the new possibilities as fast as possible, while keeping the option to steer and adjust priorities as we move forward.

Our RAPID approach leverages standardization and reusable assets. However, there are plenty of organizations who have invested heavily in tailoring processes and capabilities in ServiceNow to their own ways of working. With that, they’ve deviated from what is standard (OOTB) quite a lot. In this scenario, our RAPID approach will not be the best fit our Enterprise Implementations approach will help you get the most out of the platform in this situation.

In short, these three things will save us time:

1. Accelerators and reusable assets take away the need for manual configuration and internal discussions.
2. By leveraging best practices and standards, we can focus more on training and adoption.
3. We can use standard training materials and don’t need to develop custom training materials for you.

The answer is yes to both scenarios.

In case you want to implement a new module on an existing implementation, the benefits of RAPID will still apply.

In case you want to re-implement an already implemented module (e.g. going back to out-of-the box), the RAPID approach may also prove useful in accelerating the transition.

For upgrading existing integrations, the reusable assets part of RAPID could also prove useful, but an assessment will be required to see which parts are still of added value, and if there are any conflicts with your existing configuration.