Please share with the community what you think needs improvement with ServiceNow.
What are its weaknesses? What would you like to see changed in a future version?
Transparency in the pricing model needs to be improved.
I do not like the user interface. I would like to see a more streamlined process to assign tickets to support people.
There are Virtual Task Boards in the tool in the latest releases. There are many of them in the Scaled Agile Framework. There is some room there for improvement. It's really quite promising but, at the same time, it could be improved and I believe it will be improved soon.
For healthcare, which is a pretty audited environment, there are no concrete solutions for digital signatures, apart from our license with Adobe, so it requires orchestration. That is one area for improvement. Apart from that, initially, we struggled with financial forecasting and financial management in the PPM module. That needs improvement along with the IntegrationHub which came out in a recent release. It's still in its initial stages. That could grow into a more solid solution that could be more helpful.
Earlier, ServiceNow had the ability where you could build your own UI. The standard UI is very restricted. It doesn't look as good, compared to Remedy. Building your own UI requires some additional coding, but the standard UI is not that good when compared to Remedy's UI. When it comes to reference fields, there are some limitations where you aren't able to use them, like in relationship queries. In Remedy, when you click a menu, you get options directly, whereas here, if you use a reference field, it points you to a different form. So the UI experience totally changes for the end user. These are some of the ways ServiceNow could improve the UI, out-of-the-box.
ServiceNow is divided up into a lot of modules, so I'll give an example, instead of going into every single module. For me, there's a real opportunity, especially within the IT Service Management suite, to give a much better overall view of the workflow that individuals have across the different applications. At the moment, a lot of information is quite siloed in the different tables in ServiceNow. There is a real opportunity to present, in a centralized way, some form of universal work list, to give better ideas around demand and supply of resources, and then help prioritize that work. The only other thing that I'd say about ServiceNow, in general, is commercially related around licensing, and it's a big inhibitor for a lot of our customers, especially those who are innovators on the platform. I've got a couple of really good example clients where they are limited in what they can do with the product. If they were to do what they wanted to do, the licensing that would come about, from a platform runtime licensing perspective, would mean it wouldn't have the same value proposition. An improvement area, to summarize, would be better licensing for when clients are trying to be innovative on the platform.
HR Service Management is one module that needs a lot of improvement because it's a pretty new module. It was introduced in the last two years. It's becoming more mature day by day, but there is a lot of scope for improvement in that module.
Change Management is the area I have found that this tool can be improved because there are so many fields which are missing, such as urgency of the customer request and how the priority is defined. These are some of the areas in which I found that BMC Remedy is much better than ServiceNow.
There are a few things that it needs to improve, like automation of most things out-of-the-box. For example, when it comes to cloud management, we are still going with manual intervention. Instead of that, if we had an out-of-the-box feature available, that would be great. Also, the first time we looked at the Service Portal, it was quite hard to understand its interface. People were looking for things, like the email functionality in Service Portal. That was not available and there were other things in Service Portal that were not up to the mark.
Where it could be improved is Discovery. This may sound odd since I just praised the value of ServiceNow Discovery, but improvements to its automatic detection, the breadth of devices, and the depth of devices covered, as well as keeping up with new technologies, are all essential. Microsoft has caused some issues recently with its decision to move away from SNMP and WMI in favor of PowerShell management. ServiceNow will need to make changes to move away from these deprecated services and to discover these devices. Discovery engines universally rely upon SNMP to detect, at least at an initial level, what type of device they are talking to. Without SNMP, some other platform will need to advertise the device and its capabilities. Most applications offer API (ideally REST-based) connectivity and ServiceNow should expand upon its use of these connections.
The Service Portal could be improved. There are some things in it which are somewhat difficult for me to understand.
It's not very secure, it's web-based, and I prefer Remedy. Both the security and the web interface could be improved.
There's one that I would like to see improved to reduce the cost of our ServiceNow, related to the resetting and unblocking of passwords for users who forget their passwords. We had a conversation about this with ServiceNow. We don't have a huge amount of password reset requests, but the minimum package of resets that ServiceNow offers is much more than we need. In conversations with other companies that have a similar profile to ours, they complained about the same thing: "Why should I have to buy a minimum number of password resets, when that amount is much more than I need?" They should have some kind of scaling of the reset package, like zero to 100, 101 to 300, etc. That would be a little bit more useful for us. That package is very expensive. It's more expensive than if I were to have someone in-house who was dedicated to doing those tasks.
I would like the reporting aspect to be better, including the graphs. It could have some way for us to easily to export to a csv or spreadsheet so that if a graph cannot be provided by ServiceNow itself, we would be able to use other applications to create them. Also, if there was a feature that enabled us to interact with end users directly within ServiceNow, like an instant-messaging type of feature, that would be great. Another nice feature would be a way to easily to assign tickets and incidents to the techs who will be working on them. That could be better. Other than that, the system seems to be working just fine.
Some enhancements to the self-service platform would be helpful. That part is still a little barebone. There are some things that they could do better that we have suggested to them. Also, the mobile app is not bad, but it's limited. They are going to be working on that, I'm sure, over the years.
* The ability to embed help information onto the screens. * The scalability needs improvement.
We would like to have an Asset Management and/or Project Management feature enabled in this version and in the IT Service Management edition. The Express edition does not allow the option for scripting.
It's missing monitoring capabilities.