3 ms·

I couldn't agree more. But as others have said, it did replace some awful late 90s, early 2000s, software. What's funny is that my dayjob became a re-seller fo

I couldn't agree more. But as others have said, it did replace some awful late 90s, early 2000s, software. What's funny is that my dayjob became a re-seller for ServiceNow, and our ServiceNow install is terribly slow. Then we have a major government client that we tried to sell ServiceNow to, but they decided on another re-seller. And I still have to work with this client as a consultant so I have to login to their separate ServiceNow setup, and wow is it faster! That other vendor that won the contract over us sure did a much better job at the setup than we ever did. (I was not involved in the re-selling or setup of ServiceNow at my dayjob, I only work in it as a user)

TheNewsIsHere 3y ago
One of ServiceNow’s biggest mistakes and greatest strengths is how much freedom it provides admins and devs to absolutely grind the instance to a halt. Every shitty or slow ServiceNow instance I have seen in recent memory is because the customer is slugging along horrible code and poorly designed LCNC apps. A well managed instance can fly. Not that the platform doesn’t have its problems of course. But most people’s experience with it is as the victim/end user of awful implementations. My university used a resold white label instance from a consultant and that thing was an absolute disaster.