Review: ServiceNow Request Fulfilment

This independent review is part of our 2012 Request Fulfilment Group Test. See all participants and terms of the review here.

Executive Summary

Elevator Pitch A solid integrated platform, with the focus on improving the user’s experience of Request Fulfilment, and also focussing on the equally important business view.
Strengths They boast a unique approach of focussing on improving an end-user’s experience in engaging with IT through the Request Fulfilment process.
Weaknesses Although there are administration courses, all too often the responses relied on finding answers to configuration questions “in the wiki”.It is comprehensive, but when others promote that element of “handover” to the system’s custodians, ServiceNow seem to want to default to detachment.
Primary Market Focus Mid-size to Large Enterprise level customers

Commercial Summary

Vendor ServiceNow
Product ServiceNow
Version reviewed Berlin Release
Date of version release September 2012
Year founded 2004
Customers 1,200+
Pricing Structure ServiceNow offers a subscription license based on the number of IT process users, starting at $100 / IT process user / month with volume discounts available. There is no charge for end user access.
Competitive Differentiators
  • A single, organically developed ITSM platform built in the cloud with nothing acquired or OEMed that leverages knowledge management, collaboration, graphical workflow engine, ITSM stack, service catalog and request, runbook automation, CMDB, ITAM, software asset management, etc. all included in the subscription license.
  • An approachable, social and modern Web UI built to improve the end user experience with IT through an emphasis on usability and self service.
  • A configurable platform includes a content management system that allows IT to provide a user experience that is identical to existing customer Web properties and that matches existing user experience and IT workflow.
Additional Feature Service catalogue, service portfolio, and dozens of other enterprise service automation applications all provided through a single cloud-based platform.


Independent Review

ServiceNow has been one of the fastest growing software companies in the world, since forming in 2004.

One significant difference I saw in looking more at the single-tenant commercial deployment scenario (opposed to Managed Service Provision) was how to leverage a business view of the service catalogue.

More importantly, that view can be combined with elements of the Employee Self Service portal to give users a lot more information about the services they use, even before they go down the Request Fulfilment route.

That is not to say that other vendors do not offer the same, but ServiceNow’s focus sees the tool as an enabler for information up and down the chain, about the affordability of the services IT provide, and the usability for end-users.

Request Models

End-users can come in to the Request Fulfilment screens through a self-service portal URL which provides them a simplified view of the options available.

This can be configured to provide a customer’s look and feel, and limits the choices in the sections so that the end-user is not overwhelmed with a mass of service catalogue options.

ServiceNow recommend the three main sections (Order Things, Knowledge, Get Help) and no more than four elements beneath that.

Requests can be bundled together (for example for new hires) and most vendors now adopt the look and feel of a shopping cart experience to good effect.

But they want to make the interface as intuitive as possible.

All this is laudable, but as always that freedom of intuition requires detailed thought and configuration behind the scenes.

Menu Selection

The back end allows administrators to configure routing options, approvals, even the addition of fields mostly through drop-down and selectable variable values.

There is the capability of doing further, more complex development and administrators would need to either have an understanding of Java Script programming, or (in their words) at least have a desire to learn.

But in fairness, ServiceNow also recognise that resources or skill levels in organisations may not stretch to that – and certainly enough can be done with the options available to build on the existing  templates, utilising a graphical workflow editor, pick lists and right-click UI controls .

Request Fulfilment Lifecycle

The first step in the ServiceNow world is to build up the items in a way that makes it an appealing experience for the end user.

Once the aesthetics are taken care of, then start tackling the more repetitive elements of the process first, and then worry about tackling your exceptions.

The graphical workflow is extensive, and tasks, actions, options attached to those actions are taken care of with drag-and-drop.

It is designed so that Business Analysts or Process Managers can translate those steps graphically to configure the back-end workflow.

In addition, a business service catalogue can be developed, and this has a two-fold purpose.

Often customers have difficulty in transitioning to a service model, and understanding what that really means to them.

Here, IT can define to the business what services it offers, the reasonable levels of availability and response that can be expected, and can obviously build from there, for example Email Services.

This view is also linked to an end-user’s view of their world, so they can proactively see (even before entering the whole ticket rigmarole), service alerts or issues.


ServiceNow are not alone in the market place at focussing on how customers want to set things up behind the scenes.

Administrators of the system should have a strong end-to-end process knowledge to get the best from configuring the workflows.

Their approach, though, differs between good practical advice in terms of configuration versus a wiki-focussed depth of support information.

For example, during the demo, I was impressed at the steps outlined for an approach to tackling the workflow configuration:

  1. Build the items you want the end user to see first
  2. Worry about process later (repetitive tasks first, then exceptions)

But I am also pointed to a range of links of everything in the wiki.

There is no doubt that the information is comprehensive and, given how much is in there, fairly well organised but it can be very time consuming to wade through the options to find things, and I speak from experience!

ServiceNow offer a foundations e-learning course that can be completed within an hour.

They also provide a three-day ServiceNow system administration class, a two-day advanced system administration class, and a three-day scripting in ServiceNow course. System administrators can be up to speed within a day and be extremely proficient within a week.

However, at its core, ServiceNow does offer a well-integrated Request Fulfilment module, and reminds us that business benefit should be a driver, and provide a well thought out visual capability in that area.

ServiceNow Customers


Click on the thumbnails to enlarge.

From The ServiceNow Brochure

  • Leading provider of cloud-based services that automate enterprise IT operations.
  • Suite of applications built on our proprietary platform that automates workflow and provides integration between related businesses.
  • We help transform IT organizations from reactive, manual and task-oriented, to pro-active, automated and service-oriented organizations.
  • Assessed to PinkVERIFY 3.0
  • Provides an open, no-registration-required live instance of ServiceNow:

Further Information

Group Test Index

This independent review is part of our 2012 Request Fulfilment Group Test. See all participants and terms of the review here.

2 thoughts on “Review: ServiceNow Request Fulfilment”

Comments are closed.